mil zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (199.252.143.234, 199.252.154.234, 199.252.155.234, 199.252.157.234)
mil/DNSKEY: No response was received from the server over TCP (tried 10 times). See RFC 1035, Sec. 4.2. (199.252.143.234, TCP_-_EDNS0_4096_D_N)
mil/DNSKEY: No response was received from the server over TCP (tried 6 times). See RFC 1035, Sec. 4.2. (199.252.157.234, TCP_-_EDNS0_4096_)
mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (199.252.180.234, UDP_-_EDNS0_512_D_KN)
navy.mil zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (131.77.60.235)
navy.mil/DNSKEY: No response was received from the server over TCP (tried 6 times). See RFC 1035, Sec. 4.2. (131.77.60.235, TCP_-_EDNS0_4096_D_KN)
navy.mil/DNSKEY: No response was received from the server over TCP (tried 8 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. (214.23.245.4, UDP_-_EDNS0_4096_D_KN)
navy.mil/DS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (199.252.155.234, UDP_-_NOEDNS_)
navy.mil/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (214.3.125.231, UDP_-_EDNS0_512_D_KN)
navy.mil/NS: No response was received from the server over TCP (tried 4 times). See RFC 1035, Sec. 4.2. (199.252.154.234, TCP_-_EDNS0_4096_D)
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, TCP_-_EDNS0_4096_D_N)
ugcb9ki8rp.navy.mil/A 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.
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/A has errors; select the "Denial of existence" DNSSEC option to see them.
navy.mil/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (15)
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.
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/MX: 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. (214.3.125.231, UDP_-_EDNS0_4096_D_KN)
navy.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. (214.3.125.231, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
navy.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. (214.3.125.231, UDP_-_EDNS0_4096_D_KN)
ugcb9ki8rp.navy.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
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.