Home / Acmefyer / 47-day certificates

AcmefyerAgent-based Certificate Manager

SSL certificates will soon be valid for only 47 days.

The lifetime of public SSL/TLS certificates drops in three stages: 200 days since March 2026, 100 days from March 2027 and 47 days from March 2029. If you replace certificates by hand today, you will then do so roughly every month, on every server. Acmefyer renews them automatically and an agent installs them wherever they are needed.

01DatesWhat was decided and from when it applies

The dates: 200, 100 and 47 days of validity.

On 11 April 2025 the CA/Browser Forum set the maximum lifetime of public TLS certificates with ballot SC-081v3. Apple, Google, Microsoft and Mozilla voted in favour. The limit applies to every certificate issued from the respective date on. Certificates issued before keep running until they expire.

At the same time the period in which a certificate authority may reuse a domain validation drops to 10 days by 2029. Practically every renewal then checks again that the domain is yours. So this step has to run by itself as well.

Source: CA/Browser Forum, Ballot SC-081v3.

until 14 Mar 2026
At most 398 days. One replacement a year.
since 15 Mar 2026
At most 200 days. Two replacements a year.
from 15 Mar 2027
At most 100 days. Roughly every three months.
from 15 Mar 2029
At most 47 days. Roughly every month. A domain validation can be reused for only 10 days.
Affected
All publicly trusted TLS certificates, purchased ones as well as free ones from Let’s Encrypt. For every web server, mail system, firewall and VPN portal with a public certificate.
Not affected
Certificates from an internal CA of your own. You set their lifetime yourself.
02With AcmefyerWhat runs automatically

Renew and deploy certificates automatically.

The Acmefyer server obtains the certificates via ACME from Let’s Encrypt, ZeroSSL or Google Trust Services, handles the domain validation itself at every renewal and renews in time before expiry. How short the lifetime is makes no difference.

The second part is the more laborious one: the new certificate has to reach every system that serves it. For this the Acmefyer agent runs on the target systems. It picks up the certificate, installs it locally and reports the result. The target systems need no open port and no internet access.

Renewal
About 30 days before expiry, for very short lifetimes after about two thirds of the lifetime. If an attempt fails, more follow at growing intervals.
Validation
HTTP-01, DNS-01 for around 190 DNS providers and TLS-ALPN-01, by itself at every renewal.
Rollout
Via agent into IIS, Exchange, FortiGate, NGINX and Apache, Tomcat and many more targets.
Inventory
Agents and a network scan find the certificates that are still replaced by hand.
Purchased certificates
Can be imported and deployed through the same agents. Acmefyer warns before they expire, but the provider still has to renew them.
Notifications
Issued, failed or expiring soon: by email, Teams, Telegram, PRTG or webhook.
03SetupSwitch over before the next date
  1. 01

    Take stock

    Agents and the network scan show where each certificate sits and when it expires.

  2. 02

    Add domains

    One domain per certificate, with Let’s Encrypt and validation via HTTP-01 or DNS-01.

  3. 03

    Assign targets

    The agent suggests the matching deployment for detected applications. One click accepts it.

  4. 04

    Done

    Whether 200, 100 or 47 days: from now on Acmefyer renews and deploys by itself.

04FAQFrequently asked questions about SSL certificate lifetimes

From when are SSL certificates valid for only 47 days?

From 15 March 2029. Public TLS certificates issued from that day on may be valid for at most 47 days. Two stages come before: at most 200 days since 15 March 2026 and at most 100 days from 15 March 2027.

Are my existing certificates affected?

Not right away. The limit depends on the day of issuance. A certificate from before the date stays valid until it expires. Only the next one you have issued after that gets the shorter lifetime.

Does the 47-day rule also apply to certificates from an internal CA?

No. It binds the public certificate authorities that browsers and operating systems trust out of the box. With a CA of your own you set the lifetime yourself. Acmefyer brings a private CA for this and renews its certificates by itself as well.

Why are the lifetimes being shortened?

Three reasons are given above all: a stolen key or a wrongly issued certificate is usable only briefly, the information in the certificate is more current, and revoking certificates does not work reliably in practice. In addition, new algorithms can be introduced faster when everything is replaced automatically anyway.

Does this make certificates more expensive?

Not with ACME. Let’s Encrypt, ZeroSSL and Google Trust Services issue for free, no matter how often you renew. For purchased certificates it depends on the provider. More: renew free SSL certificates automatically.

Can I keep replacing certificates by hand?

Technically yes. At 47 days, however, this means ordering, validating, installing on every system and checking roughly every month. A forgotten replacement means a certificate warning in the browser or a service that stops working. The shortening is explicitly designed for the replacement to run automatically.