health.gov
Updated:
2021-07-06 17:07:34 UTC (1236 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (3)
- health.gov/A
- health.gov/NS
- health.gov/SOA
Secure (1)
- gov/SOA
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 14631)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26838)
- NSEC3 proving non-existence of health.gov/DS
- gov/DNSKEY (alg 8, id 48498)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Insecure (1)
- gov to health.gov
Secure (1)
- . to gov
Notices
Errors (5)
- NSEC3 proving non-existence of health.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 health.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- health.gov/DS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:500:4431::2:30, UDP_-_NOEDNS_)
- health.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:500:4431::2:30, UDP_-_NOEDNS_)
- health.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
- NSEC3 proving non-existence of health.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of health.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- health.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
