usfj.mil zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (205.56.181.106, 205.56.181.107)
usfj.mil/DNSKEY: No response was received from the server over TCP (tried 11 times). See RFC 1035, Sec. 4.2. (205.56.181.107, TCP_-_NOEDNS_)
usfj.mil/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (205.56.181.106, UDP_-_EDNS0_4096_D_KN)
usfj.mil/NSEC3PARAM: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.211.150.66, 199.211.150.67, 205.56.181.106, 205.56.181.107, UDP_-_NOEDNS_)
usfj.mil/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (199.211.150.66, 199.211.150.67, 205.56.181.106, 205.56.181.107, TCP_-_EDNS0_4096_D_N)
usfj.mil/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.211.150.66, 199.211.150.67, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
usfj.mil/SOA: No response was received from the server over UDP (tried 13 times). See RFC 1035, Sec. 4.2. (205.56.181.106, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
usfj.mil/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.211.150.66, 199.211.150.67, 205.56.181.106, UDP_-_NOEDNS_)
usfj.mil/TXT: No response was received from the server over UDP (tried 13 times). See RFC 1035, Sec. 4.2. (199.211.150.66, 205.56.181.106, UDP_-_NOEDNS_)
usfj.mil/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (199.211.150.67, UDP_-_NOEDNS_)
b0a5urmdsx.usfj.mil/A 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.
usfj.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
usfj.mil/MX 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 (10)
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.
usfj.mil/DS (alg 8, id 58520): 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 58520): 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 58520): 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 58520): 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/SOA: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (205.56.181.107, UDP_-_EDNS0_4096_D_KN)
usfj.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
usfj.mil/CNAME 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.
usfj.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.