health.mil
Updated:
2023-02-02 12:31:45 UTC (706 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (8)
- health.mil/A
- health.mil/MX
- health.mil/NS
- health.mil/NSEC3PARAM
- health.mil/SOA
- health.mil/SOA
- health.mil/SOA
- health.mil/TXT
DNSKEY/DS/NSEC status
Secure (13)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 951)
- health.mil/DNSKEY (alg 8, id 13639)
- health.mil/DNSKEY (alg 8, id 13909)
- health.mil/DNSKEY (alg 8, id 51834)
- health.mil/DNSKEY (alg 8, id 609)
- health.mil/DNSKEY (alg 8, id 65370)
- health.mil/DS (alg 8, id 13909)
- health.mil/DS (alg 8, id 13909)
- mil/DNSKEY (alg 8, id 55084)
- mil/DNSKEY (alg 8, id 57763)
- mil/DNSKEY (alg 8, id 62470)
- mil/DS (alg 8, id 62470)
Delegation status
Secure (2)
- . to mil
- mil to health.mil
Notices
Errors (11)
- health.mil/DNSKEY (alg 8, id 13639): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (214.2.208.178, 214.2.212.178, UDP_-_EDNS0_4096_D_KN)
- health.mil/DNSKEY (alg 8, id 13909): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (214.2.208.178, 214.2.212.178, UDP_-_EDNS0_4096_D_KN)
- health.mil/DNSKEY (alg 8, id 51834): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (214.2.208.178, 214.2.212.178, UDP_-_EDNS0_4096_D_KN)
- health.mil/DNSKEY (alg 8, id 609): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (214.2.208.178, 214.2.212.178, UDP_-_EDNS0_4096_D_KN)
- health.mil/DNSKEY (alg 8, id 65370): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (214.2.208.178, 214.2.212.178, UDP_-_EDNS0_4096_D_KN)
- mil to health.mil: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (214.2.208.178, 214.2.212.178, UDP_-_EDNS0_4096_D_KN)
- mil to health.mil: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (214.2.208.178, 214.2.212.178, UDP_-_EDNS0_4096_D_KN)
- jkuc1edybz.health.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
- health.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- health.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- health.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
- health.mil/DS (alg 8, id 13909): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- health.mil/DS (alg 8, id 13909): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- health.mil/DS (alg 8, id 13909): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- health.mil/DS (alg 8, id 13909): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- jkuc1edybz.health.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- health.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- health.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
