View on GitHub

DNSViz: A DNS visualization tool

hhsops.gov

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

RRset statusRRset status

Bogus (1)
  • hhsops.gov/NS
Secure (4)
  • hhsops.gov/AAAA
  • hhsops.gov/NSEC3PARAM
  • hhsops.gov/SOA
  • hhsops.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 951)
  • gov/DNSKEY (alg 8, id 24250)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • hhsops.gov/DNSKEY (alg 8, id 15843)
  • hhsops.gov/DNSKEY (alg 8, id 55804)
  • hhsops.gov/DNSKEY (alg 8, id 57255)
  • hhsops.gov/DNSKEY (alg 8, id 63079)
  • hhsops.gov/DS (alg 8, id 30226)
  • hhsops.gov/DS (alg 8, id 55804)
  • hhsops.gov/DS (alg 8, id 63079)
Non_existent (1)
  • hhsops.gov/DNSKEY (alg 8, id 30226)

Delegation statusDelegation status

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

NoticesNotices

Errors (27)
  • hhsops.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::3b)
  • hhsops.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (158.74.35.11, 158.74.35.12)
  • hhsops.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, 2607:f220:0:1::3a, UDP_-_NOEDNS_)
  • hhsops.gov/A: 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_)
  • hhsops.gov/AAAA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:f220:0:1::3a, UDP_-_NOEDNS_)
  • hhsops.gov/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2607:f220:0:1::3a, 2607:f220:0:1::3b, UDP_-_EDNS0_512_D_KN)
  • hhsops.gov/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (2607:f220:0:1::3b, UDP_-_NOEDNS_)
  • hhsops.gov/MX: No response was received from the server over TCP (tried 10 times). See RFC 1035, Sec. 4.2. (2607:f220:0:1::3b, TCP_-_NOEDNS_)
  • hhsops.gov/MX: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:f220:0:1::3a, UDP_-_NOEDNS_)
  • hhsops.gov/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2607:f220:0:1::3a, 2607:f220:0:1::3b, UDP_-_EDNS0_512_D_KN)
  • hhsops.gov/NS: 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_)
  • hhsops.gov/NS: 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_)
  • hhsops.gov/NS: 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_)
  • hhsops.gov/NS: 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)
  • hhsops.gov/NS: 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)
  • hhsops.gov/NSEC3PARAM: No response was received from the server over TCP (tried 6 times). See RFC 1035, Sec. 4.2. (2607:f220:0:1::3b, TCP_-_NOEDNS_)
  • hhsops.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (2607:f220:0:1::3b, TCP_-_EDNS0_4096_D_N)
  • hhsops.gov/SOA: No response was received from the server over TCP (tried 5 times). See RFC 1035, Sec. 4.2. (2607:f220:0:1::3a, TCP_-_EDNS0_4096_D_N)
  • hhsops.gov/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:f220:0:1::3a, UDP_-_NOEDNS__0x20)
  • hhsops.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_)
  • hhsops.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (2607:f220:0:1::3b, UDP_-_NOEDNS_)
  • hhsops.gov/TXT: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 11 times) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (2607:f220:0:1::3a, UDP_-_NOEDNS_)
  • hhsops.gov/TXT: No response was received from the server over UDP (tried 11 times) 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)
  • hhsops.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)
  • g0t4px3s8y.hhsops.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • hhsops.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • hhsops.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (1)
  • hhsops.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