Updated November 2026

How to prepare client sites for 200-day and 47-day SSL certificates

A working checklist for the 2026 to 2029 certificate cuts, written for an agency that owns 30 to 150 client domains across four different hosting stacks. No theory, and no assumption that every client is on the same platform.

The maximum lifetime of a publicly trusted TLS certificate drops from 398 days to 200 days on 15 March 2026, to 100 days on 15 March 2027, and to 47 days on 15 March 2029. Those dates come from CA/Browser Forum ballot SC-081v3, which passed in April 2025. If you have read the schedule guide, you already know the numbers. This article is the part that takes a weekend: making a mixed portfolio actually ready.

Why a mixed portfolio is the hard case

A company with one website renews one certificate with one automation and never thinks about it. An agency portfolio is the opposite: a Webflow site on Webflow's certificate, a Shopify store on Shopify's, a Squarespace page nobody has opened since 2021, two WordPress installs on a shared host, one Node app on a VPS, and a marketing landing page on a domain that a former contractor pointed at a now unused CDN.

Three of those stacks renew themselves. Two renew through a hosting panel with an email reminder that goes to an address nobody monitors. One has a certificate that will silently expire on a Saturday. The shortening lifetime does not create that risk; it multiplies how often the risk gets a chance to fire.

The checklist

1. Inventory hostnames, not websites

Pull the full list from your DNS zones: apex, www, api, shop, mail, booking, staging, portal. Every hostname that terminates TLS has its own certificate and its own renewal path. Most agency surprises live on the subdomain nobody put in the care-plan spreadsheet.

2. Record who owns each renewal

For each hostname, note the platform, the ACME client if any, the account email, and who can change the DNS challenge record. Ownership that lives in one person's memory is the failure mode the deadline exposes.

3. Confirm automation, and confirm it renews early

A renewal that runs at 30 days remaining is fine at 398 days and uncomfortably tight at 47. Set renewals to fire between 20 and 30 days remaining, and make sure a failure notifies a human within a day rather than a week.

4. Re-tune the alert thresholds

The old convention was a 30-day warning. On a 47-day certificate that warning lands when two thirds of the lifetime is gone, which leaves almost no room to act. Move to 14, 7 and 2 days, and check often enough that the 14-day alert is not the first sign of trouble.

5. Fix hardcoded fingerprints

Mobile app pinning, partner integrations and internal scripts sometimes pin a leaf certificate. At 398 days nobody notices for a year. At 47 days every renewal breaks them. Pin the intermediate or the public key instead, or remove the pin entirely.

6. Cross-check the email records in the same pass

Clients notice a broken certificate immediately. They do not notice an SPF record that has crept past the RFC 7208 lookup budget, even while their invoices are being rejected. If you are touching DNS anyway, count the lookups and read the DMARC policy while you are there.

7. Write the client-facing sentence once

"Your certificate renewed on 14 May, valid for 47 days, no action needed." That sentence is worth more than a dashboard the client will never log into, and it costs you nothing if the check runs on a schedule.

Per-platform notes

StackWho renewsWhat to watch
WebflowWebflow, on published domainsCustom domains that are not connected yet, and 301 domains
ShopifyShopify, on the primary domainSecondary domains without a live connection
SquarespaceSquarespace, when the domain is attachedDomains pointed by A record instead of CNAME
WordPress, managed hostHost automation, usually Let's EncryptRate limits, and www versus apex coverage
WordPress, shared hostControl panel cron or manualMissed renewals, and certs attached to the wrong vhost
VPS or custom Node appYouEverything: ACME client, DNS challenge, reload hook

What to do before each date

  • Before 15 March 2026: finish the inventory, fix hardcoded pins, move alerts to 14 and 7 days.
  • During 2026: verify every renewal path actually renews, especially the two hosts you inherited.
  • Before 15 March 2027: confirm your monitoring cadence is hours, not days, and that the report includes the certificate line.
  • Before 15 March 2029: expect roughly eight renewals per domain per year. Anything renewal-adjacent that depends on a human reminder has to be automated or monitored.

If you would rather not maintain this by hand across 50 domains, that is the product: checks every six hours, thresholds at 14, 7 and 2 days, and one branded report to the client each month. $39/mo for 50 domains.