capitol.gov
Updated:
2020-07-06 13:19:33 UTC (1599 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- capitol.gov/A
- capitol.gov/MX
- capitol.gov/NS
- capitol.gov/SOA
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46594)
- ./DNSKEY (alg 8, id 48903)
- capitol.gov/DNSKEY (alg 8, id 19836)
- capitol.gov/DNSKEY (alg 8, id 23373)
- capitol.gov/DNSKEY (alg 8, id 48772)
- capitol.gov/DS (alg 8, id 48772)
- capitol.gov/DS (alg 8, id 48772)
- gov/DNSKEY (alg 8, id 40176)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Secure (2)
- . to gov
- gov to capitol.gov
Notices
Warnings (8)
- capitol.gov/DS (alg 8, id 48772): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- capitol.gov/DS (alg 8, id 48772): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- capitol.gov/DS (alg 8, id 48772): 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.
- capitol.gov/DS (alg 8, id 48772): 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): 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.
JavaScript is required to make the graph below interactive.
