hhs.gov
Updated:
2023-10-24 08:39:51 UTC (400 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 (2)
- gov/SOA
- gov/SOA
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46780)
- NSEC proving non-existence of hhs.gov/DS
- NSEC3 proving non-existence of hhs.gov/DS
- gov/DNSKEY (alg 8, id 10104)
- gov/DNSKEY (alg 8, id 40921)
- gov/DNSKEY (alg 8, id 49735)
- gov/DNSKEY (alg 8, id 64280)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 64280)
- 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.
- 2q396vcth7.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 (4)
- 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.
- gov/DNSKEY (alg 8, id 40921): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (69.36.153.30, 69.36.157.30, 81.19.194.30, 209.112.123.30, 2001:500:4431::2:30, 2620:74:27::2:30, 2620:74:28::2:30, 2620:74:29::2:30, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
- hhs.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
