./DNSKEY: No response was received from the server over UDP (tried 16 times). See RFC 1035, Sec. 4.2. (192.112.36.4, UDP_-_EDNS0_4096_D_KN)
akam.cdc.gov/DNSKEY (alg 10, id 11552): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (198.246.96.61, 198.246.96.92, 198.246.125.10, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
akam.cdc.gov/DNSKEY (alg 10, id 4524): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (198.246.96.61, 198.246.96.92, 198.246.125.10, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
cdc.gov to akam.cdc.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. (198.246.96.61, 198.246.96.92, 198.246.125.10, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
cdc.gov to akam.cdc.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. (198.246.96.61, 198.246.96.92, 198.246.125.10, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
covid.akam.cdc.gov/CNAME: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (198.246.96.61, 198.246.96.92, 198.246.125.10, UDP_-_EDNS0_4096_D_KN)
cdc.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (45)
RRSIG akam.cdc.gov/DNSKEY alg 10, id 1993: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG akam.cdc.gov/DNSKEY alg 10, id 1993: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG akam.cdc.gov/DNSKEY alg 10, id 1993: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG akam.cdc.gov/DNSKEY alg 10, id 1993: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG akam.cdc.gov/DNSKEY alg 10, id 4524: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG akam.cdc.gov/DNSKEY alg 10, id 4524: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG akam.cdc.gov/DNSKEY alg 10, id 4524: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG akam.cdc.gov/DNSKEY alg 10, id 4524: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG akam.cdc.gov/DS alg 7, id 9155: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG cdc.gov/DNSKEY alg 7, id 65139: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG cdc.gov/DNSKEY alg 7, id 65139: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG cdc.gov/DNSKEY alg 7, id 9155: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG cdc.gov/DNSKEY alg 7, id 9155: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG covid.akam.cdc.gov/A alg 10, id 11552: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG covid.akam.cdc.gov/A alg 10, id 11552: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG covid.akam.cdc.gov/AAAA alg 10, id 11552: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG covid.akam.cdc.gov/AAAA alg 10, id 11552: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG covid.cdc.gov/CNAME alg 7, id 9155: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG covid.cdc.gov/CNAME alg 7, id 9155: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
akam.cdc.gov/DNSKEY (alg 10, id 1993): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (198.246.96.61, 198.246.96.92, 198.246.125.10, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
akam.cdc.gov/DNSKEY (alg 10, id 41895): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (198.246.96.61, 198.246.96.92, 198.246.125.10, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
akamaiedge.net to dscb.akamaiedge.net: The glue address(es) for n1dscb.akamaiedge.net (23.61.195.181, 128.241.216.214) differed from its authoritative address(es) (23.61.195.181). See RFC 1034, Sec. 4.2.2.
akamaiedge.net to dscb.akamaiedge.net: The glue address(es) for n2dscb.akamaiedge.net (63.141.195.103, 128.241.216.199) differed from its authoritative address(es) (63.141.195.103). See RFC 1034, Sec. 4.2.2.
akamaiedge.net to dscb.akamaiedge.net: The glue address(es) for n3dscb.akamaiedge.net (23.61.195.186, 128.241.216.206) differed from its authoritative address(es) (23.61.195.186). See RFC 1034, Sec. 4.2.2.
akamaiedge.net to dscb.akamaiedge.net: The glue address(es) for n4dscb.akamaiedge.net (23.61.195.164, 63.217.232.36) differed from its authoritative address(es) (23.61.195.164). See RFC 1034, Sec. 4.2.2.
akamaiedge.net to dscb.akamaiedge.net: The glue address(es) for n5dscb.akamaiedge.net (23.61.195.166, 128.241.220.29) differed from its authoritative address(es) (23.61.195.166). See RFC 1034, Sec. 4.2.2.
akamaiedge.net to dscb.akamaiedge.net: The glue address(es) for n6dscb.akamaiedge.net (63.233.61.218, 128.241.216.208) differed from its authoritative address(es) (63.233.61.218). See RFC 1034, Sec. 4.2.2.
akamaiedge.net to dscb.akamaiedge.net: The glue address(es) for n7dscb.akamaiedge.net (23.61.195.183, 72.246.199.57) differed from its authoritative address(es) (23.61.195.183). See RFC 1034, Sec. 4.2.2.
cdc.gov/DS (alg 7, id 65139): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
cdc.gov/DS (alg 7, id 65139): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
cdc.gov/DS (alg 7, id 65139): 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.
cdc.gov/DS (alg 7, id 65139): 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.
covid.akam.cdc.gov/CNAME: The server returned CNAME for covid.akam.cdc.gov, but records of other types exist at that name. See RFC 2181, Sec. 10.1.
gov to cdc.gov: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the gov zone): icdc-us-ns1.cdc.gov, icdc-us-ns3.cdc.gov, icdc-us-ns2.cdc.gov See RFC 1034, Sec. 4.2.2.
gov to cdc.gov: The following NS name(s) were found in the delegation NS RRset (i.e., in the gov zone), but not in the authoritative NS RRset: auth00.ns.uu.net, auth100.ns.uu.net See RFC 1034, Sec. 4.2.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): 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.
net to akamaiedge.net: Authoritative AAAA records exist for a11-192.akamaiedge.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
net to edgekey.net: Authoritative AAAA records exist for a13-65.akam.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
net to edgekey.net: Authoritative AAAA records exist for a5-65.akam.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
net to edgekey.net: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the net zone): a11-65.akam.net, ns1-2.akam.net, a9-65.akam.net, a3-65.akam.net See RFC 1034, Sec. 4.2.2.
net to edgekey.net: The following NS name(s) were found in the delegation NS RRset (i.e., in the net zone), but not in the authoritative NS RRset: ns1-66.akam.net, ns4-66.akam.net, ns5-66.akam.net, ns7-65.akam.net See RFC 1034, Sec. 4.2.2.
cdc.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.