marines.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
marines.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
marines.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
marines.mil/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
marines.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
2bt8ncqdl6.marines.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (9)
marines.mil/DS (alg 8, id 14557): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
marines.mil/DS (alg 8, id 14557): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
marines.mil/DS (alg 8, id 14557): 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.
marines.mil/DS (alg 8, id 14557): 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.
marines.mil/SOA: 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. (192.156.7.120, UDP_-_EDNS0_4096_D_K)
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.