SSL certificate 200-day validity: the 2026 limit explained
Trusted TLS certificates issued from 15 March 2026 can last at most 200 days, then 100 days in 2027 and 47 in 2029. The schedule, and what to change.
Since 15 March 2026, a publicly trusted TLS certificate can be valid for at most 200 days. The limit falls to 100 days for certificates issued on or after 15 March 2027 and to 47 days on or after 15 March 2029. The schedule comes from CA/Browser Forum ballot SC-081v3, which passed in April 2025. For an agency managing certificates across many client hosts, the practical effect is that renewal stops being an annual task and becomes something you monitor.
What the baseline requirements now say
The CA/Browser Forum writes the rule as a pair of limits, one advisory and one mandatory. For the current period the Baseline Requirements say a certificate “issued on or after 2026-03-15 and before 2027-03-15 SHOULD NOT have a Validity Period greater than 199 days and MUST NOT have a Validity Period greater than 200 days”.
The earlier rule still matters for certificates already in the wild: “Subscriber Certificates issued before 2026-03-15 SHOULD NOT have a Validity Period greater than 397 days and MUST NOT have a Validity Period greater than 398 days.”
A day is not a calendar day in this calculation. The requirements state: “For the purpose of calculations, a day is measured as 86,400 seconds.”
The 2027 and 2029 steps use the same structure. Certificates issued from 15 March 2027 must not exceed 100 days, and certificates issued from 15 March 2029 must not exceed 47 days.
The full SC-081 schedule
The validity cut is only half of the change. The ballot also shortens how long a CA may reuse validation data, which is the check that the applicant controls the domain.
| Certificate issued | Maximum validity | Domain and IP validation reuse | Subject identity reuse |
|---|---|---|---|
| Before 15 March 2026 | 398 days | 398 days | 825 days |
| 15 March 2026 to 14 March 2027 | 200 days | 200 days | 398 days |
| 15 March 2027 to 14 March 2029 | 100 days | 100 days | 398 days |
| On or after 15 March 2029 | 47 days | 10 days | 398 days |
The domain and IP reuse period falls from 398 days to 200, then 100, then 10. Subject identity reuse drops from 825 days to 398 days on 15 March 2026 and stays there.
The definition of a short-lived certificate also tightens on 15 March 2026: “For Certificates issued on or after 2026-03-15, a Subscriber Certificate with a Validity Period less than or equal to 7 days (604,800 seconds).” Let’s Encrypt already issues certificates in that range, covered below.
How the ballot passed
SC-081v3 was not a close vote. Voting ran from 4 to 11 April 2025, quorum was 16, and every bylaw requirement was marked MET. Certificate issuers cast 30 votes: 25 yes, 0 no, 5 abstain. The abstainers were “Entrust, IdenTrust, Japan Registry Services, SECOM Trust Systems, TWCA”.
Certificate consumers voted “4 voting YES: Apple, Google, Microsoft, Mozilla”. The ballot was “proposed by Clint Wilson (Apple) and endorsed by Nick France (Sectigo), Ryan Dickson (Google Chrome), and Ben Wilson (Mozilla)”. Discussion opened on 28 January 2025.
The proposal had been visible for months. Apple opened GitHub pull request #553 on 9 October 2024, and at the F2F 63 meeting that day Wilson said: “I have a proposed change for the TLS BRs that would provide a more phased approach to the lifetime reduction”. The original schedule in that pull request is no longer visible; the description now shows the final 47-day text.
Why the Forum made the change
The ballot gives three reasons. On reliability: “a reduction to both certificate lifetimes and data reuse periods increases the average net reliability of certificates”. On revocation: “A reduction to certificate lifetimes provides firm protection to users, independent of certificate status services”. On automation, it says wider deployment of bi-directional automation “is not a panacea for challenges in the Web PKI, but it certainly helps”.
Chrome’s root program makes the validation point directly: “Previously, a single validation check could be used for over two years, creating a risk that certificates were issued based on stale ownership information.”
What changes for a portfolio of client sites
A 398-day certificate could be renewed once a year and still leave slack. At 200 days, a host needs more than one renewal a year. At 100 days, it needs roughly four. At 47 days, renewal becomes a recurring operational task, and a missed reminder turns into an outage.
The failure mode is not the CA. It is the client site where auto-renew was never enabled, the staging host nobody inventoried, the www record on a different certificate, or the CDN certificate managed in a dashboard that the agency does not control. A manual calendar reminder across 30 client sites and several hostnames each is a lot of chances to miss one.
Domain expiry is a separate failure with a different recovery path. If you are triaging a site that has dropped out of search, check both: what happens when a domain expires covers the registration side, while this article covers the certificate side.
Automate renewal, and watch the automation
Let’s Encrypt has published its own timetable. It currently issues 90-day certificates, “which will be cut in half to 45 days by 2028”. Its authorisation reuse period “is currently 30 days, which will be reduced to 7 hours by 2028”.
The intermediate steps matter for planning. On 13 May 2026 the opt-in tlsserver profile moves to 45 days. On 10 February 2027 the default classic ACME profile moves to 64-day certificates with a 10-day authorisation reuse period. On 16 February 2028 the classic profile moves to 45 days with 7-hour reuse. Let’s Encrypt made 6-day certificates generally available on 15 January 2026; those are “valid for 160 hours, just over six days” and remain opt-in.
Fixed renewal intervals stop working. Let’s Encrypt warns that “renewing at a hardcoded interval of 60 days will no longer be sufficient” and says acceptable behaviour includes renewing at about two thirds of the certificate’s lifetime. It also asks operators to ensure their systems alert appropriately if certificates are not renewed when expected.
If your ACME client is configured with a fixed sleep or a cron job that runs on day 60, change it before the next step in the schedule. Renewal should be driven by the certificate’s remaining lifetime, not by a calendar.
What an expired certificate does
Browsers show a certificate error page, and an HTTPS connection does not complete. Chromium reports the condition as: “The server responded with a certificate that, by our clock, appears to either not yet be valid or to have expired.” Chrome Help lists “Your connection is not private” among certificate errors, though its page attributes NET::ERR_CERT_DATE_INVALID only to an inaccurate device clock and does not document the expired server certificate case.
For search, keep the claim small. Google’s documented HTTPS signal dates from 2014, when it said “we’re starting to use HTTPS as a ranking signal” and described it as lightweight, affecting fewer than 1% of global queries. Google’s page experience documentation still asks site owners: “Are your pages served in a secure fashion?” An expired certificate also stops any crawler or monitoring service that fetches over HTTPS, because the connection fails before the page is read.
The SEO detail is less important than the operational one: the site is unreachable over HTTPS until the certificate is replaced. For the search-side consequences and recovery, see SSL and domain expiry: the boring disasters.
A renewal checklist for agencies
- Inventory every hostname, not every site. Include
www, subdomains, staging hosts, and any certificate terminated at a CDN or reverse proxy. - Confirm auto-renew is enabled on each host, then confirm the renewal task actually runs. A dashboard toggle is not evidence.
- Check days remaining weekly across the portfolio. A certificate at 20 days left on a host with no working automation is already late.
- Renew at about two thirds of lifetime, not at a fixed number of days.
- Alert on renewal failure and on expiry, not on a calendar reminder that assumes the job ran. This is what monitoring tools for agencies do all day; the Little Warden vs stillindexed comparison prices two of them per URL and per site (October 2026).
- Know the fix path before you need it. Cloudflare, Vercel and Shopify each have their own certificate lifecycle: Cloudflare, Vercel, Shopify.
A quick expiry check from the terminal:
echo | openssl s_client -servername example.com -connect example.com:443 2>/dev/null \
| openssl x509 -noout -dates
Run it against each hostname and record the notAfter value. The free SSL and domain expiry checker does the same check in the browser and also checks domain expiry.
Where monitoring fits
An expired certificate fails the connection before any page is read, so reports built from crawl data can only show it after the fact. stillindexed checks the TLS certificate daily for each monitored site, alongside robots.txt, noindex directives, canonicals, status codes and sitemap health, and alerts by email and Telegram. That does not replace ACME automation; it catches the host where automation silently stopped. The trial covers 3 sites for 30 days, no card required.
Sources
- CA/Browser Forum ballot SC-081v3
- CA/Browser Forum TLS Baseline Requirements
- CA/Browser Forum F2F 63 minutes, 9 October 2024
- GitHub pull request 553
- Chrome Root Program, Moving Forward, Together
- Let’s Encrypt, from 90 to 45
- Let’s Encrypt, 6-day and IP certificate availability
- Google, HTTPS as a ranking signal
- Google, page experience
- Chromium net error list
- Chrome Help, fix connection errors
Read next
Questions
- When does the 200-day certificate limit start?
- The 200-day maximum applies to subscriber certificates issued on or after 15 March 2026. Certificates issued before that date could still be valid for up to 398 days. The maximum then falls to 100 days from 15 March 2027 and 47 days from 15 March 2029.
- Do existing certificates have to be reissued early?
- No. The limits apply at the moment of issuance, so a certificate issued before 15 March 2026 keeps its original expiry date. Because the old maximum was 398 days, the last certificates issued under it expire around mid-April 2027 at the latest.
- What is the domain validation reuse period?
- It is how long a certificate authority may reuse a completed domain or IP validation instead of checking again. The maximum was 398 days before 15 March 2026, becomes 200 days on that date, 100 days from 15 March 2027, and 10 days from 15 March 2029.
- Are Let's Encrypt certificates affected?
- Yes, as a publicly trusted CA, Let's Encrypt must follow the same maximums. It also plans to cut its default certificate lifetime from 90 days to 45 days by 2028, and its authorisation reuse period from 30 days to 7 hours. Its six-day certificates remain opt-in.
- What happens if a client site's certificate expires?
- Browsers show a certificate error page and HTTPS connections fail, so visitors cannot reach the site normally. Chromium reports that the certificate appears expired by its clock. Any monitoring or crawler fetching over HTTPS also fails until a valid certificate is served.