View on GitHub

DNSViz: A DNS visualization tool

medlineplus.gov

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

RRset statusRRset status

Insecure (10)
  • medlineplus.awsprod.nlm.nih.gov/A
  • medlineplus.awsprod.nlm.nih.gov/A
  • medlineplus.awsprod.nlm.nih.gov/AAAA
  • medlineplus.awsprod.nlm.nih.gov/AAAA
  • medlineplus.awsprod.nlm.nih.gov/AAAA
  • medlineplus.awsprod.nlm.nih.gov/AAAA
  • medlineplus.awsprod.nlm.nih.gov/AAAA
  • medlineplus.awsprod.nlm.nih.gov/AAAA
  • medlineplus.awsprod.nlm.nih.gov/AAAA
  • medlineplus.awsprod.nlm.nih.gov/AAAA
Secure (6)
  • medlineplus.gov/CNAME
  • medlineplus.gov/MX
  • medlineplus.gov/NS
  • medlineplus.gov/SOA
  • medlineplus.gov/TXT
  • nlm.nih.gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (19)
  • ./DNSKEY (alg 8, id 14631)
  • ./DNSKEY (alg 8, id 20326)
  • NSEC3 proving non-existence of awsprod.nlm.nih.gov/DS
  • gov/DNSKEY (alg 8, id 27306)
  • gov/DNSKEY (alg 8, id 48498)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • medlineplus.gov/DNSKEY (alg 7, id 24081)
  • medlineplus.gov/DNSKEY (alg 7, id 45128)
  • medlineplus.gov/DS (alg 7, id 24081)
  • medlineplus.gov/DS (alg 7, id 24081)
  • nih.gov/DNSKEY (alg 7, id 35355)
  • nih.gov/DNSKEY (alg 7, id 56039)
  • nih.gov/DNSKEY (alg 7, id 6318)
  • nih.gov/DS (alg 7, id 35355)
  • nih.gov/DS (alg 7, id 6318)
  • nlm.nih.gov/DNSKEY (alg 7, id 51512)
  • nlm.nih.gov/DNSKEY (alg 7, id 51763)
  • nlm.nih.gov/DS (alg 7, id 51763)

Delegation statusDelegation 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

NoticesNotices

Errors (4)
  • NSEC3 proving non-existence of awsprod.nlm.nih.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of awsprod.nlm.nih.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • t8k49wqmxy.medlineplus.gov/A 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 (73)
  • RRSIG NSEC3 proving non-existence of awsprod.nlm.nih.gov/DS alg 7, id 51512: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/CNAME alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/CNAME alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/CNAME alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/CNAME alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/CNAME alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/CNAME alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/CNAME alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/DNSKEY alg 7, id 24081: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/DNSKEY alg 7, id 24081: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/DNSKEY alg 7, id 24081: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/DNSKEY alg 7, id 24081: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/DNSKEY alg 7, id 24081: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/DNSKEY alg 7, id 24081: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/DNSKEY alg 7, id 24081: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/DNSKEY alg 7, id 24081: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/DNSKEY alg 7, id 24081: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/DNSKEY alg 7, id 24081: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/DNSKEY alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/DNSKEY alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/DNSKEY alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/DNSKEY alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/DNSKEY alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/DNSKEY alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/DNSKEY alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/DNSKEY alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/DNSKEY alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/DNSKEY alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/MX alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/MX alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/MX alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/MX alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/MX alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/NS alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/NS alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/NS alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/SOA alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/SOA alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/SOA alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/SOA alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/SOA alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/TXT alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/TXT alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG medlineplus.gov/TXT alg 7, id 45128: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 35355: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 35355: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 35355: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 56039: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 56039: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 56039: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 6318: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 6318: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nih.gov/DNSKEY alg 7, id 6318: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nlm.nih.gov/DNSKEY alg 7, id 51512: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nlm.nih.gov/DNSKEY alg 7, id 51512: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nlm.nih.gov/DNSKEY alg 7, id 51763: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nlm.nih.gov/DNSKEY alg 7, id 51763: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nlm.nih.gov/DS alg 7, id 56039: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nlm.nih.gov/SOA alg 7, id 51512: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • gov to medlineplus.gov: Authoritative AAAA records exist for gslb01.nlm.nih.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • gov to medlineplus.gov: Authoritative AAAA records exist for gslb02.nlm.nih.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • gov to medlineplus.gov: Authoritative AAAA records exist for gslb03.nlm.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/DS (alg 7, id 24081): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • medlineplus.gov/DS (alg 7, id 24081): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • medlineplus.gov/DS (alg 7, id 24081): 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.
  • medlineplus.gov/DS (alg 7, id 24081): 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/DNSKEY (alg 7, id 35355): 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:404:101::80e7:80fb, 2607:f220:418:4101::80e7:401, UDP_-_EDNS0_4096_D_KN)
  • nih.gov/DNSKEY (alg 7, id 56039): 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:404:101::80e7:80fb, 2607:f220:418:4101::80e7:401, UDP_-_EDNS0_4096_D_KN)
  • nih.gov/DNSKEY (alg 7, id 6318): 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:404:101::80e7:80fb, 2607:f220:418:4101::80e7:401, UDP_-_EDNS0_4096_D_KN)
  • medlineplus.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • medlineplus.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • t8k49wqmxy.medlineplus.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