View on GitHub

DNSViz: A DNS visualization tool

nnlm.gov

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

RRset statusRRset status

Secure (4)
  • nnlm.gov/A
  • nnlm.gov/NS
  • nnlm.gov/SOA
  • nnlm.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46594)
  • gov/DNSKEY (alg 8, id 26665)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • nnlm.gov/DNSKEY (alg 7, id 11102)
  • nnlm.gov/DNSKEY (alg 7, id 36279)
  • nnlm.gov/DS (alg 7, id 36279)
  • nnlm.gov/DS (alg 7, id 36279)

Delegation statusDelegation status

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

NoticesNotices

Errors (9)
  • nnlm.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (165.112.4.230, 2607:f220:402:1801::a570:4e6)
  • nnlm.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2607:f220:418:4101::80e7:401)
  • nnlm.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:f220:418:4101::80e7:401, UDP_-_EDNS0_4096_D_K)
  • nnlm.gov/NS: No response was received from the server over UDP (tried 15 times). See RFC 1035, Sec. 4.2. (2607:f220:418:4101::80e7:401, UDP_-_EDNS0_4096_D)
  • nnlm.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (165.112.4.230, 2607:f220:402:1801::a570:4e6, TCP_-_EDNS0_4096_D)
  • nnlm.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • 485gterkjb.nnlm.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • nnlm.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • nnlm.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (27)
  • RRSIG nnlm.gov/A alg 7, id 11102: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nnlm.gov/DNSKEY alg 7, id 11102: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nnlm.gov/DNSKEY alg 7, id 11102: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nnlm.gov/DNSKEY alg 7, id 36279: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nnlm.gov/DNSKEY alg 7, id 36279: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nnlm.gov/NS alg 7, id 11102: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nnlm.gov/SOA alg 7, id 11102: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nnlm.gov/TXT alg 7, id 11102: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • gov to nnlm.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 nnlm.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.
  • nnlm.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_K)
  • nnlm.gov/DS (alg 7, id 36279): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • nnlm.gov/DS (alg 7, id 36279): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • nnlm.gov/DS (alg 7, id 36279): 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.
  • nnlm.gov/DS (alg 7, id 36279): 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.
  • nnlm.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_K)
  • nnlm.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_K, UDP_-_EDNS0_4096_D_K_0x20)
  • nnlm.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_K)
  • nnlm.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • nnlm.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 485gterkjb.nnlm.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • nnlm.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • nnlm.gov/MX 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