eucom.mil zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (215.76.62.35)
eucom.mil/NS: The DNSKEY RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (137.95.4.157, 137.95.4.158, UDP_-_EDNS0_4096_D_KN)
eucom.mil/NS: The DNSKEY RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (215.76.62.34, 215.76.62.35, UDP_-_EDNS0_4096_D_KN)
eucom.mil/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (215.76.62.35, TCP_-_EDNS0_4096_D_N)
eucom.mil/SOA: The DNSKEY RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (137.95.4.157, 137.95.4.158, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
eucom.mil/SOA: The DNSKEY RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (215.76.62.34, 215.76.62.35, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
eucom.mil/TXT: The DNSKEY RRset for the zone included algorithm 5 (RSASHA1), but no RRSIG with algorithm 5 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (137.95.4.157, 137.95.4.158, 215.76.62.34, 215.76.62.35, UDP_-_EDNS0_4096_D_KN)
mil to eucom.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. (137.95.4.157, 137.95.4.158, 215.76.62.34, 215.76.62.35, UDP_-_EDNS0_4096_D_KN)
mil to eucom.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. (137.95.4.157, 137.95.4.158, 215.76.62.34, 215.76.62.35, UDP_-_EDNS0_4096_D_KN)
w95lu2xjpq.eucom.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
eucom.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
eucom.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
eucom.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
eucom.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
eucom.mil/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (14)
RRSIG eucom.mil/DNSKEY alg 5, id 47848: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG eucom.mil/DNSKEY alg 5, id 47848: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG eucom.mil/DNSKEY alg 5, id 47848: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG eucom.mil/DNSKEY alg 5, id 47848: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
eucom.mil/DNSKEY: The Authoritative Answer (AA) flag was not set in the response. See RFC 1035, Sec. 4.1.1. (137.95.4.157, 137.95.4.158, 215.76.62.34, 215.76.62.35, UDP_-_EDNS0_512_D_KN)
eucom.mil/DNSKEY: The server responded with no OPT record, rather than with RCODE FORMERR. See RFC 6891, Sec. 7. (137.95.4.157, 137.95.4.158, 215.76.62.34, 215.76.62.35, UDP_-_EDNS0_512_D_KN)
eucom.mil/DS (alg 8, id 37915): 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:c144:1:155::234, UDP_-_EDNS0_4096_D_KN)
eucom.mil/DS (alg 8, id 37915): 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:c144:1:155::234, UDP_-_EDNS0_4096_D_KN)
mil/DNSKEY (alg 8, id 1773): 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:c184:1:180::234, UDP_-_EDNS0_4096_D_KN)
mil/DNSKEY (alg 8, id 53035): 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:c184:1:180::234, UDP_-_EDNS0_4096_D_KN)
mil/DNSKEY (alg 8, id 62470): 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:c184:1:180::234, UDP_-_EDNS0_4096_D_KN)
eucom.mil/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
eucom.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
eucom.mil/DS has warnings; select the "Denial of existence" DNSSEC option to see them.