View on GitHub

DNSViz: A DNS visualization tool

time.nist.gov

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

RRset statusRRset status

Insecure (7)
  • ntp1.glb.nist.gov/A
  • ntp1.glb.nist.gov/A
  • ntp1.glb.nist.gov/A
  • ntp1.glb.nist.gov/AAAA
  • ntp1.glb.nist.gov/AAAA
  • ntp1.glb.nist.gov/AAAA
  • time.nist.gov/CNAME
Secure (1)
  • gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (4)
  • glb.nist.gov/DNSKEY (alg 7, id 36380)
  • glb.nist.gov/DNSKEY (alg 7, id 4395)
  • glb.nist.gov/DNSKEY (alg 7, id 54395)
  • glb.nist.gov/DS (alg 7, id 4395)
Secure (6)
  • ./DNSKEY (alg 8, id 14631)
  • ./DNSKEY (alg 8, id 20326)
  • NSEC3 proving non-existence of nist.gov/DS
  • gov/DNSKEY (alg 8, id 48498)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)

Delegation statusDelegation status

Insecure (1)
  • gov to nist.gov
Secure (2)
  • . to gov
  • nist.gov to glb.nist.gov

NoticesNotices

Errors (10)
  • NSEC3 proving non-existence of nist.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of nist.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • glb.nist.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2610:20:6005:13::8)
  • glb.nist.gov/DS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (129.6.13.4, UDP_-_EDNS0_4096_D_KN)
  • nist.gov zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (129.6.13.4)
  • nist.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2610:20:6005:13::3, 2610:20:6005:13::4)
  • nist.gov/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (129.6.13.4, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • time.nist.gov/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (129.6.13.4, UDP_-_EDNS0_4096_D_KN)
  • time.nist.gov/AAAA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (129.6.13.4, UDP_-_EDNS0_4096_D_KN)
  • nist.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (35)
  • NSEC3 proving non-existence of nist.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of nist.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • RRSIG glb.nist.gov/DNSKEY alg 7, id 36380: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG glb.nist.gov/DNSKEY alg 7, id 36380: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG glb.nist.gov/DNSKEY alg 7, id 36380: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG glb.nist.gov/DNSKEY alg 7, id 36380: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG glb.nist.gov/DNSKEY alg 7, id 36380: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG glb.nist.gov/DNSKEY alg 7, id 36380: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG glb.nist.gov/DNSKEY alg 7, id 4395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG glb.nist.gov/DNSKEY alg 7, id 4395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG glb.nist.gov/DNSKEY alg 7, id 4395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG glb.nist.gov/DNSKEY alg 7, id 4395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG glb.nist.gov/DNSKEY alg 7, id 4395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG glb.nist.gov/DNSKEY alg 7, id 4395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG glb.nist.gov/DNSKEY alg 7, id 54395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG glb.nist.gov/DNSKEY alg 7, id 54395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG glb.nist.gov/DNSKEY alg 7, id 54395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG glb.nist.gov/DNSKEY alg 7, id 54395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG glb.nist.gov/DNSKEY alg 7, id 54395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG glb.nist.gov/DNSKEY alg 7, id 54395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ntp1.glb.nist.gov/A alg 7, id 36380: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ntp1.glb.nist.gov/A alg 7, id 36380: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ntp1.glb.nist.gov/A alg 7, id 36380: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ntp1.glb.nist.gov/A alg 7, id 54395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ntp1.glb.nist.gov/A alg 7, id 54395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ntp1.glb.nist.gov/A alg 7, id 54395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ntp1.glb.nist.gov/AAAA alg 7, id 36380: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ntp1.glb.nist.gov/AAAA alg 7, id 36380: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ntp1.glb.nist.gov/AAAA alg 7, id 36380: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ntp1.glb.nist.gov/AAAA alg 7, id 54395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ntp1.glb.nist.gov/AAAA alg 7, id 54395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ntp1.glb.nist.gov/AAAA alg 7, id 54395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • glb.nist.gov/DS (alg 7, id 4395): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • glb.nist.gov/DS (alg 7, id 4395): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov to nist.gov: AAAA glue records exist for gea2.nist.gov, but there are no corresponding authoritative AAAA records. 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