nlm.gov
Updated:
2020-08-20 15:18:36 UTC (1556 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- nlm.gov/A
- nlm.gov/AAAA
- nlm.gov/MX
- nlm.gov/NS
- nlm.gov/SOA
- nlm.gov/TXT
DNSKEY/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)
- nlm.gov/DNSKEY (alg 7, id 45658)
- nlm.gov/DNSKEY (alg 7, id 63212)
- nlm.gov/DS (alg 7, id 45658)
- nlm.gov/DS (alg 7, id 45658)
Delegation status
Secure (2)
- . to gov
- gov to nlm.gov
Notices
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_K, 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_K, 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.
- nlm.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- w5d97lvr0h.nlm.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (23)
- RRSIG nlm.gov/A alg 7, id 63212: 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 63212: 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 63212: 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 63212: 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 63212: 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 63212: 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 63212: 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 63212: 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/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.
- w5d97lvr0h.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.
JavaScript is required to make the graph below interactive.
