TLS CertificatesSSLCertificate ManagementACMECybersecurityFirewallSmall Business

47 Day TLS Certificates: What Changes, When, and What to Check Before March 2027

Regroove IT Consulting10 min read2,100 words
Key Takeaways
  • Public TLS certificates are getting shorter lifetimes in three steps. 200 days since March 15, 2026, 100 days from March 15, 2027, and 47 days from March 15, 2029.
  • Renewing once a year with a calendar reminder stops working. At 47 days a certificate has to be replaced at least eight times a year, on every system that uses it.
  • Cloud services that manage their own certificates need nothing from you. The risk sits in firewalls, VPNs, remote access servers, older web servers and anything else where a certificate was installed by hand.
  • The fix is automation. ACME, the renewal protocol behind Let's Encrypt, is now supported by most certificate providers and many firewalls and servers.
  • Aim to have an inventory and a plan before March 15, 2027. That is when the limit drops to 100 days and manual renewal starts to hurt.

For most businesses, the certificate that puts the padlock on a website or a VPN login page is something you think about once a year. An email arrives, someone buys a renewal, someone else installs it, and everyone forgets about it for another twelve months. Sometimes the email goes to a person who left two years ago, and the first sign of trouble is a phone call from a customer who cannot reach your site.

That yearly routine is ending. The industry body that sets the rules for these certificates has voted to cut their maximum lifetime from 398 days to 47 days, in steps between 2026 and 2029. The first step has already happened. This guide explains what is changing, what breaks if you do nothing, and where to look in your own environment.

What is changing

Every publicly trusted TLS certificate (people often still call them SSL certificates) is issued under rules set by the CA/Browser Forum, a group made up of the certificate authorities that sell certificates and the companies that make browsers, such as Apple, Google, Microsoft and Mozilla. In April 2025 the forum approved Ballot SC-081v3, proposed by Apple, with no votes against. It replaces the old 398 day maximum with a schedule:

The shrinking certificate
Maximum lifetime of a publicly trusted TLS certificate, and the fewest renewals that means in a year.
Maximum TLS certificate lifetime from 2026 to 2029Until March 15, 2026 the maximum was 398 days, one renewal a year. From March 15, 2026 it is 200 days, at least two renewals a year. From March 15, 2027 it is 100 days, at least four. From March 15, 2029 it is 47 days, at least eight.Until March 15, 2026the old limit398 days1 renewal a yearMarch 15, 2026in effect now200 days2+ renewals a yearMarch 15, 2027next step100 days4+ renewals a yearMarch 15, 2029final step47 days8+ renewals a year

A second change matters just as much. Before issuing a certificate, the authority has to check that you control the domain name, usually by asking you to add a DNS record, place a file on your website or answer an email. Until now that check could be reused for more than a year. The reuse window shrinks on the same dates:

FromMaximum certificate lifetimeDomain check can be reused for
Before March 15, 2026398 days398 days
March 15, 2026 (now)200 days200 days
March 15, 2027100 days100 days
March 15, 202947 days10 days

By 2029, almost every renewal will need a fresh proof that you own the domain. For organization validated and extended validation certificates, the company details checked by the authority can now be reused for at most 398 days, down from 825.

Why 47? It is one 31 day month plus about half a month of margin, so an automated system can renew monthly and still have time to retry if something goes wrong.

What breaks if you do nothing

A certificate does not fade slowly. It works until the expiry date, then it fails. When it does:

  • Websites show a full page browser warning, and most visitors leave.
  • VPN clients refuse to connect, or show a warning that staff learn to click through, which is worse.
  • Email, remote desktop and wireless networks stop connecting, often with an error message that does not mention certificates at all.
  • Apps that talk to each other in the background fail quietly, and someone spends a morning finding out why.

With a yearly certificate, a business could get away with a calendar reminder and one person who knew the steps. At 100 days that is four or more renewals a year per certificate. At 47 days it is at least eight, and closer to twelve if you renew with a sensible margin. Multiply that by every device that holds a copy, and manual renewal stops being a chore and becomes a reliable way to cause outages.

