sapr.mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (199.252.47.11, UDP_-_EDNS0_512_D_K)
sapr.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
sapr.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
x4hanek6wi.sapr.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
sapr.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (11)
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.
sapr.mil/DS (alg 8, id 21832): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
sapr.mil/DS (alg 8, id 21832): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
sapr.mil/DS (alg 8, id 21832): 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.
sapr.mil/DS (alg 8, id 21832): 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.
sapr.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
x4hanek6wi.sapr.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
sapr.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.