hhsops.gov
Updated:
2024-04-02 21:36:31 UTC (234 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (1)
- hhsops.gov/TXT
Secure (3)
- hhsops.gov/A
- hhsops.gov/NS
- hhsops.gov/SOA
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 30903)
- ./DNSKEY (alg 8, id 5613)
- gov/DNSKEY (alg 8, id 10104)
- gov/DNSKEY (alg 8, id 64280)
- gov/DS (alg 8, id 64280)
- hhsops.gov/DNSKEY (alg 13, id 2917)
- hhsops.gov/DNSKEY (alg 13, id 9637)
- hhsops.gov/DS (alg 13, id 9637)
Delegation status
Secure (2)
- . to gov
- gov to hhsops.gov
Notices
Errors (19)
- 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.11, 158.74.35.12, 2607:f220:0:1::3a, 2607:f220:0:1::3b)
- hhsops.gov/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (158.74.35.12, 2607:f220:0:1::3a, UDP_-_NOEDNS_)
- hhsops.gov/AAAA: 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, 2607:f220:0:1::3b, UDP_-_NOEDNS_)
- hhsops.gov/DNSKEY: 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, 2607:f220:0:1::3b, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
- 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, 2607:f220:0:1::3b, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
- 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. (158.74.35.11, 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. (158.74.35.11, 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. (158.74.35.11, UDP_-_EDNS0_4096_D_KN)
- hhsops.gov/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (2607:f220:0:1::3a, UDP_-_NOEDNS_)
- hhsops.gov/NSEC3PARAM: 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, 2607:f220:0:1::3b, UDP_-_NOEDNS_)
- hhsops.gov/SOA: 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, 2607:f220:0:1::3b, TCP_-_NOEDNS_)
- hhsops.gov/SOA: 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, 2607:f220:0:1::3b, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
- 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. (2607:f220:0:1::3a, 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. (2607:f220:0:1::3a, 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. (2607:f220:0:1::3a, UDP_-_EDNS0_4096_D_KN)
- hhsops.gov/TXT: 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::3b, UDP_-_NOEDNS_)
- 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.
- brqd8zkglp.hhsops.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
