RRSIG gov/DNSKEY alg 8, id 64280: The TTL of the RRset (86400) exceeds the value of the Original TTL field of the RRSIG RR covering it (3600). See RFC 4035, Sec. 2.2.
RRSIG gov/DNSKEY alg 8, id 64280: The TTL of the RRset (86400) exceeds the value of the Original TTL field of the RRSIG RR covering it (3600). See RFC 4035, Sec. 2.2.
RRSIG gov/DNSKEY alg 8, id 64280: The TTL of the RRset (86400) exceeds the value of the Original TTL field of the RRSIG RR covering it (3600). See RFC 4035, Sec. 2.2.
RRSIG gov/DNSKEY alg 8, id 64280: The TTL of the RRset (86400) exceeds the value of the Original TTL field of the RRSIG RR covering it (3600). See RFC 4035, Sec. 2.2.
RRSIG gov/DNSKEY alg 8, id 64280: The TTL of the RRset (86400) exceeds the value of the Original TTL field of the RRSIG RR covering it (3600). See RFC 4035, Sec. 2.2.
cdc.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (25)
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 22623: 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 22623: 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 22623: 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 22623: 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 22544: 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 22544: 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 22544: 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 54678: 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 54678: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG www.akam.cdc.gov/A alg 10, id 21110: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG www.akam.cdc.gov/AAAA alg 10, id 21110: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG www.akam.cdc.gov/AAAA alg 10, id 21110: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG www.cdc.gov/CNAME alg 7, id 22544: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG www.cdc.gov/CNAME alg 7, id 22544: 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): 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. (2600:1403:a::43, 2600:1480:b000::42, UDP_-_EDNS0_4096_D_KN)
akam.cdc.gov/DNSKEY (alg 10, id 21110): 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. (2600:1403:a::43, 2600:1480:b000::42, UDP_-_EDNS0_4096_D_KN)
akam.cdc.gov/DNSKEY (alg 10, id 22623): 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. (2600:1403:a::43, 2600:1480:b000::42, UDP_-_EDNS0_4096_D_KN)
akam.cdc.gov/DNSKEY (alg 10, id 48743): 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. (2600:1403:a::43, 2600:1480:b000::42, UDP_-_EDNS0_4096_D_KN)
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.
cdc.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.