View on GitHub

DNSViz: A DNS visualization tool

nih.gov

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

RRset statusRRset status

Bogus (5)
  • nih.gov/A
  • nih.gov/MX
  • nih.gov/NS
  • nih.gov/SOA
  • nih.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (6)
  • nih.gov/DNSKEY (alg 7, id 10907)
  • nih.gov/DNSKEY (alg 7, id 2264)
  • nih.gov/DNSKEY (alg 7, id 35669)
  • nih.gov/DNSKEY (alg 7, id 51573)
  • nih.gov/DNSKEY (alg 7, id 56039)
  • nih.gov/DNSKEY (alg 7, id 58971)
Secure (7)
  • ./DNSKEY (alg 8, id 14631)
  • ./DNSKEY (alg 8, id 20326)
  • gov/DNSKEY (alg 8, id 48498)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • nih.gov/DS (alg 7, id 35355)
  • nih.gov/DS (alg 7, id 6318)
Non_existent (2)
  • nih.gov/DNSKEY (alg 7, id 35355)
  • nih.gov/DNSKEY (alg 7, id 6318)

Delegation statusDelegation status

Bogus (1)
  • gov to nih.gov
Secure (1)
  • . to gov

NoticesNotices

Errors (7)
  • gov to nih.gov: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (128.231.64.1, 128.231.128.251, 165.112.4.230, 2607:f220:402:1801::a570:4e6, 2607:f220:404:101::80e7:80fb, 2607:f220:418:4101::80e7:401, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
  • gov to nih.gov: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no DS RR matched a DNSKEY with algorithm 7 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (128.231.64.1, 128.231.128.251, 165.112.4.230, 2607:f220:402:1801::a570:4e6, 2607:f220:404:101::80e7:80fb, 2607:f220:418:4101::80e7:401, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
  • nih.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (128.231.64.1, 165.112.4.230)
  • nih.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (128.231.64.1, 165.112.4.230, TCP_-_EDNS0_4096_D_N)
  • c9wsjxm0v6.nih.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • nih.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • nih.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (67)
  • RRSIG nih.gov/A alg 7, id 10907: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/A alg 7, id 2264: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/A alg 7, id 35669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/A alg 7, id 56039: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 10907: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 10907: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 10907: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 10907: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 10907: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 10907: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 2264: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 2264: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 2264: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 2264: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 2264: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 2264: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 35669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 35669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 35669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 35669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 35669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 35669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 51573: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 51573: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 51573: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 51573: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 51573: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 51573: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 56039: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 56039: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 56039: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 56039: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 56039: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 56039: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 58971: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 58971: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 58971: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 58971: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 58971: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 58971: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/MX alg 7, id 10907: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/MX alg 7, id 2264: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/MX alg 7, id 35669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/MX alg 7, id 56039: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/NS alg 7, id 10907: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/NS alg 7, id 2264: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/NS alg 7, id 35669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/NS alg 7, id 56039: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/SOA alg 7, id 10907: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/SOA alg 7, id 2264: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/SOA alg 7, id 35669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/SOA alg 7, id 56039: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/TXT alg 7, id 10907: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/TXT alg 7, id 2264: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/TXT alg 7, id 35669: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/TXT alg 7, id 56039: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • nih.gov/DNSKEY (alg 7, id 10907): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2607:f220:404:101::80e7:80fb, 2607:f220:418:4101::80e7:401, UDP_-_EDNS0_4096_D_KN)
  • nih.gov/DNSKEY (alg 7, id 2264): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2607:f220:404:101::80e7:80fb, 2607:f220:418:4101::80e7:401, UDP_-_EDNS0_4096_D_KN)
  • nih.gov/DNSKEY (alg 7, id 35669): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2607:f220:404:101::80e7:80fb, 2607:f220:418:4101::80e7:401, UDP_-_EDNS0_4096_D_KN)
  • nih.gov/DNSKEY (alg 7, id 51573): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2607:f220:404:101::80e7:80fb, 2607:f220:418:4101::80e7:401, UDP_-_EDNS0_4096_D_KN)
  • nih.gov/DNSKEY (alg 7, id 56039): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2607:f220:404:101::80e7:80fb, 2607:f220:418:4101::80e7:401, UDP_-_EDNS0_4096_D_KN)
  • nih.gov/DNSKEY (alg 7, id 58971): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2607:f220:404:101::80e7:80fb, 2607:f220:418:4101::80e7:401, UDP_-_EDNS0_4096_D_KN)
  • nih.gov/TXT: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2607:f220:404:101::80e7:80fb, 2607:f220:418:4101::80e7:401, UDP_-_EDNS0_4096_D_KN)
  • nih.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • nih.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • c9wsjxm0v6.nih.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • nih.gov/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