mil to osd.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.
mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (199.252.143.234, UDP_-_EDNS0_512_D_KN)
osd.mil zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (214.14.133.11)
osd.mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (199.252.47.11, 199.252.47.75)
osd.mil/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.252.47.11, 199.252.47.75, 214.14.133.11, UDP_-_NOEDNS_)
osd.mil/DNSKEY: No response was received from the server over UDP (tried 11 times). See RFC 1035, Sec. 4.2. (214.14.133.11, UDP_-_EDNS0_4096_D_KN)
osd.mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (214.14.133.11, UDP_-_EDNS0_512_D_KN)
osd.mil/MX: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (214.14.133.11, TCP_-_EDNS0_4096_D_KN)
osd.mil/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (214.14.133.11, UDP_-_EDNS0_512_D_KN)
osd.mil/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.252.47.11, 199.252.47.75, UDP_-_NOEDNS_)
osd.mil/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (214.14.133.11, TCP_-_EDNS0_4096_D_N)
osd.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
osd.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
z4mgeyqsjn.osd.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
osd.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
mil/DS (alg 8, id 51349): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
mil/DS (alg 8, id 51349): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
mil/DS (alg 8, id 51349): 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.
mil/DS (alg 8, id 51349): 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.
osd.mil/NSEC3PARAM: 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.14.133.11, UDP_-_EDNS0_4096_D_KN)
osd.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.14.133.11, UDP_-_EDNS0_4096_D_KN_0x20)
osd.mil/TXT: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (214.14.133.11, UDP_-_EDNS0_4096_D_KN)
osd.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.