NSEC3 proving non-existence of dds.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 dds.mil/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
dds.mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2608:120:c:162::243, UDP_-_EDNS0_512_D_KN)
dds.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
dds.mil/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
NSEC3 proving non-existence of dds.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of dds.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
dds.mil/DS (alg 13, id 37555): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
dds.mil/DS (alg 13, id 37555): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
dds.mil/DS (alg 13, id 37555): 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.
dds.mil/DS (alg 13, id 37555): 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.
dds.mil/DS has warnings; select the "Denial of existence" DNSSEC option to see them.