RRSIG af.mil/DNSKEY alg 8, id 34539: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG af.mil/DNSKEY alg 8, id 34539: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG af.mil/DNSKEY alg 8, id 34539: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG af.mil/DNSKEY alg 8, id 34539: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG af.mil/DNSKEY alg 8, id 34539: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG af.mil/DNSKEY alg 8, id 56521: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG af.mil/DNSKEY alg 8, id 56521: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG af.mil/DNSKEY alg 8, id 56521: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG af.mil/DNSKEY alg 8, id 56521: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG af.mil/DNSKEY alg 8, id 56521: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG af.mil/DNSKEY alg 8, id 9826: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG af.mil/DNSKEY alg 8, id 9826: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG af.mil/DNSKEY alg 8, id 9826: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG af.mil/DNSKEY alg 8, id 9826: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG af.mil/DNSKEY alg 8, id 9826: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
mil to af.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. (132.3.41.10, UDP_-_EDNS0_4096_D_K)
af.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
af.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
4xusaygpde.af.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
af.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
af.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
af.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (14)
af.mil/DNSKEY (alg 8, id 37074): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (132.3.13.10, UDP_-_EDNS0_4096_D_K)
af.mil/DS (alg 8, id 56521): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
af.mil/DS (alg 8, id 56521): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
af.mil/DS (alg 8, id 56521): 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.
af.mil/DS (alg 8, id 56521): 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): 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.
af.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
4xusaygpde.af.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
af.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
af.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
af.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.