navy.mil zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (131.77.60.235, 152.229.110.235, 214.3.125.231, 215.65.126.180)
navy.mil/DNSKEY: No response was received from the server over TCP (tried 9 times). See RFC 1035, Sec. 4.2. (215.65.126.180, TCP_-_EDNS0_4096_D_KN)
navy.mil/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (131.77.60.235, 152.229.110.235, 214.3.125.231, UDP_-_EDNS0_4096_D_KN)
navy.mil/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (131.77.60.235, 152.229.110.235, 214.3.125.231, 214.23.245.4, 214.23.245.5, 215.65.126.180, 215.65.126.181, TCP_-_EDNS0_4096_D_N)
navy.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
3ux1bkdp2i.navy.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
navy.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
navy.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
navy.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (16)
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.
mil/DS (alg 8, id 51349): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
mil/DS (alg 8, id 51349): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
mil/DS (alg 8, id 51349): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
mil/DS (alg 8, id 51349): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:2f::f, UDP_-_EDNS0_4096_D_KN)
navy.mil/DS (alg 8, id 54382): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
navy.mil/DS (alg 8, id 54382): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
navy.mil/DS (alg 8, id 54382): 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.
navy.mil/DS (alg 8, id 54382): 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.
navy.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
3ux1bkdp2i.navy.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
navy.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
navy.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.