View on GitHub

DNSViz: A DNS visualization tool

nnss.gov

« 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 (4)
  • nnss.gov/A
  • nnss.gov/NS
  • nnss.gov/SOA
  • nnss.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (13)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26838)
  • gov/DNSKEY (alg 8, id 57735)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • nnss.gov/DNSKEY (alg 8, id 38944)
  • nnss.gov/DNSKEY (alg 8, id 41932)
  • nnss.gov/DNSKEY (alg 8, id 6084)
  • nnss.gov/DNSKEY (alg 8, id 6298)
  • nnss.gov/DS (alg 8, id 38944)
  • nnss.gov/DS (alg 8, id 38944)
  • nnss.gov/DS (alg 8, id 41932)
  • nnss.gov/DS (alg 8, id 41932)

Delegation statusDelegation status

Secure (2)
  • . to gov
  • gov to nnss.gov

NoticesNotices

Errors (7)
  • nnss.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2607:2080:0:2::320, 2607:2080:0:2::400)
  • nnss.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:2080:0:2::320, 2607:2080:0:2::400, UDP_-_NOEDNS_)
  • nnss.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:2080:0:2::320, 2607:2080:0:2::400, UDP_-_NOEDNS_)
  • nnss.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • 3mxlg4to1c.nnss.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • nnss.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • nnss.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
  • gov/DS (alg 8, id 7698): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (192.5.5.241, 2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • gov/DS (alg 8, id 7698): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (192.5.5.241, 2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
  • nnss.gov/DS (alg 8, id 38944): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • nnss.gov/DS (alg 8, id 38944): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • nnss.gov/DS (alg 8, id 38944): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • nnss.gov/DS (alg 8, id 38944): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • nnss.gov/DS (alg 8, id 41932): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • nnss.gov/DS (alg 8, id 41932): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • nnss.gov/DS (alg 8, id 41932): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • nnss.gov/DS (alg 8, id 41932): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.

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