45-Day TLS Certificates Are Coming: What Website Owners Need to Automate

Content delivery and caching illustration for improving WooCommerce holiday store performance

Public TLS certificates are getting shorter. The CA/Browser Forum has adopted a schedule that reduces maximum certificate validity over several years, ending at 47 days in March 2029. Let’s Encrypt is moving its own default certificates to 45 days by February 2028.

For a well-managed server, shorter certificates should be boring. For a server that still depends on someone remembering to renew a certificate by hand, the change is a warning that the workflow needs automation.

Why Certificate Lifetimes Are Shrinking

Shorter certificates reduce the amount of time a compromised or mis-issued certificate can remain valid. They also force the web ecosystem toward automated issuance and renewal.

That trade makes sense because certificate automation is mature now. ACME clients can request, renew, and install certificates without a person opening a calendar reminder.

The Industry Timeline

The CA/Browser Forum schedule eventually limits publicly trusted TLS certificates to 47 days beginning March 15, 2029. The reductions started in 2026 and step down over time.

Let’s Encrypt has its own implementation timeline. Its default classic profile remains at 90 days for now, then moves to 64 days in February 2027 and 45 days in February 2028. An opt-in 45-day tlsserver profile became available in 2026 for early testing.

Manual Renewal Is the Real Problem

A 45-day certificate is not difficult when renewal is automatic. It is very difficult when a human must remember to generate a CSR, validate the domain, download files, install the chain, reload services, and verify the result every few weeks.

If your HTTPS process still looks like that, fix the process before the shorter lifetime becomes your emergency.

Use ACME and Monitor the Result

Automate issuance with an ACME-capable client or hosting platform. Then monitor certificate expiry independently. Automation without monitoring can fail quietly because of DNS problems, blocked validation paths, permissions, or changed server configuration.

A small UPS battery backup will not solve certificate renewal, but reliable infrastructure matters when automated jobs and control panels need to remain available. More important is an external expiry monitor that alerts before users see a browser warning.

Watch How ACME Renewal Works

This practical ACME and Let’s Encrypt walkthrough shows the basic idea behind automated certificate issuance and renewal.

https://www.youtube.com/watch?v=jrRngUD1xZQ

Domain Validation Will Get Shorter Too

The certificate lifetime is not the only number changing. Reuse periods for domain validation are also shrinking. That means certificate authorities will need fresh proof of domain control more often.

The operational message is the same: DNS and HTTP validation need to be automated, predictable, and documented.

Test Renewal Before Expiry

Do not wait for a live certificate to approach expiration before discovering that the renewal hook cannot reload the web server. Use a staging CA or dry-run function where your ACME client supports it.

Our DNSSEC and domain-locking guide covers another part of the trust chain. Certificates, DNS, and domain control are separate systems, but they all protect the same public identity.

Shorter Certificates Are Mostly an Operations Test

The security benefit is real, but for site owners the practical effect is a test of automation quality. Sites with good ACME renewal will barely notice. Sites with spreadsheets and calendar reminders will notice very quickly.

For broader technical explanations outside hosting, TUARS has plain-language guides on digital tools and security habits.

What to Change Now

Inventory how certificates are issued. Confirm automatic renewal works. Monitor expiry from outside the server. Keep DNS credentials scoped and protected. Document who owns the process.

Do that now and 45-day certificates become a routine background task instead of a recurring outage risk.

References

  1. 1. CA/Browser Forum Ballot SC081v3
  2. 2. Let’s Encrypt: Decreasing Certificate Lifetimes to 45 Days
  3. 3. Let’s Encrypt: Shorter Certificate Lifetimes and Rate Limits