dma.mil zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (155.7.145.112)
dma.mil zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (155.7.208.112)
dma.mil/DNSKEY: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (155.7.145.112, TCP_-_EDNS0_4096_D_KN)
dma.mil/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (155.7.208.112, UDP_-_EDNS0_4096_D_KN)
dma.mil/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (155.7.145.112, 155.7.208.112, 155.7.208.113, TCP_-_EDNS0_4096_D_N)
mil zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (199.252.157.234)
mil zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (199.252.155.234)
mil/DNSKEY: No response was received from the server over TCP (tried 4 times). See RFC 1035, Sec. 4.2. (199.252.157.234, TCP_-_EDNS0_4096_D)
mil/DNSKEY: No response was received from the server over TCP (tried 7 times). See RFC 1035, Sec. 4.2. (199.252.155.234, TCP_-_EDNS0_4096_D)
mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (199.252.157.234, UDP_-_EDNS0_512_D_KN)
dma.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
jnco5f9ibv.dma.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
dma.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
dma.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
dma.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (12)
dma.mil/DS (alg 8, id 16930): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
dma.mil/DS (alg 8, id 16930): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
dma.mil/DS (alg 8, id 16930): 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.
dma.mil/DS (alg 8, id 16930): 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): 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.
dma.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
jnco5f9ibv.dma.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
dma.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
dma.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.