← Guides

SSL certificates are moving to 47 days: the 2026 to 2029 timeline

Updated 2026-11-22. Sources are listed at the end.

In April 2025 the CA/Browser Forum adopted Ballot SC-081v3, which reduces the maximum validity of publicly trusted TLS certificates from 398 days to 47 days in steps between March 2026 and March 2029. It also shortens how long a CA may reuse a domain validation.

The timeline

Maximum TLS certificate validity and domain validation reuse (Ballot SC-081v3)
Certificates issuedMaximum validityMaximum reuse of domain validationRenewals per year, roughly
Before 15 March 2026398 days398 days1
From 15 March 2026200 days200 days2
From 15 March 2027100 days100 days4
From 15 March 202947 days10 days8

The last column is our arithmetic (365 days divided by the maximum validity, rounded); in practice you renew before expiry, so slightly more often. The 200-day limit already applies to certificates issued since 15 March 2026.

What changes for you

  • Manual renewals multiply. A certificate bought and installed by hand once a year will need that work about eight times a year by 2029.
  • Domain validation repeats. With 10-day reuse in 2029, proving control of the domain becomes part of nearly every renewal.
  • Automation becomes the norm. ACME, the protocol Let's Encrypt uses, is the usual way to automate issuance and renewal.

How to prepare

  1. Make an inventory. List every hostname with a certificate. CT logs show what has been issued for your domains (see how to search CT logs).
  2. Find the manual ones. Long validity periods, commercial issuers and irregular renewal dates are signs of hand renewal.
  3. Automate what you can with an ACME client, and document the rest (appliances, load balancers, hosted services) with an owner for each.
  4. Monitor expiry for everything, automated or not. Automation fails quietly (see why Let's Encrypt renewals fail).

Doing this for many domains?

Lindenkit flags certificates that look manually renewed (by issuer, lifetime and renewal history), which are the ones that will need hand renewal 2, then 4, then about 8 times a year. The flag is an estimate, not a certainty.

Lindenkit Certificates lists the certificates logged in public Certificate Transparency logs for each domain you add, tracks the domain's registration expiry through RDAP, and emails you 30, 14, 7 and 1 days before either lapses. It reads public data and does not connect to your servers, so it shows the latest certificate per CT logs, which may not be the one a server presents. Free for up to 10 certificates; Base US$29/month for 100.

How Lindenkit Certificates works Try the free checker

Sources