NSEC proving non-existence of awsprod.nlm.nih.gov/DS
gov/DNSKEY (alg 8, id 56278)
gov/DNSKEY (alg 8, id 7698)
gov/DS (alg 8, id 7698)
medlineplus.gov/DNSKEY (alg 8, id 41409)
medlineplus.gov/DNSKEY (alg 8, id 5749)
medlineplus.gov/DS (alg 8, id 5749)
nih.gov/DNSKEY (alg 8, id 32209)
nih.gov/DNSKEY (alg 8, id 36243)
nih.gov/DNSKEY (alg 8, id 37854)
nih.gov/DS (alg 8, id 32209)
nih.gov/DS (alg 8, id 32209)
nih.gov/DS (alg 8, id 57346)
nlm.nih.gov/DNSKEY (alg 8, id 22726)
nlm.nih.gov/DNSKEY (alg 8, id 41136)
nlm.nih.gov/DS (alg 8, id 22726)
Non_existent (1)
nih.gov/DNSKEY (alg 8, id 57346)
Delegation status
Insecure (1)
nlm.nih.gov to awsprod.nlm.nih.gov
Secure (4)
. to gov
gov to medlineplus.gov
gov to nih.gov
nih.gov to nlm.nih.gov
Notices
Errors (22)
medlineplus.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (130.14.252.50, 130.14.252.53, 165.112.6.3, 2607:f220:41f:1405::3)
medlineplus.gov/DNSKEY: No response was received from the server over UDP (tried 11 times). See RFC 1035, Sec. 4.2. (2607:f220:41e:252::53, UDP_-_EDNS0_4096_D_N)
medlineplus.gov/DNSKEY: No response was received from the server over UDP (tried 14 times). See RFC 1035, Sec. 4.2. (2607:f220:41e:252::50, UDP_-_EDNS0_4096_D_KN)
medlineplus.gov/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2607:f220:41e:252::53, UDP_-_EDNS0_512_D_KN)
medlineplus.gov/MX (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (165.112.6.3, UDP_-_EDNS0_4096_D_KN)
medlineplus.gov/MX (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (165.112.6.3, UDP_-_EDNS0_4096_D_KN)
medlineplus.gov/MX (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (165.112.6.3, UDP_-_EDNS0_4096_D_KN)
medlineplus.gov/MX: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:f220:41f:1405::3, TCP_-_EDNS0_4096_D_KN)
medlineplus.gov/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2607:f220:41e:252::53, UDP_-_EDNS0_512_D_KN)
medlineplus.gov/NS: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (165.112.6.3, 2607:f220:41f:1405::3, UDP_-_EDNS0_4096_D_KN)
medlineplus.gov/SOA (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (165.112.6.3, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
medlineplus.gov/SOA (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (165.112.6.3, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
medlineplus.gov/SOA (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (165.112.6.3, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
medlineplus.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (130.14.252.50, 130.14.252.53, 165.112.6.3, 2607:f220:41e:252::50, 2607:f220:41f:1405::3, TCP_-_EDNS0_4096_D_N)
medlineplus.gov/SOA: No response was received from the server over TCP (tried 7 times). See RFC 1035, Sec. 4.2. (2607:f220:41f:1405::3, TCP_-_EDNS0_4096_D_KN, TCP_-_EDNS0_4096_D_KN_0x20)
medlineplus.gov/TXT (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (165.112.6.3, UDP_-_EDNS0_4096_D_KN)
medlineplus.gov/TXT (NODATA): The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (165.112.6.3, UDP_-_EDNS0_4096_D_KN)
medlineplus.gov/TXT (NODATA): The NODATA response did not include an SOA record. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (165.112.6.3, UDP_-_EDNS0_4096_D_KN)
medlineplus.gov/TXT: No response was received from the server over TCP (tried 7 times). See RFC 1035, Sec. 4.2. (2607:f220:41f:1405::3, TCP_-_EDNS0_4096_D_KN)
mvepifak6h.medlineplus.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
medlineplus.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
medlineplus.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (17)
gov to nih.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 nih.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 nih.gov: Authoritative AAAA records exist for ns3.nih.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
medlineplus.gov/CNAME: The server returned CNAME for medlineplus.gov, but records of other types exist at that name. See RFC 2181, Sec. 10.1.
medlineplus.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:252::50, UDP_-_EDNS0_4096_D_KN)
medlineplus.gov/MX: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (165.112.6.3, 2607:f220:41f:1405::3, UDP_-_EDNS0_512_D_KN)
medlineplus.gov/NSEC3PARAM: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (2607:f220:41e:252::50, UDP_-_EDNS0_4096_D_KN)
nih.gov/DS (alg 8, id 32209): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
nih.gov/DS (alg 8, id 32209): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
nih.gov/DS (alg 8, id 32209): 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.
nih.gov/DS (alg 8, id 32209): 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.
nih.gov/DS (alg 8, id 57346): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
nih.gov/DS (alg 8, id 57346): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
nih.gov/DS (alg 8, id 57346): 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.
nih.gov/DS (alg 8, id 57346): 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.
mvepifak6h.medlineplus.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
medlineplus.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.