View on GitHub

DNSViz: A DNS visualization tool

medlineplus.gov

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

RRset statusRRset status

Bogus (3)
  • medlineplus.gov/MX (NODATA)
  • medlineplus.gov/SOA (NODATA)
  • medlineplus.gov/TXT (NODATA)
Insecure (11)
  • 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 (18)
  • ./DNSKEY (alg 8, id 18733)
  • ./DNSKEY (alg 8, id 20326)
  • 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 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 (19)
  • medlineplus.gov zone: The server(s) were not responsive to queries over TCP. (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). (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). (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). (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. (165.112.6.3, UDP_-_EDNS0_4096_D_KN)
  • medlineplus.gov/MX (NODATA): No SOA RR was returned with the NODATA response. (165.112.6.3, UDP_-_EDNS0_4096_D_KN)
  • medlineplus.gov/MX (NODATA): The Authoritative Answer (AA) flag was not set in the response. (165.112.6.3, UDP_-_EDNS0_4096_D_KN)
  • medlineplus.gov/MX: No response was received from the server over TCP (tried 12 times). (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). (2607:f220:41e:252::53, UDP_-_EDNS0_512_D_KN)
  • medlineplus.gov/NS: The Authoritative Answer (AA) flag was not set in the response. (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. (165.112.6.3, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • medlineplus.gov/SOA (NODATA): No SOA RR was returned with the NODATA response. (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. (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). (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). (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. (165.112.6.3, UDP_-_EDNS0_4096_D_KN)
  • medlineplus.gov/TXT (NODATA): No SOA RR was returned with the NODATA response. (165.112.6.3, UDP_-_EDNS0_4096_D_KN)
  • medlineplus.gov/TXT (NODATA): The Authoritative Answer (AA) flag was not set in the response. (165.112.6.3, UDP_-_EDNS0_4096_D_KN)
  • medlineplus.gov/TXT: No response was received from the server over TCP (tried 7 times). (2607:f220:41f:1405::3, TCP_-_EDNS0_4096_D_KN)
Warnings (15)
  • gov to nih.gov: Authoritative AAAA records exist for ns.nih.gov, but there are no corresponding AAAA glue records.
  • gov to nih.gov: Authoritative AAAA records exist for ns2.nih.gov, but there are no corresponding AAAA glue records.
  • gov to nih.gov: Authoritative AAAA records exist for ns3.nih.gov, but there are no corresponding AAAA glue records.
  • medlineplus.gov/CNAME: The server returned CNAME for medlineplus.gov, but records of other types exist at that name.
  • 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. (2607:f220:41e:252::50, UDP_-_EDNS0_4096_D_KN)
  • medlineplus.gov/MX: The Authoritative Answer (AA) flag was not set in the response. (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). (2607:f220:41e:252::50, UDP_-_EDNS0_4096_D_KN)
  • nih.gov/DS (alg 8, id 32209): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
  • nih.gov/DS (alg 8, id 32209): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
  • 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.
  • 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.
  • nih.gov/DS (alg 8, id 57346): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
  • nih.gov/DS (alg 8, id 57346): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
  • 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.
  • 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.

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