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

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

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 14631)
  • ./DNSKEY (alg 8, id 20326)
  • gov/DNSKEY (alg 8, id 27306)
  • gov/DNSKEY (alg 8, id 48498)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • nih.gov/DNSKEY (alg 7, id 35355)
  • nih.gov/DNSKEY (alg 7, id 56039)
  • nih.gov/DNSKEY (alg 7, id 6318)
  • nih.gov/DS (alg 7, id 35355)
  • nih.gov/DS (alg 7, id 6318)

Delegation statusDelegation status

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

NoticesNotices

Errors (5)
  • ./DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:7fe::53, UDP_-_NOEDNS_)
  • ./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2001:7fe::53, UDP_-_EDNS0_512_D_KN)
  • nih.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • atin4oxkj3.nih.gov/A 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 (22)
  • 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 35355: 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 35355: 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 35355: 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 6318: 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 6318: 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 6318: 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 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 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 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 35355): 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 6318): 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.
  • atin4oxkj3.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