health.mil/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (214.2.214.178, 214.2.215.178, UDP_-_EDNS0_4096_D_KN)
health.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
w6v5rfy2l1.health.mil/A 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 (16)
health.mil/DNSKEY (alg 8, id 1050): 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.215.178, UDP_-_EDNS0_4096_D_KN)
health.mil/DNSKEY (alg 8, id 11565): 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.215.178, UDP_-_EDNS0_4096_D_KN)
health.mil/DNSKEY (alg 8, id 13909): 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.215.178, UDP_-_EDNS0_4096_D_KN)
health.mil/DNSKEY (alg 8, id 15228): 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.215.178, UDP_-_EDNS0_4096_D_KN)
health.mil/DNSKEY (alg 8, id 56419): 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.215.178, UDP_-_EDNS0_4096_D_KN)
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/MX: 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.210.178, UDP_-_EDNS0_4096_D_KN)
health.mil/SOA: 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.216.178, UDP_-_EDNS0_4096_D_KN_0x20)
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.
health.mil/DNSKEY 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.
w6v5rfy2l1.health.mil/A 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.