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 (12)
  • medlineplus.awsprod.nlm.nih.gov/A
  • medlineplus.awsprod.nlm.nih.gov/A
  • 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 (11)
  • medlineplus.gov/CNAME
  • medlineplus.gov/MX
  • medlineplus.gov/NS
  • medlineplus.gov/NSEC3PARAM
  • medlineplus.gov/NSEC3PARAM
  • medlineplus.gov/NSEC3PARAM
  • medlineplus.gov/NSEC3PARAM
  • medlineplus.gov/NSEC3PARAM
  • medlineplus.gov/SOA
  • medlineplus.gov/TXT
  • nlm.nih.gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (23)
  • ./DNSKEY (alg 8, id 11019)
  • ./DNSKEY (alg 8, id 20326)
  • NSEC proving non-existence of awsprod.nlm.nih.gov/DS
  • gov/DNSKEY (alg 8, id 40921)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • medlineplus.gov/DNSKEY (alg 8, id 56703)
  • medlineplus.gov/DNSKEY (alg 8, id 58792)
  • medlineplus.gov/DS (alg 8, id 58792)
  • nih.gov/DNSKEY (alg 8, id 32209)
  • nih.gov/DNSKEY (alg 8, id 32751)
  • nih.gov/DNSKEY (alg 8, id 37398)
  • nih.gov/DNSKEY (alg 8, id 55230)
  • nih.gov/DNSKEY (alg 8, id 59659)
  • nih.gov/DS (alg 8, id 32209)
  • nih.gov/DS (alg 8, id 32209)
  • nih.gov/DS (alg 8, id 59659)
  • nih.gov/DS (alg 8, id 59659)
  • nlm.nih.gov/DNSKEY (alg 8, id 18450)
  • nlm.nih.gov/DNSKEY (alg 8, id 49585)
  • nlm.nih.gov/DNSKEY (alg 8, id 57904)
  • nlm.nih.gov/DS (alg 8, id 22726)
  • nlm.nih.gov/DS (alg 8, id 49585)
Non_existent (1)
  • nlm.nih.gov/DNSKEY (alg 8, id 22726)

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 (6)
  • medlineplus.gov/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (130.14.252.50, 130.14.252.53, 2607:f220:41e:252::50, 2607:f220:41e:252::53, UDP_-_EDNS0_512_D_KN)
  • nih.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (128.231.64.1, 2607:f220:418:4101::80e7:401)
  • nlm.nih.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (128.231.64.1, 2607:f220:418:4101::80e7:401)
  • medlineplus.gov/CNAME 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.
  • ytju5i2w8k.medlineplus.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (14)
  • 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 from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (130.14.252.50, 130.14.252.53, 2607:f220:41e:252::50, 2607:f220:41e:252::53, 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 59659): 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 59659): 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 59659): 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 59659): 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/CNAME 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