All articles

Security · · 6 min read

47-day TLS certificates: what changes for teams hosting many sites

By Rushit Chandegara, Founder & CTO, InfraCloudEdge

In April 2025 the CA/Browser Forum approved ballot SC-081, which shortens how long a public TLS certificate can be valid. The first step has already happened: since 15 March 2026, new certificates can be valid for at most 200 days. It drops to 100 days in March 2027 and to 47 days in March 2029.

If you run one website, a 47-day certificate is a non-event once renewals are automated. If you host dozens or hundreds of customer sites, it changes how you have to operate.

The timeline

  • From 15 March 2026: maximum validity 200 days.
  • From 15 March 2027: maximum validity 100 days.
  • From 15 March 2029: maximum validity 47 days, and domain validation can only be reused for 10 days.

Why manual renewals stop working

With a one-year certificate, a calendar reminder and a support ticket were enough. At 47 days, every certificate needs renewing roughly every month. A platform hosting 200 sites would be handling several renewals every working day, and a single missed one takes a customer site offline with a browser warning.

Paid certificates bought per site get the same treatment: shorter lifetimes mean more frequent reissues, not cheaper ones. For most hosted sites the practical answer is ACME automation with a free certificate authority such as Let's Encrypt.

What to automate

  • Issuance and renewal with an ACME client (certbot, acme.sh, or your load balancer's managed certificates) on a schedule that renews well before expiry.
  • Domain validation that does not depend on a person: HTTP-01 on the web server, or DNS-01 through your DNS provider's API for wildcards.
  • Reloading the web server after renewal, without dropping connections.
  • Monitoring of what is actually served. Let's Encrypt stopped sending expiry reminder emails in 2025, so your own checks are now the only warning you get.

Customers who bring their own certificate

Some customers will insist on a certificate from their own CA. Keep a clear split: sites you manage get automated certificates; customer-supplied certificates are stored separately, monitored for expiry, and the customer is told well in advance. Mixing the two in one manual process is where outages come from.

A checklist for platforms hosting many sites

  • Inventory every hostname you serve and where its certificate comes from.
  • Group hostnames sensibly: a wildcard for your own subdomains, and one certificate per customer site or small group.
  • Plan the cut-over so customers do not need to change DNS, for example by keeping the same public IP address.
  • Have a one-command rollback to the previous setup.
  • Alert at 14 days before expiry, not on the day.

We recently designed this for a platform hosting 218 websites, where fewer than a third had working HTTPS. The full write-up is in our case studies.

More articles