NSEC3 proving non-existence of dtic.mil/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of dtic.mil/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
dtic.mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2608:140:c:157::235, UDP_-_EDNS0_512_D_KN)
dtic.mil/DS has errors; select the "Denial of existence" DNSSEC option to see them.
dtic.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
dtic.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
dtic.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
NSEC3 proving non-existence of dtic.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of dtic.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
dtic.mil/A: 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. (199.252.157.235, UDP_-_EDNS0_4096_D_KN)
dtic.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. (199.252.180.243, UDP_-_EDNS0_4096_D_KN)
dtic.mil/DS has warnings; select the "Denial of existence" DNSSEC option to see them.