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 (2)
  • hhsops.gov/NSEC3PARAM
  • hhsops.gov/NSEC3PARAM
Secure (7)
  • hhsops.gov/A
  • hhsops.gov/AAAA
  • hhsops.gov/MX
  • hhsops.gov/NS
  • hhsops.gov/NSEC3PARAM
  • hhsops.gov/SOA
  • hhsops.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (16)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • gov/DNSKEY (alg 8, id 24250)
  • gov/DNSKEY (alg 8, id 50011)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • hhsops.gov/DNSKEY (alg 8, id 13176)
  • hhsops.gov/DNSKEY (alg 8, id 24345)
  • hhsops.gov/DNSKEY (alg 8, id 55804)
  • hhsops.gov/DNSKEY (alg 8, id 59643)
  • hhsops.gov/DNSKEY (alg 8, id 63079)
  • hhsops.gov/DNSKEY (alg 8, id 65260)
  • hhsops.gov/DNSKEY (alg 8, id 8331)
  • hhsops.gov/DS (alg 8, id 55804)
  • hhsops.gov/DS (alg 8, id 63079)
  • hhsops.gov/DS (alg 8, id 65260)

Delegation statusDelegation status

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

NoticesNotices

Errors (51)
  • RRSIG hhsops.gov/A alg 8, id 59643: With a TTL of 90000 the RRSIG RR can be in the cache of a non-validating resolver until 10 hours, 25 minutes after it expires at 2023-04-19 06:24:54+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG hhsops.gov/MX alg 8, id 59643: With a TTL of 90000 the RRSIG RR can be in the cache of a non-validating resolver until 6 hours, 9 minutes after it expires at 2023-04-19 10:41:03+00:00. See RFC 4035, Sec. 5.3.3.
  • gov to hhsops.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. (158.74.35.12, TCP_-_NOEDNS_)
  • gov to hhsops.gov: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (158.74.35.12, TCP_-_NOEDNS_)
  • 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::3a)
  • hhsops.gov/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (158.74.35.11, 2607:f220:0:1::3a, 2607:f220:0:1::3b, UDP_-_NOEDNS_)
  • hhsops.gov/AAAA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (158.74.35.11, 2607:f220:0:1::3a, UDP_-_NOEDNS_)
  • hhsops.gov/DNSKEY (alg 8, id 13176): 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. (158.74.35.12, TCP_-_NOEDNS_)
  • hhsops.gov/DNSKEY (alg 8, id 13176): 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. (158.74.35.12, UDP_-_EDNS0_4096_D_KN)
  • hhsops.gov/DNSKEY (alg 8, id 13176): 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. (158.74.35.12, UDP_-_EDNS0_4096_D_KN)
  • hhsops.gov/DNSKEY (alg 8, id 24345): 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. (158.74.35.12, TCP_-_NOEDNS_)
  • hhsops.gov/DNSKEY (alg 8, id 24345): 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. (158.74.35.12, UDP_-_EDNS0_4096_D_KN)
  • hhsops.gov/DNSKEY (alg 8, id 24345): 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. (158.74.35.12, UDP_-_EDNS0_4096_D_KN)
  • hhsops.gov/DNSKEY (alg 8, id 55804): 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. (158.74.35.12, TCP_-_NOEDNS_)
  • hhsops.gov/DNSKEY (alg 8, id 55804): 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. (158.74.35.12, UDP_-_EDNS0_4096_D_KN)
  • hhsops.gov/DNSKEY (alg 8, id 55804): 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. (158.74.35.12, UDP_-_EDNS0_4096_D_KN)
  • hhsops.gov/DNSKEY (alg 8, id 59643): 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. (158.74.35.12, TCP_-_NOEDNS_)
  • hhsops.gov/DNSKEY (alg 8, id 59643): 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. (158.74.35.12, UDP_-_EDNS0_4096_D_KN)
  • hhsops.gov/DNSKEY (alg 8, id 59643): 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. (158.74.35.12, UDP_-_EDNS0_4096_D_KN)
  • hhsops.gov/DNSKEY (alg 8, id 63079): 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. (158.74.35.12, TCP_-_NOEDNS_)
  • hhsops.gov/DNSKEY (alg 8, id 63079): 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. (158.74.35.12, UDP_-_EDNS0_4096_D_KN)
  • hhsops.gov/DNSKEY (alg 8, id 63079): 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. (158.74.35.12, UDP_-_EDNS0_4096_D_KN)
  • hhsops.gov/DNSKEY (alg 8, id 65260): 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. (158.74.35.12, TCP_-_NOEDNS_)
  • hhsops.gov/DNSKEY (alg 8, id 65260): 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. (158.74.35.12, UDP_-_EDNS0_4096_D_KN)
  • hhsops.gov/DNSKEY (alg 8, id 65260): 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. (158.74.35.12, UDP_-_EDNS0_4096_D_KN)
  • hhsops.gov/DNSKEY (alg 8, id 8331): 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. (158.74.35.12, TCP_-_NOEDNS_)
  • hhsops.gov/DNSKEY (alg 8, id 8331): 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. (158.74.35.12, UDP_-_EDNS0_4096_D_KN)
  • hhsops.gov/DNSKEY (alg 8, id 8331): 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. (158.74.35.12, UDP_-_EDNS0_4096_D_KN)
  • hhsops.gov/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (158.74.35.11, 2607:f220:0:1::3a, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • hhsops.gov/MX: 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_)
  • hhsops.gov/MX: 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::3b, UDP_-_EDNS0_4096_D_KN)
  • hhsops.gov/MX: 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::3b, UDP_-_EDNS0_4096_D_KN)
  • hhsops.gov/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (158.74.35.11, 158.74.35.12, 2607:f220:0:1::3a, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • hhsops.gov/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (158.74.35.12, 2607:f220:0:1::3b, UDP_-_NOEDNS_)
  • hhsops.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. (158.74.35.11, UDP_-_NOEDNS_)
  • hhsops.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::3b, UDP_-_NOEDNS_)
  • hhsops.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. (158.74.35.11, UDP_-_EDNS0_4096_D_KN)
  • hhsops.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::3b, UDP_-_EDNS0_4096_D_KN)
  • hhsops.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. (158.74.35.11, UDP_-_EDNS0_4096_D_KN)
  • hhsops.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::3b, UDP_-_EDNS0_4096_D_KN)
  • hhsops.gov/NSEC3PARAM: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (2607:f220:0:1::3a, UDP_-_NOEDNS_)
  • hhsops.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, TCP_-_NOEDNS_)
  • hhsops.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, TCP_-_EDNS0_4096_D_N)
  • hhsops.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (158.74.35.11, 2607:f220:0:1::3a, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • hhsops.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (2607:f220:0:1::3a, TCP_-_NOEDNS_)
  • hhsops.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. (158.74.35.11, 2607:f220:0:1::3b, UDP_-_NOEDNS_)
  • 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. (158.74.35.11, 2607:f220:0:1::3b, UDP_-_EDNS0_4096_D_KN)
  • hhsops.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. (158.74.35.11, 2607:f220:0:1::3b, UDP_-_EDNS0_4096_D_KN)
  • 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.
  • wmuah4lns1.hhsops.gov/A 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