hhs.gov
Updated:
2023-08-29 15:35:16 UTC (457 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- hhs.gov/A
- hhs.gov/MX
- hhs.gov/NS
- hhs.gov/SOA
- hhs.gov/TXT
Secure (1)
- gov/SOA
DNSKEY/DS/NSEC status
Insecure (4)
- hhs.gov/DNSKEY (alg 8, id 23377)
- hhs.gov/DNSKEY (alg 8, id 24002)
- hhs.gov/DNSKEY (alg 8, id 25161)
- hhs.gov/DNSKEY (alg 8, id 26568)
Secure (6)
- ./DNSKEY (alg 8, id 11019)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of hhs.gov/DS
- gov/DNSKEY (alg 8, id 40921)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Insecure (1)
- gov to hhs.gov
Secure (1)
- . to gov
Notices
Errors (4)
- NSEC3 proving non-existence of hhs.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of hhs.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- ybgh2uoz9v.hhs.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- hhs.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
- NSEC3 proving non-existence of hhs.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of hhs.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- hhs.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
