Guide, updated November 2026
The 47-day certificate era: every date from 2026 to 2029.
Publicly trusted TLS certificates lose more than half their maximum lifetime in three steps, and the last step lands in March 2029. For an agency running care plans, the deadline is not the interesting part. The interesting part is that each step multiplies the number of renewals that can fail without anyone noticing.
The schedule
Ballot SC-081v3 amends the CA/Browser Forum TLS Baseline Requirements, the rulebook every publicly trusted certificate authority has to follow. It sets a maximum validity period plus a maximum domain validation reuse period, both on the same three-date ladder.
| Phase | Takes effect | Max validity | Renewals a year |
|---|---|---|---|
| In force now | Before 15 March 2026 | 398 days | About one a year |
| Phase 1 | 15 March 2026 | 200 days | About two a year |
| Phase 2 | 15 March 2027 | 100 days | About four a year |
| Phase 3 | 15 March 2029 | 47 days | About eight a year |
The ballot passed on 11 April 2025 with 25 certificate issuers and all four major browsers voting yes. Validation reuse limits fall on the same dates, which means revalidating a domain more often than once a year is now part of every renewal path.
Why agencies feel it first
In a single company, one platform team owns certificates and one automation renews them. An agency owns a portfolio: a Webflow site here, a Shopify store there, a WordPress install on a shared host, a Squarespace page from 2021, and always one client on a VPS that a former freelancer configured. Each stack has its own renewal story, and none of them tell you when they fail.
Certificate failure is also the least forgiving kind of maintenance failure. DNS changes are invisible, SPF overflow is invisible until mail bounces, but an expired certificate is a full page browser warning that a client will screenshot and send to their own boss. It does not matter that the site is otherwise fine.
Five things break on the way down
Manual renewal calendars
A 398-day certificate survives a year of someone forgetting. A 47-day certificate survives six weeks. Any client renewal that depends on a note in a project management tool becomes a monthly job.
ACME clients tuned to 90 days
Most automation was built around a 90-day cadence and a comfortable human fallback window. At 47 days the fallback disappears: an ACME failure has to page someone the same week, or the client sees a browser interstitial first.
Alert thresholds set at 30 days
A 30-day warning on a 47-day certificate fires when two thirds of its life is gone. Useful alerts move to 14, 7 and 2 days, with a check cadence measured in hours rather than days.
Certificate pinning and hardcoded fingerprints
Pinning a leaf certificate to a short-lived certificate breaks the client on renewal. Pin the intermediate or the public key instead, or remove the pin.
Hosts that terminate TLS for you
Webflow, Shopify and Squarespace handle certificates on their own infrastructure. The risk moves to the domains that do not: legacy VPS hosting, marketing landing pages, client mail subdomains, and anything a former developer set up once.
The agency playbook
- 01
Inventory every hostname, not every site
api., shop., mail., booking., staging. Each one is a separate certificate with a separate renewal path.
- 02
Confirm automation per hostname
Record the ACME client, the account email and who owns the DNS challenge. Unknown ownership is the failure mode.
- 03
Move validation ahead of the deadline
Revalidate before each phase. A 200-day certificate issued in February 2026 still expires after the Phase 2 cutover.
- 04
Re-tune alert thresholds before Phase 2
14, 7 and 2 days, checked every 6 hours. Anything coarser turns an outage warning into an outage report.
- 05
Fix email authentication in the same pass
A certificate failure is loud. SPF and DMARC failures are silent: invoices and password resets get rejected or filed as spam.
- 06
Produce a client-facing artifact
The client pays for a care plan. Give them a line item that says the certificate is healthy and 41 days from renewal, rather than asking them to trust you.
- 07
Rehearse one renewal by hand
Break the automation on a staging domain once. You will learn more about your dashboard than in any audit.
Sources
- CA/Browser Forum, Ballot SC-081v3: Introduce Schedule of Reducing Validity and Data Reuse Periods, 11 April 2025.
- SSL.com, Preparing for 47-day SSL/TLS certificates.
- Microsoft, Outlook's new requirements for high-volume senders, the parallel pressure on email authentication.