ready.gov
Updated:
2022-03-28 16:05:31 UTC (971 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (7)
- ready.gov/A
- ready.gov/AAAA
- ready.gov/AAAA
- ready.gov/NS
- ready.gov/NSEC3PARAM
- ready.gov/SOA
- ready.gov/TXT
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 47671)
- ./DNSKEY (alg 8, id 9799)
- gov/DNSKEY (alg 8, id 7030)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- ready.gov/DNSKEY (alg 8, id 25021)
- ready.gov/DNSKEY (alg 8, id 51768)
- ready.gov/DNSKEY (alg 8, id 9991)
- ready.gov/DS (alg 8, id 25021)
- ready.gov/DS (alg 8, id 25021)
Delegation status
Secure (2)
- . to gov
- gov to ready.gov
Notices
Errors (3)
- ready.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- pwqlgvc5o6.ready.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- ready.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
- ready.gov/DS (alg 8, id 25021): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ready.gov/DS (alg 8, id 25021): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ready.gov/DS (alg 8, id 25021): 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.
- ready.gov/DS (alg 8, id 25021): 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.
- ready.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- pwqlgvc5o6.ready.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- ready.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
