usfj.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
usfj.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
8mu7t9ofg6.usfj.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
usfj.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
usfj.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (19)
mil to usfj.mil: The following NS name(s) were found in the delegation NS RRset (i.e., in the mil zone), but not in the authoritative NS RRset: pnocxns1.pr.navy.mil, pnocxns2.pr.navy.mil See RFC 1034, Sec. 4.2.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): 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.
usfj.mil/DS (alg 8, id 9982): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
usfj.mil/DS (alg 8, id 9982): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
usfj.mil/DS (alg 8, id 9982): 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.
usfj.mil/DS (alg 8, id 9982): 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.
usfj.mil/DS (alg 8, id 9982): 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.143.234, UDP_-_EDNS0_4096_D_KN)
usfj.mil/DS (alg 8, id 9982): 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.143.234, UDP_-_EDNS0_4096_D_KN)
usfj.mil/DS (alg 8, id 9982): 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.143.234, UDP_-_EDNS0_4096_D_KN)
usfj.mil/DS (alg 8, id 9982): 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.143.234, UDP_-_EDNS0_4096_D_KN)
usfj.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
usfj.mil/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
8mu7t9ofg6.usfj.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
usfj.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
usfj.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
usfj.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.