NSEC3 proving non-existence of dtra.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 dtra.mil/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
dtra.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
4dv9ylk7ih.dtra.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
dtra.mil/DS has errors; select the "Denial of existence" DNSSEC option to see them.
dtra.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
dtra.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
dtra.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (16)
NSEC3 proving non-existence of dtra.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of dtra.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
mil/DS (alg 8, id 7765): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
mil/DS (alg 8, id 7765): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
mil/DS (alg 8, id 7765): 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 7765): 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 7765): 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. (192.33.4.12, UDP_-_EDNS0_4096_D_K)
mil/DS (alg 8, id 7765): 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. (192.33.4.12, UDP_-_EDNS0_4096_D_K)
mil/DS (alg 8, id 7765): 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. (192.33.4.12, UDP_-_EDNS0_4096_D_K)
mil/DS (alg 8, id 7765): 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. (192.33.4.12, UDP_-_EDNS0_4096_D_K)
dtra.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
4dv9ylk7ih.dtra.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
dtra.mil/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
dtra.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
dtra.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
dtra.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.