census.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (148.129.75.12, 148.129.129.12, 2610:20:2000:101::19:0, 2610:20:2010:a04::19:0)
census.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (148.129.75.12, 148.129.129.12, 2610:20:2000:101::19:0, 2610:20:2010:a04::19:0, UDP_-_NOEDNS_)
census.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (148.129.75.12, 148.129.129.12, 2610:20:2000:101::19:0, 2610:20:2010:a04::19:0, UDP_-_NOEDNS_)
c8wvflku56.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 (58)
RRSIG census.gov/A alg 7, id 59747: 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 59747: 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 59747: 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 59747: 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 59747: 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 59747: 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 59747: 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 59747: 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 59747: 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 59747: 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 7143: 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 7143: 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 7143: 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 7143: 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 7143: 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 7143: 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 7143: 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 7143: 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 59747: 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 59747: 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 59747: 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 59747: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
census.gov/DNSKEY (alg 7, id 20069): 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 31295): 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 59747): 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 7143): 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 26416): 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 51555): 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 57033): 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 57351): 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.
census.gov/DS (alg 7, id 7143): 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 7143): 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 7143): 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 7143): 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 8, id 2484): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
census.gov/DS (alg 8, id 2484): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
census.gov/DS (alg 8, id 2484): 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 8, id 2484): 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 8, id 26416): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
census.gov/DS (alg 8, id 26416): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
census.gov/DS (alg 8, id 26416): 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 8, id 26416): 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 to census.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): hq-inf-edns01.tco.census.gov, bcc-inf-edns01.tco.census.gov 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.
c8wvflku56.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.