A year of renewals
Each dot is a certificate replacement on every system that uses it, at the longest allowed lifetime. Real schedules renew earlier, so expect more.
Certificate replacements in one year at each maximum lifetimeAcross twelve months, a 398 day certificate is replaced once, a 200 day certificate twice, a 100 day certificate four times and a 47 day certificate eight times.JFMAMJJASOND398 day certificatereplaced once200 day certificatereplaced 2 times100 day certificatereplaced 4 times47 day certificatereplaced 8 times

Your checklist

You do not need to solve everything this year, but you should know where you stand before March 15, 2027.

  1. Find every public certificate you own. Every publicly trusted certificate is recorded in public Certificate Transparency logs. Search your domain on crt.sh and you will see every certificate issued for it, including ones nobody remembers ordering.
  2. Write down where each one is installed and who renews it. One certificate can live on several devices. The list below shows where they usually hide.
  3. Sort them into three groups. Managed by a cloud service, which needs nothing. Can be automated with ACME, which you should set up now. Cannot be automated, which needs replacing, moving behind a proxy, or moving to an internal certificate.
  4. Check that your certificate provider supports ACME. Let's Encrypt is built on it, and most commercial certificate authorities now offer it on their paid certificates too.
  5. Stop copying one wildcard certificate to many devices. It turns every renewal into a hunt.
  6. Monitor expiry separately from renewal. Automation fails quietly when a password changes or a firewall rule blocks it. An independent alert two weeks before expiry catches that in time.

Where certificates usually hide

These are the places we most often find certificates that were installed by hand and are renewed by memory.

WhereWhy it gets missedUsual fix
Firewall SSL VPN and admin portalInstalled once when the firewall went in, then forgotten until staff cannot connect from home.Many current firewalls, including recent FortiGate and pfSense releases, can request and renew their own certificate through ACME. Older units need a script or a replacement.
On premises ExchangeThe certificate is bound to several services at once, so renewing it is a careful manual job.Automate it with an ACME client that knows Exchange, or finish the move to Exchange Online and retire the server.
Remote Desktop Gateway and Web AccessUsually set up by whoever built the server years ago, with nobody owning the renewal since.An ACME client on the server that renews the certificate and updates the Gateway binding.
Wireless network (RADIUS and NPS)Devices check this certificate every time they join the network, so an expiry knocks everyone offline at once.If it came from a public authority, move it to an internal certificate authority. Your devices can trust it through Intune or Group Policy.
Printers, NAS, switches and hypervisor consolesManagement pages nobody looks at until something is wrong.These rarely need a public certificate. Use an internal one, or put them behind a reverse proxy that renews for them.
Older IIS websites and line of business appsThe certificate was bought by email, imported by hand and bound in IIS Manager.Free ACME clients such as Certify The Web renew the certificate and update the IIS binding on a schedule.
Load balancers and reverse proxiesOften the one place that holds certificates for many services behind it.Most have ACME built in or available as an add on. Turn it on and let the proxy renew for everything behind it.
One wildcard certificate copied to many devicesThe worst case. Every renewal means touching every device, and missing one breaks it.Give each service its own certificate that renews itself, or put the services behind one proxy that holds the wildcard.

What you can leave alone

Services that issue and renew their own certificates already work this way, and many renew far more often than 47 days. That includes Microsoft 365, Azure services that use managed certificates, Cloudflare, and most website hosts that include a free certificate. Let's Encrypt, which already issues 90 day certificates, is moving its default to 64 days in February 2027 and 45 days in 2028. Systems that renew automatically today will keep up.

Certificates from your own internal certificate authority, such as Active Directory Certificate Services, are not covered by these rules at all. For services that only staff use on your own network, an internal certificate is often the simplest answer.

How the automation works

ACME (Automatic Certificate Management Environment) is a standard way for a server to ask a certificate authority for a certificate, prove it controls the domain, install the result and repeat the whole process before expiry, with nobody involved. It is how Let's Encrypt has handed out hundreds of millions of certificates. A small program, the ACME client, runs on the server or device and does the work on a schedule.

