RRSIG ng.mil/DNSKEY alg 8, id 19689: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG ng.mil/DNSKEY alg 8, id 19689: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG ng.mil/DNSKEY alg 8, id 19689: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG ng.mil/DNSKEY alg 8, id 6460: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG ng.mil/DNSKEY alg 8, id 6460: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG ng.mil/DNSKEY alg 8, id 6460: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
mil to ng.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. (140.153.43.44, UDP_-_EDNS0_4096_D_K)
ng.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
ng.mil/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
ng.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
ng.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
ng.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
ng.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
udk2m8zyiq.ng.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (14)
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.
ng.mil/DS (alg 8, id 6460): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
ng.mil/DS (alg 8, id 6460): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
ng.mil/DS (alg 8, id 6460): 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.
ng.mil/DS (alg 8, id 6460): 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.
ng.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
ng.mil/TXT has warnings; select the "Denial of existence" DNSSEC option to see them.
ng.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
ng.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
ng.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
udk2m8zyiq.ng.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.