Skip to main content

47-day TLS certificates: what changes and how to prepare

· 3 min read
CertAutoPilot Team
CloudNativeWorks

Public TLS certificates are getting much shorter lives. The CA/Browser Forum ballot SC-081 lowers the maximum validity of a publicly trusted TLS certificate in four steps, ending at 47 days in March 2029. A process that renews a certificate by hand once a year has to do it roughly eight times a year by then, for every certificate.

The timeline​

Certificates issuedMaximum validityRenewals a year, per certificate
until 15 March 2026398 daysabout 1
from 15 March 2026200 daysabout 2
from 15 March 2027100 daysabout 4
from 15 March 202947 daysabout 8

The same ballot also shortens how long a CA may reuse a domain validation it already performed, so the proof that you control a domain has to be repeated more often too. In practice this means DNS or HTTP validation has to be automated along with the renewal itself.

Why it is harder than it looks​

Renewing is rarely the hard part. The work around it is:

  • Finding every certificate. Certificates that nobody tracks are the ones that expire in production. Load balancers, Windows servers, appliances and Kubernetes clusters each keep their own copy.
  • Deploying the new certificate everywhere it is used. One certificate can sit on an F5 virtual server, three IIS sites and a Kubernetes Secret. Renewing it at the CA fixes none of them.
  • Proving it worked. A renewal that reached the CA but not the server still expires on schedule.
  • Keeping humans out of the loop without losing control. Approvals, audit trails and rollback have to keep working when nobody clicks "renew" any more.

A checklist​

  1. Inventory first. Scan your networks, DNS zones and Certificate Transparency logs and list every certificate, where it is served and who owns it.
  2. Measure your exposure. Count certificates that are renewed manually, validated with manual DNS records, or deployed by hand. Those are the ones that will break.
  3. Automate validation. Use DNS-01 with an API-driven DNS provider, or HTTP-01 where a route to the challenge path exists. Manual TXT records do not scale to eight renewals a year.
  4. Automate deployment. Every place a certificate is installed needs a deployment step that runs after each renewal, without someone logging in to the device.
  5. Verify after deploying. Check the fingerprint the endpoint actually serves, not the one you uploaded.
  6. Keep a way back. Being able to roll a target back to the previous certificate version turns a bad deployment into a minor event.
  7. Watch the calendar. Renewal load concentrates on certain days; know your busiest day before the CA does.

How CertAutoPilot helps​

CertAutoPilot's 47-Day Readiness dashboard scores a project on exactly these points: how much is automated, how much of it is deployed automatically, and how much still relies on manual DNS. It projects renewals per year at 47 days and shows the busiest renewal day ahead, so you can see the gap before the 2027 and 2029 deadlines rather than after.

Issuance and renewal run through ACME (Let's Encrypt, Google Trust Services, Sectigo and private ACME CAs) or Microsoft AD CS, and each renewal is deployed to its targets automatically, then checked against what the endpoint serves.