RRSIG dla.mil/DNSKEY alg 8, id 58143: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG dla.mil/DNSKEY alg 8, id 58143: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG dla.mil/DNSKEY alg 8, id 58143: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG dla.mil/DNSKEY alg 8, id 60304: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG dla.mil/DNSKEY alg 8, id 60304: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG dla.mil/DNSKEY alg 8, id 60304: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
mil to dla.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. (206.38.35.3, UDP_-_EDNS0_4096_D_K)
dla.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
dla.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
dla.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
5o2bie87nm.dla.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
dla.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (19)
dla.mil/DNSKEY (alg 8, id 44845): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (131.78.81.254, UDP_-_EDNS0_4096_D_K)
dla.mil/DS (alg 8, id 60304): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
dla.mil/DS (alg 8, id 60304): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
dla.mil/DS (alg 8, id 60304): 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.
dla.mil/DS (alg 8, id 60304): 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.
dla.mil/DS (alg 8, id 60304): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (199.252.155.234, UDP_-_EDNS0_4096_D_K)
dla.mil/DS (alg 8, id 60304): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (199.252.155.234, UDP_-_EDNS0_4096_D_K)
dla.mil/DS (alg 8, id 60304): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (199.252.155.234, UDP_-_EDNS0_4096_D_K)
dla.mil/DS (alg 8, id 60304): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (199.252.155.234, UDP_-_EDNS0_4096_D_K)
dla.mil/TXT: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (206.38.35.3, UDP_-_EDNS0_4096_D_K)
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.
dla.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
dla.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
dla.mil/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
5o2bie87nm.dla.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
dla.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.