There are three common ways to get there, and most businesses end up using a mix:

  • Built in ACME on the firewall, proxy or platform, when it supports it. Turn it on and point it at your provider.
  • An ACME client on the server for Windows and Linux systems that do not have it built in. It renews the certificate and updates the service that uses it.
  • A certificate management tool for larger estates, which keeps the inventory, renews across many systems and alerts when something fails.

For devices that cannot run ACME and cannot be replaced yet, put them behind a reverse proxy that handles the public certificate for them, or move them to an internal certificate if only staff need to reach them.

Why the industry is doing this

A certificate is a promise that the server you are talking to belongs to the name in the address bar. If its private key is stolen, or a certificate is issued by mistake, the promise stays valid until the certificate expires, because the ways browsers check for revoked certificates have never been reliable. Shorter lifetimes shrink that window from over a year to a few weeks.

There is a longer term reason too. When the industry has to replace the encryption inside certificates, which is expected as quantum resistant cryptography arrives, organizations that already renew automatically every month will switch without noticing. Those that renew by hand once a year will not.

Not sure where your certificates are?
We find every public certificate you own, sort out what can renew itself, and automate the rest on your firewalls, servers and network gear before the 100 day step in March 2027.
Talk to us about certificates

This work usually sits across a few of our services: firewall management for VPN and portal certificates, managed infrastructure for servers and internal certificate authorities, and managed security for monitoring and expiry alerts.

Frequently asked questions

What is the 47 day certificate rule?

It is a decision by the CA/Browser Forum, the group of certificate authorities and browser makers that sets the rules for website certificates. Public TLS certificates, the ones that put the padlock in the browser, are getting shorter maximum lifetimes in steps: 200 days from March 15, 2026, 100 days from March 15, 2027, and 47 days from March 15, 2029. Before this change the limit was 398 days.

Is the change already in effect?

Yes. The first step took effect on March 15, 2026. Any public certificate issued since then lasts at most 200 days, so a certificate you bought as a one year product in early 2026 needs replacing sooner than the old habit of renewing once a year would suggest.

Does this affect my website?

If your website host or platform provides the certificate for you, as most modern hosts, Microsoft 365, Azure and Cloudflare do, it already renews automatically and you do not need to do anything. The work is in places where someone installed a certificate by hand: firewalls, VPNs, remote access servers, older web servers and network devices.

Do I need to buy more certificates?

Usually not. Many certificate providers already sell certificates as yearly or multi year subscriptions that include as many reissues as you need during the term. What changes is how often the certificate has to be replaced on your systems, not necessarily how often you pay. Check the terms with your provider before your next renewal.

Does this apply to internal certificates?

No. The rule covers publicly trusted certificates only. Certificates issued by your own internal certificate authority, such as Active Directory Certificate Services, keep whatever lifetime you set. That is why moving internal only services to an internal certificate authority is one of the simplest fixes.

What happens when a certificate expires?

Browsers show a full page warning and most people stop there. Email clients, VPN clients, wireless networks and apps that call each other in the background usually refuse to connect at all. The certificate does not degrade gracefully. It works until the expiry date and then it fails.

Does it affect code signing or email signing certificates?

No. This change is for TLS server certificates, the kind that secure websites and other services you connect to. Code signing and email (S/MIME) certificates are governed by separate rules.

Sources

Helio PereiraAuthor: Helio Pereira

Regroove IT Consulting

Microsoft Solutions Partner specializing in Managed IT Services and Modern Work, covering Microsoft 365, Teams, SharePoint, Power Platform, and Azure. Helping organizations everywhere get lasting value from their Microsoft investment since 1993.

About Regroove →

Want a hand with this?

We do this work every week. Have a look at how we help, or just tell us what you are trying to solve.

Comments

Loading comments…

Leave a comment

Comments are reviewed before they appear. Your email is never published, and we only use it to let you know when your comment goes live.

Links are not accepted, which keeps the spam out.

0/2000