nnlm.gov
Updated:
2022-03-17 16:39:20 UTC (981 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- nnlm.gov/A
- nnlm.gov/NS
- nnlm.gov/NSEC3PARAM
- nnlm.gov/SOA
- nnlm.gov/TXT
DNSKEY/DS/NSEC status
Secure (9)
- ./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)
- nnlm.gov/DNSKEY (alg 7, id 13854)
- nnlm.gov/DNSKEY (alg 7, id 60353)
- nnlm.gov/DS (alg 7, id 13854)
- nnlm.gov/DS (alg 7, id 13854)
Delegation status
Secure (2)
- . to gov
- gov to nnlm.gov
Notices
Errors (4)
- nnlm.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- 275og8ykz3.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 (28)
- RRSIG nnlm.gov/A alg 7, id 60353: 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 13854: 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 13854: 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 60353: 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 60353: 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 60353: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG nnlm.gov/NSEC3PARAM alg 7, id 60353: 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 60353: 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 60353: 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 to nnlm.gov: Authoritative AAAA records exist for ns.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 ns2.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 ns3.nih.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- 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_KN)
- nnlm.gov/DS (alg 7, id 13854): 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 13854): 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 13854): 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 13854): 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_KN)
- nnlm.gov/NSEC3PARAM: 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)
- 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_KN, UDP_-_EDNS0_4096_D_KN_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_KN)
- nnlm.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- 275og8ykz3.nnlm.gov/A 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.
- 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.
JavaScript is required to make the graph below interactive.
