View on GitHub

DNSViz: A DNS visualization tool

cctld.ru

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

RRset statusRRset status

Bogus (6)
  • cctld.ru/A
  • cctld.ru/MX
  • cctld.ru/NS
  • cctld.ru/SOA
  • cctld.ru/TXT
  • ru/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (1)
  • NSEC3 proving non-existence of cctld.ru/DS
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

Insecure (1)
  • ru to cctld.ru
Secure (1)
  • . to ru

NoticesNotices

Errors (8)
  • RRSIG NSEC3 proving non-existence of cctld.ru/DS alg 8, id 52263: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG NSEC3 proving non-existence of cctld.ru/DS 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.
  • cctld.ru/DS: The TCP connection was interrupted (ECONNRESET). See RFC 1035, Sec. 4.2. (193.232.128.6, TCP_-_EDNS0_4096_D_N)
  • ru zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (193.232.156.17)
  • ru/DNSKEY: No response was received from the server over TCP (tried 1 times). See RFC 1035, Sec. 4.2. (193.232.156.17, TCP_-_EDNS0_4096_D_KN)
  • ru/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (193.232.142.17, UDP_-_EDNS0_512_D_KN)
  • cctld.ru/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
  • ru to cctld.ru: 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.142.17, UDP_-_EDNS0_4096_D_KN)
  • ru to cctld.ru: 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.85.252.62, UDP_-_EDNS0_4096_D_KN)
  • ru/DNSKEY (alg 8, id 43786): 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.142.17, UDP_-_EDNS0_4096_D_KN)
  • ru/DNSKEY (alg 8, id 44301): 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.142.17, UDP_-_EDNS0_4096_D_KN)
  • ru/DNSKEY (alg 8, id 52263): 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.142.17, UDP_-_EDNS0_4096_D_KN)
  • cctld.ru/DS 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