dma.mil/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.145.112, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
dma.mil/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.145.112, UDP_-_EDNS0_4096_D_KN)
dma.mil/NSEC3PARAM: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.145.112, 155.7.145.113, 155.7.208.113, UDP_-_EDNS0_4096_D_KN)
dma.mil/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.145.112, 155.7.208.113, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
dma.mil/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (155.7.145.112, UDP_-_EDNS0_4096_D_KN)
mil to dma.mil: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (155.7.145.112, 155.7.145.113, 155.7.208.112, 155.7.208.113, TCP_-_EDNS0_4096_D_KN)
mil to dma.mil: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (155.7.145.112, 155.7.145.113, 155.7.208.112, 155.7.208.113, TCP_-_EDNS0_4096_D_KN)
mil zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2608:140:c:157::234)
dma.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
mdog78i2q0.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.
Warnings (21)
dma.mil/DS (alg 8, id 10672): 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 10672): 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 10672): 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 10672): 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 10672): 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. (2608:120:c:162::234, UDP_-_EDNS0_4096_D_KN)
dma.mil/DS (alg 8, id 10672): 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. (2608:120:c:162::234, UDP_-_EDNS0_4096_D_KN)
dma.mil/DS (alg 8, id 10672): 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. (2608:120:c:162::234, UDP_-_EDNS0_4096_D_KN)
dma.mil/DS (alg 8, id 10672): 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. (2608:120:c:162::234, UDP_-_EDNS0_4096_D_KN)
dma.mil/DS (alg 8, id 29437): 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 29437): 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 29437): 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 29437): 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 29437): 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. (2608:120:c:162::234, UDP_-_EDNS0_4096_D_KN)
dma.mil/DS (alg 8, id 29437): 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. (2608:120:c:162::234, UDP_-_EDNS0_4096_D_KN)
dma.mil/DS (alg 8, id 29437): 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. (2608:120:c:162::234, UDP_-_EDNS0_4096_D_KN)
dma.mil/DS (alg 8, id 29437): 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. (2608:120:c:162::234, UDP_-_EDNS0_4096_D_KN)
dma.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
mdog78i2q0.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.
dma.mil/DS has warnings; select the "Denial of existence" DNSSEC option to see them.