ehr.gov
Updated:
2023-09-14 14:31:22 UTC (434 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (4)
- ehr.gov/MX
- ehr.gov/NS
- ehr.gov/SOA
- ehr.gov/TXT
Secure (1)
- gov/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 11019)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of ehr.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 ehr.gov
Secure (1)
- . to gov
Notices
Errors (6)
- NSEC3 proving non-existence of ehr.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 ehr.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- ehr.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (214.2.252.50, 214.2.252.52, 214.2.253.50, 214.2.253.52)
- ehr.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (214.2.252.50, 214.2.252.52, 214.2.253.50, 214.2.253.52, UDP_-_NOEDNS_)
- ehr.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- ehr.gov/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- NSEC3 proving non-existence of ehr.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of ehr.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- gov to ehr.gov: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the gov zone): ns01-cern-auth2.health.mil, ns01-cernls-auth1.health.mil, ns01-cernls-auth2.health.mil, ns01-cern-auth1.health.mil See RFC 1034, Sec. 4.2.2.
- ehr.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
