View on GitHub

DNSViz: A DNS visualization tool

ru

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Bogus (4)
  • ru/NS
  • ru/NSEC3PARAM
  • ru/SOA
  • ru/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 30903)
  • ru/DNSKEY (alg 8, id 43786)
  • ru/DNSKEY (alg 8, id 44301)
  • ru/DNSKEY (alg 8, id 52263)
  • ru/DS (alg 8, id 43786)

Delegation statusDelegation status

Secure (1)
  • . to ru

NoticesNotices

Errors (18)
  • RRSIG ru/NS alg 8, id 52263: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG ru/NSEC3PARAM alg 8, id 52263: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG ru/SOA alg 8, id 52263: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG ru/SOA alg 8, id 52263: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • ru zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (193.232.128.6, 194.85.252.62, 2001:678:16:0:194:85:252:62, 2001:678:17:0:193:232:128:6)
  • ru/DNSKEY: No response was received from the server over UDP (tried 10 times). See RFC 1035, Sec. 4.2. (2001:678:14:0:193:232:156:17, UDP_-_EDNS0_4096_D)
  • ru/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (194.85.252.62, UDP_-_NOEDNS_)
  • ru/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (193.232.128.6, 193.232.142.17, 194.85.252.62, 2001:678:14:0:193:232:156:17, UDP_-_EDNS0_512_D_KN)
  • ru/DNSKEY: There was an error communicating with the server over TCP (UNKNOWN). See RFC 1035, Sec. 4.2. (193.232.156.17, TCP_-_EDNS0_4096_D)
  • ru/SOA: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 10 times) with the DO bit set. See RFC 4035, Sec. 3.2.1. (194.85.252.62, UDP_-_EDNS0_4096_)
  • ru/SOA: No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared (however, this server appeared to respond legitimately to other queries with the DO EDNS flag set). See RFC 6891, Sec. 6.1.4. (194.85.252.62, UDP_-_EDNS0_4096_D_KN)
  • ru/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (193.232.142.17, 194.85.252.62, 2001:678:14:0:193:232:156:17, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • ru/SOA: The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (194.85.252.62, UDP_-_EDNS0_4096_D_KN)
  • ru/SOA: The TCP connection was interrupted (ECONNRESET). See RFC 1035, Sec. 4.2. (194.85.252.62, 2001:678:16:0:194:85:252:62, TCP_-_EDNS0_4096_D_N)
  • ru/SOA: There was an error communicating with the server over TCP (UNKNOWN). See RFC 1035, Sec. 4.2. (193.232.128.6, 2001:678:17:0:193:232:128:6, TCP_-_EDNS0_4096_D_N)
  • ru/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • ru/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • awgdty58fm.ru/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
  • ru/NS: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (193.232.156.17, 194.190.124.17, UDP_-_EDNS0_4096_D_KN)
  • ru/NSEC3PARAM: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (2001:678:14:0:193:232:156:17, UDP_-_EDNS0_4096_D_KN)
  • ru/SOA: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (193.232.156.17, UDP_-_EDNS0_4096_D_KN_0x20)
  • ru/SOA: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (194.190.124.17, UDP_-_EDNS0_4096_D_KN)
  • awgdty58fm.ru/A has warnings; select the "Denial of existence" DNSSEC option to see them.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph