RRSIG sapr.mil/DNSKEY alg 8, id 15139: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG sapr.mil/DNSKEY alg 8, id 15139: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG sapr.mil/DNSKEY alg 8, id 15139: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG sapr.mil/DNSKEY alg 8, id 21832: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG sapr.mil/DNSKEY alg 8, id 21832: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG sapr.mil/DNSKEY alg 8, id 21832: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG sapr.mil/DNSKEY alg 8, id 58014: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG sapr.mil/DNSKEY alg 8, id 58014: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG sapr.mil/DNSKEY alg 8, id 58014: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
mil to sapr.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. (199.252.47.11, 199.252.47.75, 214.14.133.11, UDP_-_EDNS0_4096_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.
wmfout6ckq.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 7765): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
mil/DS (alg 8, id 7765): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
mil/DS (alg 8, id 7765): 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 7765): 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.
wmfout6ckq.sapr.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
sapr.mil/CNAME 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.