gov to census.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. (23.211.132.67, 84.53.139.66, 95.100.173.64, 96.7.49.65, 96.7.50.65, 148.129.75.11, 148.129.129.31, 193.108.91.22, 2600:1401:2::16, 2600:1406:1b::43, 2600:1408:1c::41, 2600:1480:1::42, 2610:20:2000:101::18:0, 2610:20:2010:a04::18:0, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
gov to census.gov: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no DS RR matched a DNSKEY with algorithm 7 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (23.211.132.67, 84.53.139.66, 95.100.173.64, 96.7.49.65, 96.7.50.65, 148.129.75.11, 148.129.129.31, 193.108.91.22, 2600:1401:2::16, 2600:1406:1b::43, 2600:1408:1c::41, 2600:1480:1::42, 2610:20:2000:101::18:0, 2610:20:2010:a04::18:0, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
gov to census.gov: 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. (23.211.132.67, 84.53.139.66, 95.100.173.64, 96.7.49.65, 96.7.50.65, 148.129.75.11, 148.129.129.31, 193.108.91.22, 2600:1401:2::16, 2600:1406:1b::43, 2600:1408:1c::41, 2600:1480:1::42, 2610:20:2000:101::18:0, 2610:20:2010:a04::18:0, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
id90eu6bmj.census.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
census.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (42)
RRSIG census.gov/A alg 7, id 34973: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG census.gov/AAAA alg 7, id 34973: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG census.gov/DNSKEY alg 7, id 34973: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG census.gov/DNSKEY alg 7, id 34973: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG census.gov/DNSKEY alg 7, id 34973: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG census.gov/DNSKEY alg 7, id 34973: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG census.gov/DNSKEY alg 7, id 34973: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG census.gov/DNSKEY alg 7, id 34973: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG census.gov/DNSKEY alg 7, id 34973: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG census.gov/DNSKEY alg 7, id 34973: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG census.gov/DNSKEY alg 7, id 44298: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG census.gov/DNSKEY alg 7, id 44298: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG census.gov/DNSKEY alg 7, id 44298: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG census.gov/DNSKEY alg 7, id 44298: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG census.gov/DNSKEY alg 7, id 44298: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG census.gov/DNSKEY alg 7, id 44298: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG census.gov/DNSKEY alg 7, id 44298: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG census.gov/DNSKEY alg 7, id 44298: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG census.gov/MX alg 7, id 34973: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG census.gov/NS alg 7, id 34973: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG census.gov/NSEC3PARAM alg 7, id 34973: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG census.gov/SOA alg 7, id 34973: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG census.gov/TXT alg 7, id 34973: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
census.gov/DNSKEY (alg 7, id 18350): 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. (2610:20:2000:101::18:0, 2610:20:2010:a04::18:0, UDP_-_EDNS0_4096_D_KN)
census.gov/DNSKEY (alg 7, id 34973): 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. (2610:20:2000:101::18:0, 2610:20:2010:a04::18:0, UDP_-_EDNS0_4096_D_KN)
census.gov/DNSKEY (alg 7, id 44298): 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. (2610:20:2000:101::18:0, 2610:20:2010:a04::18:0, UDP_-_EDNS0_4096_D_KN)
census.gov/DNSKEY (alg 7, id 7133): 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. (2610:20:2000:101::18:0, 2610:20:2010:a04::18:0, UDP_-_EDNS0_4096_D_KN)
census.gov/DNSKEY (alg 8, id 11455): 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. (2610:20:2000:101::18:0, 2610:20:2010:a04::18:0, UDP_-_EDNS0_4096_D_KN)
census.gov/DNSKEY (alg 8, id 24261): 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. (2610:20:2000:101::18:0, 2610:20:2010:a04::18:0, UDP_-_EDNS0_4096_D_KN)
census.gov/DNSKEY (alg 8, id 40401): 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. (2610:20:2000:101::18:0, 2610:20:2010:a04::18:0, UDP_-_EDNS0_4096_D_KN)
census.gov/DNSKEY (alg 8, id 43518): 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. (2610:20:2000:101::18:0, 2610:20:2010:a04::18:0, UDP_-_EDNS0_4096_D_KN)
census.gov/DS (alg 7, id 21455): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
census.gov/DS (alg 7, id 21455): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
census.gov/DS (alg 7, id 21455): 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.
census.gov/DS (alg 7, id 21455): 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.
census.gov/DS (alg 7, id 57002): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
census.gov/DS (alg 7, id 57002): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
census.gov/DS (alg 7, id 57002): 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.
census.gov/DS (alg 7, id 57002): 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.
id90eu6bmj.census.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
census.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
census.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.