Certificate renewal is becoming somebody's job
The first cut landed in March 2026. The next one arrives in March 2027. Anyone still renewing certificates by hand is about to find out how often.
On 11 April 2025 the CA/Browser Forum, the body that sets the rules every public certificate authority follows, passed ballot SC-081v3. It cuts the maximum life of a public TLS certificate from 398 days to 47 days in three steps: 200 days from 15 March 2026, 100 days from 15 March 2027 and 47 days from 15 March 2029. The first step is already in force.
The same ballot cuts how long a certificate authority may reuse the evidence that you control your own domain, on the same dates: 200 days, then 100, then 10.
The free automated issuers are moving as well. Let's Encrypt will shorten its default certificate from 90 days to 64 days on 10 February 2027 and to 45 days on 16 February 2028.
What that actually changes
If your certificate renews itself, nothing. Automated issuance already runs on short lifetimes and shorter ones cost you nothing.
If somebody renews it by hand once a year, the arithmetic changes underneath them. From next March a 100 day certificate needs replacing at least four times a year, and a 47 day certificate roughly eight times a year. A task that was an annual diary entry becomes a recurring operational duty, and the failure mode is not subtle: a browser refuses to load the site and tells every visitor it is not safe.
Who this catches
When we measured 95 companies in one industry, 8 were running certificates with a lifetime beyond 180 days. Those are the manually managed ones. The rest were on 90 day certificates that renew themselves, which is why a short remaining life on one of those is nothing to worry about and a short remaining life on a long certificate is.
That distinction matters more than it sounds. Plenty of monitoring tools will warn you that a certificate expires in three weeks. On an automated 90 day certificate that is routine. On a 397 day certificate it means a person has to do something, and the person in question usually does not know the certificate exists.
What to do
- Find out whether your certificate is automated. A lifetime of 90 days or less usually means it is. A lifetime near 200 days, or a full year on an older certificate, means it is not.
- If it is not, move to automated renewal before 15 March 2027 rather than after. The work is the same either way, and from that date a manual certificate means at least four renewals a year.
- Check every domain you own, not only the main one. Parked domains, campaign domains and the old company name all present certificates to somebody.
This is a small thing. It is on this blog because it is a small thing with a public failure mode, arriving on a schedule nobody outside the certificate industry has read.
Sources
- CA/Browser Forum, Ballot SC-081v3 : passed 11 April 2025. Maximum validity 200 days from 15 March 2026, 100 days from 15 March 2027, 47 days from 15 March 2029; domain validation reuse 200, 100, then 10 days on the same dates, per the Baseline Requirements.
- Let's Encrypt, Decreasing certificate lifetimes to 45 days: default certificate 64 days from 10 February 2027, 45 days from 16 February 2028.
- Our own measurement of 95 companies, 18 September 2026. Method in What we found on 95 company websites.
Worth two minutes
Open your site, click the padlock, and look at the issue and expiry dates. If they are about 90 days apart you can stop reading. If they are a year apart, somebody needs to own this.