house.gov
Updated:
2021-04-07 15:12:00 UTC (1333 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- house.gov/A
- house.gov/NS
- house.gov/SOA
- house.gov/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 14631)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 42351)
- gov/DNSKEY (alg 8, id 27306)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- house.gov/DNSKEY (alg 13, id 34842)
- house.gov/DNSKEY (alg 13, id 52436)
- house.gov/DS (alg 13, id 52436)
- house.gov/DS (alg 13, id 52436)
Delegation status
Secure (2)
- . to gov
- gov to house.gov
Notices
Errors (1)
- gov/DS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:500:12::d0d, UDP_-_NOEDNS_)
Warnings (4)
- house.gov/DS (alg 13, id 52436): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- house.gov/DS (alg 13, id 52436): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- house.gov/DS (alg 13, id 52436): 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.
- house.gov/DS (alg 13, id 52436): 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.
JavaScript is required to make the graph below interactive.
