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

Bogus (7)
  • nlm.gov/A
  • nlm.gov/AAAA
  • nlm.gov/MX
  • nlm.gov/NS
  • nlm.gov/NSEC3PARAM
  • nlm.gov/SOA
  • nlm.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (3)
  • nlm.gov/DNSKEY (alg 7, id 2286)
  • nlm.gov/DNSKEY (alg 7, id 48901)
  • nlm.gov/DNSKEY (alg 7, id 513)
Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 9799)
  • gov/DNSKEY (alg 8, id 7030)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • nlm.gov/DS (alg 7, id 11374)
Non_existent (1)
  • nlm.gov/DNSKEY (alg 7, id 11374)

Delegation statusDelegation status

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

NoticesNotices

Errors (4)
  • gov to nlm.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. (130.14.55.72, 130.14.55.128, 2607:f220:41e:7055::72, 2607:f220:41e:7055::128, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
  • gov to nlm.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. (130.14.55.72, 130.14.55.128, 2607:f220:41e:7055::72, 2607:f220:41e:7055::128, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
  • 15g6qdizxv.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 (28)
  • RRSIG nlm.gov/A alg 7, id 513: 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 513: 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 2286: 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 2286: 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 2286: 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 48901: 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 48901: 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 48901: 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 513: 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 513: 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 513: 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 513: 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 513: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nlm.gov/NSEC3PARAM alg 7, id 513: 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 513: 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 513: 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.
  • nlm.gov/DNSKEY (alg 7, id 2286): 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 48901): 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 513): 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 11374): 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 11374): 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 11374): 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 11374): 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.
  • 15g6qdizxv.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