Key Takeaways
- A phased, industry-wide rule called Ballot SC-081v3 is shrinking the maximum lifespan of public SSL/TLS certificates, from 398 days down to 200, then 100, then eventually 47.
- The first cut already took effect on March 15, 2026. The next lands March 15, 2027, and the final cut to 47 days lands March 15, 2029.
- The goal is security: a stolen or misused certificate simply can’t be exploited for as long, and shorter lifespans force the industry toward automated renewal instead of manual, error-prone processes.
- Your billing doesn’t change. You still purchase a standard 12-month term. The certificate file itself just needs to be reissued and reinstalled more often within that term.
- Certificates issued before a given cutoff date keep their original validity period until they expire normally. Nothing already installed suddenly stops working.
What’s Actually Changing
Public SSL/TLS certificates, the ones that put the padlock in a browser’s address bar, are getting a lot shorter shelf life. The change comes from Ballot SC-081v3, a rule adopted by the CA/Browser Forum, the industry body of major browser makers and certificate authorities that sets the ground rules for how the web’s trust system works. DigiCert’s own guidance lays out the schedule plainly, and it’s already underway.
Here’s the timeline:
- Through March 14, 2026: maximum validity was 398 days, a little over a year.
- March 15, 2026 (already in effect): maximum validity dropped to 200 days, roughly twice-a-year renewals.
- March 15, 2027: maximum validity drops again to 100 days, about five renewals a year.
- March 15, 2029: maximum validity bottoms out at 47 days, essentially a monthly cycle.
Why the Industry Is Doing This
Three reasons keep coming up, and they all point in the same direction.
The security case is straightforward. A shorter certificate lifespan limits how long a stolen or compromised certificate stays useful to an attacker. If something goes wrong, the damage window shrinks as the validity period shortens.
The second reason is less obvious but arguably more important: certificate revocation has never worked especially well across the broader web. The traditional systems browsers use to check whether a certificate has been revoked, things like certificate revocation lists and the Online Certificate Status Protocol (OCSP), have a long history of being slow or unreliable at scale. If you can’t count on revocation to catch a bad certificate quickly, the next best option is to make sure the certificate expires quickly on its own.
The third reason is really the point of the first two: forcing automation. Nobody is going to manually reissue and reinstall a certificate every 47 days across a large environment without something breaking. That’s by design. The industry is pushing everyone toward automated renewal, typically through a protocol called Automated Certificate Management Environment (ACME), which handles the reissue and reinstall process without a person needing to remember to do it or getting it wrong.
What This Means for Your Business
The practical impact is smaller than the headline number suggests, but it’s still worth understanding clearly.
Your billing arrangement doesn’t change.
You still buy a certificate on a standard 12-month service term. What changes is how many times that certificate file gets reissued and reinstalled within those 12 months. Most major certificate authorities handle the additional reissuances at no extra charge.
Existing certificates are unaffected.
If your certificate was issued before a given transition date, it keeps running on its original validity period until it expires normally. Nothing currently installed and working suddenly breaks or needs attention today.
Manual management gets harder to sustain.
At 200 days, a manual renewal process is annoying but manageable. At 100 days, and especially at 47, manual renewal becomes a real operational risk, since a missed renewal means a site or service going down with a certificate error until someone catches it.
How Emerge Is Handling This for Our Customers
We’re making a few changes on our end to keep this from becoming a surprise for anyone.
- We’ve sent notices to all customers explaining this change, and will send a follow-up reminder in January.
- Every SSL certificate quote now includes a statement clarifying billing: any certification, validation, reissuance, or related compliance work required by our certificate provider during the license term isn’t included in the quoted price and will be billed separately as it’s incurred.
- We’ll still handle the initial installation with every SSL certificate purchase.
- Any additional certification or validation work needed during the license term is billed on a time-and-materials basis.
Our internal team is updating our standard operating procedures and quote templates now, so this is reflected consistently across every new SSL engagement going forward.
What to Do Next
If you manage your own certificates today, this is a good moment to ask whether your renewal process can survive a 100-day cycle, let alone a 47-day one. If the honest answer is “probably not without some scrambling,” automation through a protocol like ACME is worth setting up well before you’re forced into it.
