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/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/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/NSEC3PARAM: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (158.74.35.11, UDP_-_EDNS0_4096_D_KN)
hhsops.gov/NSEC3PARAM: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (158.74.35.12, 2607:f220:0:1::3b, UDP_-_EDNS0_4096_D_KN)
hhsops.gov/NSEC3PARAM: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (2607:f220:0:1::3a, UDP_-_EDNS0_4096_D_KN)
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/TXT: 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/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
ibcyxuokd5.hhsops.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (12)
hhsops.gov/DS (alg 8, id 33175): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
hhsops.gov/DS (alg 8, id 33175): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
hhsops.gov/DS (alg 8, id 33175): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
hhsops.gov/DS (alg 8, id 33175): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
hhsops.gov/DS (alg 8, id 50665): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
hhsops.gov/DS (alg 8, id 50665): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
hhsops.gov/DS (alg 8, id 50665): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
hhsops.gov/DS (alg 8, id 50665): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
hhsops.gov/DS (alg 8, id 58879): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
hhsops.gov/DS (alg 8, id 58879): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
hhsops.gov/DS (alg 8, id 58879): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
hhsops.gov/DS (alg 8, id 58879): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.