healthfinder.gov
Updated:
2023-08-30 05:09:23 UTC (449 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (4)
- healthfinder.gov/A
- healthfinder.gov/NS
- healthfinder.gov/SOA
- healthfinder.gov/TXT
Secure (1)
- gov/SOA
DNSKEY/DS/NSEC status
Insecure (4)
- healthfinder.gov/DNSKEY (alg 8, id 12270)
- healthfinder.gov/DNSKEY (alg 8, id 53210)
- healthfinder.gov/DNSKEY (alg 8, id 58023)
- healthfinder.gov/DNSKEY (alg 8, id 6926)
Secure (6)
- ./DNSKEY (alg 8, id 11019)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of healthfinder.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 healthfinder.gov
Secure (1)
- . to gov
Notices
Errors (4)
- NSEC3 proving non-existence of healthfinder.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 healthfinder.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- sct7ohw6q8.healthfinder.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- healthfinder.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
- NSEC3 proving non-existence of healthfinder.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of healthfinder.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- healthfinder.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
