TLS certificate and CA requirement effective dates (CA/Browser Forum, Chrome, Mozilla)

Forward-dated schedule of when each TLS certificate and certificate authority requirement takes effect, and which programme it binds. Each record is one requirement with its effective date, the Baseline Requirements section it amends, and the authority imposing it. Covers the CA/Browser Forum TLS Baseline Requirements effective-date table, the Google Chrome Root Program policy, and the Mozilla Root Store Policy. Answers 'when does the 200 day certificate lifetime take effect', 'TLS certificate maximum validity 100 days date', '47 day certificates 2029 timeline', 'when does domain validation reuse drop to 200 days', 'SC-081 phased schedule', and 'when do CAs have to do DNSSEC validation'. The dates changed recently and change again with every ballot, so an answer from model memory describes a world that has already moved; the maximum subscriber certificate validity drops to 200 days on 2026-03-15 and to 100 days on 2027-03-15, and the domain-validation reuse period and the subject-identity reuse period fall on different schedules to each other.

The data

Where this came from

Every record above links the page it was taken from and quotes the sentence that states it. These are the 3 sources this dataset was assembled from.

• cabforum.orghttps://cabforum.org/working-groups/server/baseline-requirements/requirements/
• googlechrome.github.iohttps://googlechrome.github.io/chromerootprogram/
• mozilla.orghttps://www.mozilla.org/en-US/about/governance/policies/security-group/certs/policy/

Machine-readable

• data.jsonThe whole dataset — every record with its source URL and source quote.
• Open Knowledge Format bundleOne JSON object per line — every record's frontmatter and quoted span exactly as it is held here, in one fetch.
• How this is made and checkedWhat "verified against source" does and does not mean.

45 records. last verified against source 2026-08-05. due for re-check by 2026-11-03.

Licence. Facts extracted from freely published governance documents. The CA/Browser Forum publishes the Baseline Requirements publicly for implementation; the Chrome Root Program policy and Mozilla Root Store Policy are published openly by their respective root programmes. Each record quotes a short verbatim span and links back to the document section.