hhsops.gov
Updated:
2021-11-05 23:07:28 UTC (1066 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (9)
- hhsops.gov/A
- hhsops.gov/AAAA
- hhsops.gov/MX
- hhsops.gov/NS
- hhsops.gov/NSEC3PARAM
- hhsops.gov/NSEC3PARAM
- hhsops.gov/NSEC3PARAM
- hhsops.gov/SOA
- hhsops.gov/TXT
DNSKEY/DS/NSEC status
Secure (14)
- ./DNSKEY (alg 8, id 14748)
- ./DNSKEY (alg 8, id 20326)
- gov/DNSKEY (alg 8, id 6229)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- hhsops.gov/DNSKEY (alg 8, id 13143)
- hhsops.gov/DNSKEY (alg 8, id 2373)
- hhsops.gov/DNSKEY (alg 8, id 2985)
- hhsops.gov/DNSKEY (alg 8, id 33175)
- hhsops.gov/DNSKEY (alg 8, id 50665)
- hhsops.gov/DNSKEY (alg 8, id 58879)
- hhsops.gov/DS (alg 8, id 40912)
- hhsops.gov/DS (alg 8, id 50665)
- hhsops.gov/DS (alg 8, id 50665)
Non_existent (1)
- hhsops.gov/DNSKEY (alg 8, id 40912)
Delegation status
Secure (2)
- . to gov
- gov to hhsops.gov
Notices
Errors (11)
- RRSIG hhsops.gov/A alg 8, id 2373: With a TTL of 86400 the RRSIG RR can be in the cache of a non-validating resolver until 2 hours, 52 minutes after it expires at 2021-11-06 20:15:22+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG hhsops.gov/A alg 8, id 2373: With a TTL of 86400 the RRSIG RR can be in the cache of a non-validating resolver until 4 hours, 36 minutes after it expires at 2021-11-06 18:30:58+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG hhsops.gov/A alg 8, id 2373: With a TTL of 86400 the RRSIG RR can be in the cache of a non-validating resolver until 5 hours after it expires at 2021-11-06 18:06:54+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG hhsops.gov/MX alg 8, id 2373: With a TTL of 86400 the RRSIG RR can be in the cache of a non-validating resolver until 5 hours after it expires at 2021-11-06 18:06:54+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG hhsops.gov/MX alg 8, id 2373: With a TTL of 86400 the RRSIG RR can be in the cache of a non-validating resolver until 5 hours after it expires at 2021-11-06 18:06:59+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG hhsops.gov/NS alg 8, id 2373: With a TTL of 86400 the RRSIG RR can be in the cache of a non-validating resolver until 5 hours after it expires at 2021-11-06 18:06:52+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG hhsops.gov/NS alg 8, id 2373: With a TTL of 86400 the RRSIG RR can be in the cache of a non-validating resolver until 5 hours after it expires at 2021-11-06 18:06:54+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG hhsops.gov/TXT alg 8, id 2373: With a TTL of 86400 the RRSIG RR can be in the cache of a non-validating resolver until 4 hours, 20 minutes after it expires at 2021-11-06 18:46:32+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG hhsops.gov/TXT alg 8, id 2373: With a TTL of 86400 the RRSIG RR can be in the cache of a non-validating resolver until 5 hours after it expires at 2021-11-06 18:06:54+00:00. See RFC 4035, Sec. 5.3.3.
- hhsops.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- sf4qetahnx.hhsops.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
- 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/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- sf4qetahnx.hhsops.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
