pubmed.gov
Updated:
2022-08-09 23:19:23 UTC (835 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (7)
- pubmed.gov/A
- pubmed.gov/AAAA
- pubmed.gov/MX
- pubmed.gov/NS
- pubmed.gov/NSEC3PARAM
- pubmed.gov/SOA
- pubmed.gov/TXT
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 20826)
- gov/DNSKEY (alg 8, id 261)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- pubmed.gov/DNSKEY (alg 8, id 44016)
- pubmed.gov/DNSKEY (alg 8, id 45670)
- pubmed.gov/DS (alg 8, id 45670)
Delegation status
Secure (2)
- . to gov
- gov to pubmed.gov
Notices
Errors (2)
- pubmed.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- v6d9wsxu15.pubmed.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (15)
- gov to pubmed.gov: Authoritative AAAA records exist for dns1-ncbi.ncbi.nlm.nih.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- gov to pubmed.gov: Authoritative AAAA records exist for dns2-ncbi.ncbi.nlm.nih.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- gov to pubmed.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 pubmed.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 pubmed.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 pubmed.gov: Authoritative AAAA records exist for ns3.nih.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- pubmed.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, UDP_-_EDNS0_4096_D_KN)
- pubmed.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, UDP_-_EDNS0_4096_D_KN)
- pubmed.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, UDP_-_EDNS0_4096_D_KN)
- pubmed.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, UDP_-_EDNS0_4096_D_KN)
- pubmed.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, UDP_-_EDNS0_4096_D_KN)
- pubmed.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, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- pubmed.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, UDP_-_EDNS0_4096_D_KN)
- pubmed.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- v6d9wsxu15.pubmed.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
