army.mil/NSEC3PARAM: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (192.82.113.7, UDP_-_NOEDNS_)
sfbkyet7v4.army.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
army.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
army.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
army.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (17)
. to mil: Authoritative AAAA records exist for con1.nipr.mil, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
. to mil: Authoritative AAAA records exist for con2.nipr.mil, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
. to mil: Authoritative AAAA records exist for eur1.nipr.mil, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
. to mil: Authoritative AAAA records exist for eur2.nipr.mil, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
. to mil: Authoritative AAAA records exist for pac1.nipr.mil, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
. to mil: Authoritative AAAA records exist for pac2.nipr.mil, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
army.mil/DS (alg 8, id 26374): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
army.mil/DS (alg 8, id 26374): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
army.mil/DS (alg 8, id 26374): 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.
army.mil/DS (alg 8, id 26374): 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.
army.mil/NSEC3PARAM: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (140.153.43.44, UDP_-_EDNS0_4096_D_KN)
mil/DNSKEY (alg 8, id 25191): 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.162.234, UDP_-_EDNS0_4096_D_KN)
mil/DNSKEY (alg 8, id 56347): 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.162.234, UDP_-_EDNS0_4096_D_KN)
sfbkyet7v4.army.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
army.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
army.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
army.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.