letsencrypt / letsencrypt/cp-cps
Add description of DNSSEC validation to 3.2.2
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 38
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
Validation of DNSSEC information becomes mandatory on 2026-03-15. We already do this, but don't mention it in our CP/CPS.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate section 3.2.2 in the CP/CPS documents and review how DNSSEC validation is described elsewhere. Confirm that the section documents the existing validation practice and the upcoming mandatory requirement; done when the CP/CPS clearly covers it and documentation checks pass.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100