gov to nwcg.gov: 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. (199.134.208.70, 199.134.208.90, 199.134.227.132, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
gov to nwcg.gov: The DS RRset for the zone included algorithm 10 (RSASHA512), but no DS RR matched a DNSKEY with algorithm 10 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.134.208.70, 199.134.208.90, 199.134.227.132, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
nwcg.gov/A: The DS RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.134.208.70, 199.134.208.90, 199.134.227.132, UDP_-_EDNS0_4096_D_KN)
nwcg.gov/DNSKEY (alg 13, id 24766): The DS RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.134.208.70, 199.134.208.90, 199.134.227.132, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
nwcg.gov/DNSKEY (alg 13, id 63883): The DS RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.134.208.70, 199.134.208.90, 199.134.227.132, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
nwcg.gov/NS: The DS RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.134.208.70, 199.134.208.90, 199.134.227.132, UDP_-_EDNS0_4096_D_KN)
nwcg.gov/NSEC3PARAM: The DS RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.134.208.70, 199.134.208.90, 199.134.227.132, UDP_-_EDNS0_4096_D_KN)
nwcg.gov/SOA: The DS RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.134.208.70, 199.134.208.90, 199.134.227.132, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
nwcg.gov/TXT: The DS RRset for the zone included algorithm 10 (RSASHA512), but no RRSIG with algorithm 10 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.134.208.70, 199.134.208.90, 199.134.227.132, UDP_-_EDNS0_4096_D_KN)
nwcg.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
nwcg.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
nwcg.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
nwcg.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
t91do0h2uj.nwcg.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
nwcg.gov/TXT: 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.134.208.70, UDP_-_EDNS0_4096_D_KN)
t91do0h2uj.nwcg.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
nwcg.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
nwcg.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
nwcg.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.