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 (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

Bogus (2)
  • nlm.gov/DNSKEY (alg 8, id 13315)
  • nlm.gov/DNSKEY (alg 8, id 40225)
Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 47671)
  • ./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 48901)
Non_existent (1)
  • nlm.gov/DNSKEY (alg 7, id 48901)

Delegation statusDelegation status

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

NoticesNotices

Errors (17)
  • 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. (128.231.64.1, 128.231.128.251, 130.14.55.72, 130.14.55.128, 165.112.4.230, 2607:f220:41e:7055::72, 2607:f220:41e:7055::128, 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. (128.231.64.1, 128.231.128.251, 130.14.55.72, 130.14.55.128, 165.112.4.230, 2607:f220:41e:7055::72, 2607:f220:41e:7055::128, UDP_-_EDNS0_4096_D_KN)
  • nlm.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2607:f220:402:1801::a570:4e6, 2607:f220:404:101::80e7:80fb, 2607:f220:418:4101::80e7:401)
  • nlm.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:f220:402:1801::a570:4e6, 2607:f220:404:101::80e7:80fb, 2607:f220:418:4101::80e7:401, UDP_-_NOEDNS_)
  • nlm.gov/A: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (128.231.64.1, 128.231.128.251, 130.14.55.72, 130.14.55.128, 165.112.4.230, 2607:f220:41e:7055::72, 2607:f220:41e:7055::128, UDP_-_EDNS0_4096_D_KN)
  • nlm.gov/AAAA: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (128.231.64.1, 128.231.128.251, 130.14.55.72, 130.14.55.128, 165.112.4.230, 2607:f220:41e:7055::72, 2607:f220:41e:7055::128, UDP_-_EDNS0_4096_D_KN)
  • nlm.gov/DNSKEY (alg 8, id 13315): The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (128.231.64.1, 128.231.128.251, 130.14.55.72, 130.14.55.128, 165.112.4.230, 2607:f220:41e:7055::72, 2607:f220:41e:7055::128, UDP_-_EDNS0_4096_D_KN)
  • nlm.gov/DNSKEY (alg 8, id 40225): The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (128.231.64.1, 128.231.128.251, 130.14.55.72, 130.14.55.128, 165.112.4.230, 2607:f220:41e:7055::72, 2607:f220:41e:7055::128, UDP_-_EDNS0_4096_D_KN)
  • nlm.gov/MX: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (128.231.64.1, 128.231.128.251, 130.14.55.72, 130.14.55.128, 165.112.4.230, 2607:f220:41e:7055::72, 2607:f220:41e:7055::128, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • nlm.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:f220:402:1801::a570:4e6, 2607:f220:404:101::80e7:80fb, 2607:f220:418:4101::80e7:401, UDP_-_NOEDNS_)
  • nlm.gov/NS: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (128.231.64.1, 128.231.128.251, 130.14.55.72, 130.14.55.128, 165.112.4.230, 2607:f220:41e:7055::72, 2607:f220:41e:7055::128, UDP_-_EDNS0_4096_D_KN)
  • nlm.gov/SOA: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (128.231.64.1, 128.231.128.251, 130.14.55.72, 130.14.55.128, 165.112.4.230, 2607:f220:41e:7055::72, 2607:f220:41e:7055::128, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • nlm.gov/TXT: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (128.231.64.1, 128.231.128.251, 130.14.55.72, 130.14.55.128, 165.112.4.230, 2607:f220:41e:7055::72, 2607:f220:41e:7055::128, UDP_-_EDNS0_4096_D_KN)
  • nlm.gov/DNSKEY 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.
  • mj5708hypr.nlm.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • nlm.gov/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (9)
  • 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 to nlm.gov: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the gov zone): ns.nih.gov, ns2.nih.gov, ns3.nih.gov See RFC 1034, Sec. 4.2.2.
  • nlm.gov/A: 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/AAAA: 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/MX: 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/NS: 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/SOA: 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, UDP_-_EDNS0_4096_D_KN_0x20)
  • nlm.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:41e:7055::72, 2607:f220:41e:7055::128, UDP_-_EDNS0_4096_D_KN)

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