View on GitHub

DNSViz: A DNS visualization tool

findtreatment.gov

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

RRset statusRRset status

Bogus (4)
  • findtreatment.gov/AAAA
  • findtreatment.gov/NSEC3PARAM
  • findtreatment.gov/SOA
  • findtreatment.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 951)
  • findtreatment.gov/DS (alg 8, id 30226)
  • findtreatment.gov/DS (alg 8, id 39097)
  • findtreatment.gov/DS (alg 8, id 55804)
  • gov/DNSKEY (alg 8, id 24250)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
Non_existent (3)
  • findtreatment.gov/DNSKEY (alg 8, id 30226)
  • findtreatment.gov/DNSKEY (alg 8, id 39097)
  • findtreatment.gov/DNSKEY (alg 8, id 55804)

Delegation statusDelegation status

Bogus (1)
  • gov to findtreatment.gov
Secure (1)
  • . to gov

NoticesNotices

Errors (38)
  • findtreatment.gov zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (2607:f220:0:1::3a, 2607:f220:0:1::3b)
  • findtreatment.gov zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (158.74.35.12)
  • findtreatment.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (158.74.35.12)
  • findtreatment.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (158.74.35.11)
  • findtreatment.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (158.74.35.11, 158.74.35.12, UDP_-_NOEDNS_)
  • findtreatment.gov/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (2607:f220:0:1::3a, 2607:f220:0:1::3b, UDP_-_NOEDNS_)
  • findtreatment.gov/AAAA: DNSSEC was effectively downgraded because the response had an invalid RCODE (SERVFAIL) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (2607:f220:0:1::3b, UDP_-_NOEDNS_)
  • findtreatment.gov/AAAA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (158.74.35.12, 2607:f220:0:1::3a, UDP_-_NOEDNS_)
  • findtreatment.gov/AAAA: The response had an invalid RCODE (SERVFAIL) until EDNS was disabled. See RFC 6891, Sec. 6.2.6. (2607:f220:0:1::3b, UDP_-_EDNS0_4096_D_KN)
  • findtreatment.gov/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (158.74.35.12, UDP_-_NOEDNS_)
  • findtreatment.gov/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (158.74.35.12, UDP_-_EDNS0_512_D_KN)
  • findtreatment.gov/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (2607:f220:0:1::3a, 2607:f220:0:1::3b, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • findtreatment.gov/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (2607:f220:0:1::3a, TCP_-_NOEDNS_)
  • findtreatment.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (158.74.35.11, UDP_-_NOEDNS_)
  • findtreatment.gov/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (158.74.35.12, 2607:f220:0:1::3a, 2607:f220:0:1::3b, UDP_-_NOEDNS_)
  • findtreatment.gov/NSEC3PARAM: DNSSEC was effectively downgraded because the response had an invalid RCODE (SERVFAIL) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (2607:f220:0:1::3a, UDP_-_NOEDNS_)
  • findtreatment.gov/NSEC3PARAM: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (158.74.35.12, UDP_-_NOEDNS_)
  • findtreatment.gov/NSEC3PARAM: No response was received from the server over UDP (tried 13 times). See RFC 1035, Sec. 4.2. (2607:f220:0:1::3b, UDP_-_NOEDNS_)
  • findtreatment.gov/NSEC3PARAM: The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (2607:f220:0:1::3a, UDP_-_EDNS0_4096_D_KN)
  • findtreatment.gov/NSEC3PARAM: The response had an invalid RCODE (SERVFAIL) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (2607:f220:0:1::3a, UDP_-_EDNS0_4096_D_KN)
  • findtreatment.gov/SOA: DNSSEC was effectively downgraded because the response had an invalid RCODE (SERVFAIL) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (2607:f220:0:1::3b, UDP_-_NOEDNS_)
  • findtreatment.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (158.74.35.12, TCP_-_EDNS0_4096_D_N)
  • findtreatment.gov/SOA: No response was received from the server over TCP (tried 4 times). See RFC 1035, Sec. 4.2. (2607:f220:0:1::3a, TCP_-_NOEDNS_)
  • findtreatment.gov/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (158.74.35.12, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • findtreatment.gov/SOA: No response was received from the server over UDP (tried 13 times). See RFC 1035, Sec. 4.2. (2607:f220:0:1::3b, UDP_-_NOEDNS_)
  • findtreatment.gov/SOA: The response had an invalid RCODE (SERVFAIL) until EDNS was disabled. See RFC 6891, Sec. 6.2.6. (2607:f220:0:1::3b, UDP_-_EDNS0_4096_D_KN)
  • findtreatment.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (2607:f220:0:1::3a, 2607:f220:0:1::3b, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • findtreatment.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (2607:f220:0:1::3b, TCP_-_NOEDNS_)
  • findtreatment.gov/TXT: DNSSEC was effectively downgraded because the response had an invalid RCODE (SERVFAIL) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (2607:f220:0:1::3a, 2607:f220:0:1::3b, UDP_-_NOEDNS_)
  • findtreatment.gov/TXT: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (158.74.35.12, UDP_-_NOEDNS_)
  • findtreatment.gov/TXT: The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (2607:f220:0:1::3a, UDP_-_EDNS0_4096_D_KN)
  • findtreatment.gov/TXT: The response had an invalid RCODE (SERVFAIL) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (2607:f220:0:1::3a, UDP_-_EDNS0_4096_D_KN)
  • findtreatment.gov/TXT: The response had an invalid RCODE (SERVFAIL) until EDNS was disabled. See RFC 6891, Sec. 6.2.6. (2607:f220:0:1::3b, UDP_-_EDNS0_4096_D_KN)
  • gov to findtreatment.gov: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11.
  • findtreatment.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • findtreatment.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • dkymicehp4.findtreatment.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • findtreatment.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (1)
  • findtreatment.gov/MX 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