View on GitHub

DNSViz: A DNS visualization tool

www.example.com

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

RRset statusRRset status

Secure (2)
  • www.example.com/A
  • www.example.com/AAAA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (9)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 46551)
  • com/DS (alg 8, id 30909)
  • example.com/DNSKEY (alg 13, id 370)
  • example.com/DNSKEY (alg 13, id 44029)
  • example.com/DNSKEY (alg 13, id 8701)
  • example.com/DS (alg 13, id 370)

Delegation statusDelegation status

Secure (2)
  • . to com
  • com to example.com

NoticesNotices

Errors (8)
  • example.com/DS (alg 13, id 370): 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. (192.5.6.30, 192.12.94.30, 192.31.80.30, UDP_-_EDNS0_4096_)
  • example.com/DS (alg 13, id 370): 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. (192.5.6.30, 192.12.94.30, 192.31.80.30, UDP_-_EDNS0_4096_)
  • example.com/DS (alg 13, id 370): 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. (192.5.6.30, 192.12.94.30, 192.31.80.30, UDP_-_EDNS0_4096_D_KN)
  • example.com/DS (alg 13, id 370): 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. (192.5.6.30, 192.12.94.30, 192.31.80.30, UDP_-_EDNS0_4096_D_KN)
  • example.com/DS (alg 13, id 370): 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. (192.5.6.30, 192.12.94.30, 192.31.80.30, UDP_-_EDNS0_4096_D_KN)
  • example.com/DS (alg 13, id 370): 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. (192.5.6.30, 192.12.94.30, 192.31.80.30, UDP_-_EDNS0_4096_D_KN)
  • example.com/DS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (192.26.92.30, UDP_-_NOEDNS_)
  • example.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (1)
  • example.com/CNAME 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