View on GitHub

DNSViz: A DNS visualization tool

nlm.gov

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

RRset statusRRset status

Secure (6)
  • nlm.gov/A
  • nlm.gov/AAAA
  • nlm.gov/MX
  • nlm.gov/NS
  • nlm.gov/SOA
  • nlm.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 42351)
  • gov/DNSKEY (alg 8, id 27306)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • nlm.gov/DNSKEY (alg 7, id 11374)
  • nlm.gov/DNSKEY (alg 7, id 17057)
  • nlm.gov/DNSKEY (alg 7, id 45658)
  • nlm.gov/DS (alg 7, id 45658)
  • nlm.gov/DS (alg 7, id 45658)

Delegation statusDelegation status

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

NoticesNotices

Errors (13)
  • nlm.gov zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (140.142.5.5, 2607:4000:200:42::5)
  • nlm.gov zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (140.142.5.5, 2607:4000:200:42::5)
  • nlm.gov/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (140.142.5.5, 2607:4000:200:42::5, UDP_-_NOEDNS_)
  • nlm.gov/AAAA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (140.142.5.5, 2607:4000:200:42::5, UDP_-_NOEDNS_)
  • nlm.gov/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (140.142.5.5, 2607:4000:200:42::5, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • nlm.gov/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (140.142.5.5, 2607:4000:200:42::5, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • nlm.gov/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (140.142.5.5, 2607:4000:200:42::5, UDP_-_NOEDNS_)
  • nlm.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (140.142.5.5, 2607:4000:200:42::5, TCP_-_NOEDNS_)
  • nlm.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (140.142.5.5, 2607:4000:200:42::5, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • nlm.gov/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (140.142.5.5, 2607:4000:200:42::5, UDP_-_NOEDNS_)
  • nlm.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • d72m3gneyz.nlm.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • nlm.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (31)
  • RRSIG nlm.gov/A alg 7, id 17057: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nlm.gov/AAAA alg 7, id 17057: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nlm.gov/DNSKEY alg 7, id 11374: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nlm.gov/DNSKEY alg 7, id 11374: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nlm.gov/DNSKEY alg 7, id 11374: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nlm.gov/DNSKEY alg 7, id 17057: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nlm.gov/DNSKEY alg 7, id 17057: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nlm.gov/DNSKEY alg 7, id 17057: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nlm.gov/DNSKEY alg 7, id 45658: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nlm.gov/DNSKEY alg 7, id 45658: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nlm.gov/DNSKEY alg 7, id 45658: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nlm.gov/MX alg 7, id 17057: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nlm.gov/NS alg 7, id 17057: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nlm.gov/SOA alg 7, id 17057: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nlm.gov/TXT alg 7, id 17057: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • gov to nlm.gov: Authoritative AAAA records exist for lhcns1.nlm.nih.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • gov to nlm.gov: Authoritative AAAA records exist for lhcns2.nlm.nih.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): 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.
  • gov/DS (alg 8, id 7698): 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.
  • nlm.gov/DNSKEY (alg 7, id 11374): 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:41e:7055::72, 2607:f220:41e:7055::128, UDP_-_EDNS0_4096_D_KN)
  • nlm.gov/DNSKEY (alg 7, id 17057): 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:41e:7055::72, 2607:f220:41e:7055::128, UDP_-_EDNS0_4096_D_KN)
  • nlm.gov/DNSKEY (alg 7, id 45658): 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:41e:7055::72, 2607:f220:41e:7055::128, UDP_-_EDNS0_4096_D_KN)
  • nlm.gov/DS (alg 7, id 45658): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • nlm.gov/DS (alg 7, id 45658): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • nlm.gov/DS (alg 7, id 45658): 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.
  • nlm.gov/DS (alg 7, id 45658): 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.
  • nlm.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • d72m3gneyz.nlm.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • nlm.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