View on GitHub

DNSViz: A DNS visualization tool

zapaname.us

« 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 (1)
  • us/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20038)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 61050)
  • NSEC3 proving non-existence of zapaname.us/DS
  • us/DNSKEY (alg 8, id 54159)
  • us/DNSKEY (alg 8, id 59017)
  • us/DS (alg 8, id 59017)

Delegation statusDelegation status

Lame (1)
  • us to zapaname.us
Secure (1)
  • . to us

NoticesNotices

Errors (4)
  • zapaname.us zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (35.208.110.23, 35.209.100.171)
  • zapaname.us zone: There was an error resolving the following NS name(s) to address(es): ns1.zapaname.us, ns2.zapaname.us
  • zapaname.us/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (35.208.110.23, 35.209.100.171, UDP_-_NOEDNS_)
  • zapaname.us/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (35.208.110.23, 35.209.100.171, UDP_-_NOEDNS_)

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