dc3on.gov/DNSKEY (alg 13, id 24485): The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (66.102.236.215, 66.102.236.216, UDP_-_EDNS0_4096_D_K)
dc3on.gov/DNSKEY (alg 13, id 24485): The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (66.102.236.215, 66.102.236.216, UDP_-_EDNS0_4096_D_K)
dc3on.gov/DNSKEY (alg 13, id 56663): The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (66.102.236.215, 66.102.236.216, UDP_-_EDNS0_4096_D_K)
dc3on.gov/DNSKEY (alg 13, id 56663): The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (66.102.236.215, 66.102.236.216, UDP_-_EDNS0_4096_D_K)
dc3on.gov/DNSKEY (alg 8, id 17709): The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (66.102.236.215, 66.102.236.216, UDP_-_EDNS0_4096_D_K)
dc3on.gov/DNSKEY (alg 8, id 17709): The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (66.102.236.215, 66.102.236.216, UDP_-_EDNS0_4096_D_K)
dc3on.gov/DNSKEY (alg 8, id 51010): The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (66.102.236.215, 66.102.236.216, UDP_-_EDNS0_4096_D_K)
dc3on.gov/DNSKEY (alg 8, id 51010): The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (66.102.236.215, 66.102.236.216, UDP_-_EDNS0_4096_D_K)
dc3on.gov/DNSKEY (alg 8, id 54001): The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (66.102.236.215, 66.102.236.216, UDP_-_EDNS0_4096_D_K)
dc3on.gov/DNSKEY (alg 8, id 54001): The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (66.102.236.215, 66.102.236.216, UDP_-_EDNS0_4096_D_K)
dc3on.gov/MX: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (66.102.236.215, 66.102.236.216, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
dc3on.gov/MX: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (66.102.236.215, 66.102.236.216, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
dc3on.gov/NS: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (66.102.236.215, 66.102.236.216, UDP_-_EDNS0_4096_D_K)
dc3on.gov/NS: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (66.102.236.215, 66.102.236.216, UDP_-_EDNS0_4096_D_K)
dc3on.gov/SOA: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (66.102.236.215, 66.102.236.216, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
dc3on.gov/SOA: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (66.102.236.215, 66.102.236.216, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
dc3on.gov/TXT: The DNSKEY RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (66.102.236.215, 66.102.236.216, UDP_-_EDNS0_4096_D_K)
dc3on.gov/TXT: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no RRSIG with algorithm 13 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (66.102.236.215, 66.102.236.216, UDP_-_EDNS0_4096_D_K)
gov to dc3on.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. (66.102.236.215, 66.102.236.216, UDP_-_EDNS0_4096_D_K)
gov to dc3on.gov: The DS RRset for the zone included algorithm 13 (ECDSAP256SHA256), but no DS RR matched a DNSKEY with algorithm 13 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (66.102.236.215, 66.102.236.216, UDP_-_EDNS0_4096_D_K)
gov/DS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:500:12::d0d, UDP_-_NOEDNS_)
dc3on.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
g2rtkpyf0o.dc3on.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
dc3on.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
dc3on.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
dc3on.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (12)
dc3on.gov/DS (alg 13, id 56663): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
dc3on.gov/DS (alg 13, id 56663): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
dc3on.gov/DS (alg 13, id 56663): 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.
dc3on.gov/DS (alg 13, id 56663): 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.
gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
gov/DS (alg 8, id 7698): 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.
gov/DS (alg 8, id 7698): 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.
dc3on.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
g2rtkpyf0o.dc3on.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
dc3on.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
dc3on.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.