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 (3)
  • ru/NS
  • ru/NSEC3PARAM
  • 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 (8)
  • 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.
  • ru zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (193.232.128.6, 193.232.142.17, 2001:678:17:0:193:232:128:6)
  • ru/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (193.232.142.17, 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.
  • 9xkpen8bq6.ru/A has errors; 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