health.mil
Updated:
2024-01-18 10:19:30 UTC (345 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 (12)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 30903)
- health.mil/DNSKEY (alg 8, id 11565)
- health.mil/DNSKEY (alg 8, id 13909)
- health.mil/DNSKEY (alg 8, id 16533)
- health.mil/DNSKEY (alg 8, id 56419)
- health.mil/DS (alg 8, id 56419)
- health.mil/DS (alg 8, id 56419)
- mil/DNSKEY (alg 8, id 16801)
- mil/DNSKEY (alg 8, id 49404)
- mil/DNSKEY (alg 8, id 51706)
- mil/DS (alg 8, id 16801)
Delegation status
Secure (2)
- . to mil
- mil to health.mil
Notices
Errors (8)
- health.mil/DNSKEY: No response was received from the server over UDP (tried 10 times). See RFC 1035, Sec. 4.2. (214.2.216.178, UDP_-_EDNS0_4096_D_KN)
- health.mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (214.2.208.178, 214.2.212.178, 214.2.214.178, UDP_-_EDNS0_512_D_KN)
- health.mil/MX: No response was received from the server over TCP (tried 2 times). See RFC 1035, Sec. 4.2. (214.2.212.178, TCP_-_EDNS0_4096_D)
- health.mil/NS: 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)
- t2o45xgpn8.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 (10)
- health.mil/DS (alg 8, id 56419): 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 56419): 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 56419): 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 56419): 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/SOA: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (214.2.211.178, UDP_-_EDNS0_4096_D_KN)
- health.mil/TXT: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (214.2.213.178, UDP_-_EDNS0_4096_D_KN)
- mil to health.mil: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the mil zone): ns01-swc-gw.health.mil See RFC 1034, Sec. 4.2.2.
- t2o45xgpn8.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.
