View on GitHub

DNSViz: A DNS visualization tool

pubmed.gov

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

RRset statusRRset 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 statusDNSKEY/DS/NSEC status

Secure (12)
  • ./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 7, id 24249)
  • pubmed.gov/DNSKEY (alg 7, id 59408)
  • pubmed.gov/DNSKEY (alg 8, id 44016)
  • pubmed.gov/DNSKEY (alg 8, id 45670)
  • pubmed.gov/DS (alg 7, id 24249)
  • pubmed.gov/DS (alg 7, id 24249)
  • pubmed.gov/DS (alg 8, id 45670)

Delegation statusDelegation status

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

NoticesNotices

Errors (3)
  • pubmed.gov/MX: No response was received from the server over UDP (tried 15 times). See RFC 1035, Sec. 4.2. (2607:f220:41e:7055::72, UDP_-_EDNS0_4096_D_KN)
  • 7jwaor9i2m.pubmed.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • pubmed.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (38)
  • RRSIG pubmed.gov/A alg 7, id 59408: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG pubmed.gov/AAAA alg 7, id 59408: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG pubmed.gov/DNSKEY alg 7, id 24249: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG pubmed.gov/DNSKEY alg 7, id 24249: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG pubmed.gov/DNSKEY alg 7, id 24249: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG pubmed.gov/DNSKEY alg 7, id 24249: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG pubmed.gov/DNSKEY alg 7, id 59408: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG pubmed.gov/DNSKEY alg 7, id 59408: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG pubmed.gov/DNSKEY alg 7, id 59408: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG pubmed.gov/DNSKEY alg 7, id 59408: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG pubmed.gov/MX alg 7, id 59408: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG pubmed.gov/NS alg 7, id 59408: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG pubmed.gov/NSEC3PARAM alg 7, id 59408: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG pubmed.gov/SOA alg 7, id 59408: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG pubmed.gov/TXT alg 7, id 59408: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • 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/DNSKEY (alg 7, id 24249): 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/DNSKEY (alg 7, id 59408): 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/DNSKEY (alg 8, id 44016): 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/DNSKEY (alg 8, id 45670): 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/DS (alg 7, id 24249): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • pubmed.gov/DS (alg 7, id 24249): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • pubmed.gov/DS (alg 7, id 24249): 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.
  • pubmed.gov/DS (alg 7, id 24249): 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.
  • 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.
  • pubmed.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 7jwaor9i2m.pubmed.gov/A 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