hhsops.gov
Updated:
2023-04-18 16:49:58 UTC (588 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (6)
- hhsops.gov/A
- hhsops.gov/AAAA
- hhsops.gov/MX
- hhsops.gov/NS
- hhsops.gov/SOA
- hhsops.gov/TXT
DNSKEY/DS/NSEC status
Secure (9)
- ./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/DS (alg 8, id 55804)
- hhsops.gov/DS (alg 8, id 63079)
- hhsops.gov/DS (alg 8, id 65260)
Non_existent (3)
- hhsops.gov/DNSKEY (alg 8, id 55804)
- hhsops.gov/DNSKEY (alg 8, id 63079)
- hhsops.gov/DNSKEY (alg 8, id 65260)
Delegation status
Bogus (1)
- gov to hhsops.gov
Secure (1)
- . to gov
Notices
Errors (27)
- 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.11, 158.74.35.12, 2607:f220:0:1::3a, 2607:f220:0:1::3b, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN, UDP_-_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.11, 158.74.35.12, 2607:f220:0:1::3a, 2607:f220:0:1::3b, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN, UDP_-_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. (158.74.35.12)
- hhsops.gov/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (158.74.35.11, 158.74.35.12, 2607:f220:0:1::3a, 2607:f220:0:1::3b, UDP_-_EDNS0_4096_D_KN)
- hhsops.gov/AAAA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (158.74.35.11, 158.74.35.12, 2607:f220:0:1::3a, 2607:f220:0:1::3b, 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, UDP_-_EDNS0_512_D_KN)
- 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. (158.74.35.11, UDP_-_NOEDNS_)
- hhsops.gov/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (158.74.35.11, 158.74.35.12, 2607:f220:0:1::3a, 2607:f220:0:1::3b, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- 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. (158.74.35.11, 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. (158.74.35.11, UDP_-_EDNS0_4096_D_KN)
- hhsops.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (158.74.35.11, 158.74.35.12, 2607:f220:0:1::3a, 2607:f220:0:1::3b, UDP_-_EDNS0_4096_D_KN)
- 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. (158.74.35.11, 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: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (158.74.35.11, 158.74.35.12, 2607:f220:0:1::3a, 2607:f220:0:1::3b, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- hhsops.gov/SOA: 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/SOA: 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/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.12, 2607:f220:0:1::3b, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
- hhsops.gov/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (158.74.35.12, 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.12, UDP_-_NOEDNS_)
- hhsops.gov/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (158.74.35.11, 2607:f220:0:1::3a, 2607:f220:0:1::3b, 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. (158.74.35.12, 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.12, 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.
- hhsops.gov/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
- bozdu8mvns.hhsops.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
