congress.gov

Updated: 2020-03-27 01:27:45 UTC (1702 days ago) Go to most recent »

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 33853)
./DNSKEY (alg 8, id 48903)
congress.gov/DS (alg 8, id 27310)
congress.gov/DS (alg 8, id 32782)
gov/DNSKEY (alg 8, id 36558)
gov/DNSKEY (alg 8, id 7698)
gov/DS (alg 8, id 7698)
gov/DS (alg 8, id 7698)

congress.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (140.147.32.166, 140.147.239.150)
congress.gov zone: There was an error resolving the following NS name(s) to address(es): ns21.loc.gov, ns23.loc.gov
congress.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.147.32.166, 140.147.239.150, UDP_-_NOEDNS_)
congress.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (140.147.32.166, 140.147.239.150, UDP_-_NOEDNS_)
gov to congress.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.

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.