state.gov
Updated:
2022-10-27 13:31:49 UTC (758 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (7)
- state.gov/A
- state.gov/AAAA
- state.gov/MX
- state.gov/NS
- state.gov/NSEC3PARAM
- state.gov/SOA
- state.gov/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 18733)
- ./DNSKEY (alg 8, id 20326)
- gov/DNSKEY (alg 8, id 56278)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- state.gov/DNSKEY (alg 8, id 52383)
- state.gov/DNSKEY (alg 8, id 63940)
- state.gov/DNSKEY (alg 8, id 65463)
- state.gov/DS (alg 8, id 63940)
- state.gov/DS (alg 8, id 63940)
Delegation status
Secure (2)
- . to gov
- gov to state.gov
Notices
Errors (2)
- p1gt7sendl.state.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- state.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
- state.gov/DS (alg 8, id 63940): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- state.gov/DS (alg 8, id 63940): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- state.gov/DS (alg 8, id 63940): 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.
- state.gov/DS (alg 8, id 63940): 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.
- p1gt7sendl.state.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- state.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
