View on GitHub

DNSViz: A DNS visualization tool

yaxim.org

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

RRset statusRRset status

Secure (5)
  • yaxim.org/A
  • yaxim.org/AAAA
  • yaxim.org/MX
  • yaxim.org/NS
  • yaxim.org/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (9)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 42351)
  • org/DNSKEY (alg 8, id 26974)
  • org/DNSKEY (alg 8, id 34266)
  • org/DNSKEY (alg 8, id 63858)
  • org/DS (alg 8, id 26974)
  • yaxim.org/DNSKEY (alg 8, id 42199)
  • yaxim.org/DNSKEY (alg 8, id 6384)
  • yaxim.org/DS (alg 8, id 42199)

Delegation statusDelegation status

Secure (2)
  • . to org
  • org to yaxim.org

NoticesNotices

Errors (3)
  • yaxim.org zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (69.36.225.255)
  • yaxim.org/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (69.36.225.255, UDP_-_NOEDNS_)
  • yaxim.org/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (69.36.225.255, UDP_-_NOEDNS_)
Warnings (2)
  • org to yaxim.org: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the org zone): ns2.afraid.org See RFC 1034, Sec. 4.2.2.
  • org to yaxim.org: The following NS name(s) were found in the delegation NS RRset (i.e., in the org zone), but not in the authoritative NS RRset: ns.layer42.net See RFC 1034, Sec. 4.2.2.

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