mil to southcom.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.
southcom.mil/DNSKEY: No response was received from the server over TCP (tried 10 times). See RFC 1035, Sec. 4.2. (130.22.36.4, TCP_-_EDNS0_4096_D_KN)
southcom.mil/DNSKEY: No response was received from the server over TCP (tried 6 times). See RFC 1035, Sec. 4.2. (130.22.177.211, TCP_-_EDNS0_4096_D_KN)
southcom.mil/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (130.22.36.4, 130.22.177.211, TCP_-_EDNS0_4096_D_N)
southcom.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
skjtnvlmip.southcom.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
southcom.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
southcom.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
southcom.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
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.
southcom.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
southcom.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
skjtnvlmip.southcom.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.