The SSL certificate lifetime for millions of websites is about to get shorter. On 7 October 2026, Let’s Encrypt announced that from 10 February 2027, every certificate it issues or renews will be valid for 64 days instead of 90 by default. Its test (staging) system switches to 64-day certificates on 14 October 2026.

If your site uses a free SSL certificate from your host, there’s a good chance it comes from Let’s Encrypt. Most sites with automatic renewal won’t need to do anything. But sites with manual renewals or custom renewal scripts could see an expired certificate warning if nobody checks. This guide explains what changes, who is affected and what to check, in plain language.
What exactly is changing
| Date | Change | Who it affects |
|---|---|---|
| 14 Oct 2026 | Staging (test) environment starts issuing 64-day certificates | Developers and admins who test renewals |
| 10 Feb 2027 | Default certificates drop from 90 to 64 days; authorization reuse cut from 30 to 10 days | Everyone using the default Let’s Encrypt profile |
| 11 May 2027 | Let’s Encrypt expects the last 90-day certificate to expire | — |
| 16 Feb 2028 | Default drops further to 45 days; authorization reuse cut to 7 hours | Everyone using the default profile |
Let’s Encrypt says it will not revoke any existing certificates because of this. Your current certificate keeps working until its normal expiry date; the shorter lifetime starts at your next renewal on or after 10 February 2027.
In simple terms, the SSL certificate lifetime change means a certificate that used to be renewed about every 60 days will now be renewed roughly every six weeks, and from 2028 about once a month.
Why SSL certificate lifetime is getting shorter
Shorter certificates limit the damage if a private key is stolen or a certificate is issued by mistake, because a bad certificate stops working sooner. Let’s Encrypt gives this reason in its announcement. The whole industry is moving the same way: the CA/Browser Forum, which sets rules for public certificates, has approved a schedule that cuts the maximum lifetime for all public TLS certificates to 200 days from March 2026, 100 days from March 2027 and 47 days from March 2029. Let’s Encrypt is simply moving earlier than the deadline.
Am I affected? A quick check
- Shared hosting with free SSL (cPanel AutoSSL, Hostinger, Bluehost and similar): the host renews for you. You are very likely fine, but it is worth confirming that your host’s free SSL renews automatically.
- Cloudflare proxy (orange cloud): visitors see Cloudflare’s edge certificate, which Cloudflare manages. Your origin server certificate still needs to stay valid if you use Full (strict) mode.
- Your own VPS with Certbot or another ACME client: usually fine if renewal runs automatically, but check the schedule and any custom scripts (see below).
- Manual renewals, copied certificates or old control panels: this is the risky group. Anyone renewing by hand will have to do it more often, and a missed renewal means browsers show a security warning.
Not sure who issued your certificate? In Chrome, click the icon to the left of the address bar, choose the connection details, then open the certificate. The “Issued by” field shows Let’s Encrypt if that is your certificate authority, along with the expiry date.
What to do now: a practical checklist
1. Make sure renewal is automatic
If you are on a VPS with Certbot, these two commands show whether renewal is scheduled and whether it works:
systemctl list-timers | grep certbot
sudo certbot renew --dry-runThe first shows the automatic renewal timer (on systems that use systemd). The second runs a test renewal without changing your real certificate. If the dry run fails, fix it now, not in February.
2. Look for hard-coded renewal days
Let’s Encrypt specifically warns about scripts that renew a fixed number of days after issue or before expiry. It suggests searching cron jobs, scripts and runbooks for numbers like 83, 80 or 60. Example: a script that renews “60 days after issue” worked with 90-day certificates, but with a 64-day certificate it leaves only four days of safety margin, and none at all once certificates drop to 45 days.
The recommended rule is to renew at about two-thirds of the certificate’s lifetime. For a 64-day certificate, that is around day 43 (two-thirds of 64 is about 42.7).
3. Check whether your client supports ARI
ACME Renewal Information (ARI) lets Let’s Encrypt tell your client when to renew. Let’s Encrypt says that if renewal is automated and the client supports ARI, “you should be all set”. Check your client’s documentation to see whether it supports ARI. We are not listing version numbers here because support differs by client and version.
4. Test against staging
If you run your own ACME setup, point a test domain at Let’s Encrypt’s staging environment after 14 October 2026. You’ll get 64-day test certificates and can confirm your renewal, reload and deployment steps work before the change goes live.
5. Add an expiry alert
Set up a simple expiry check so you hear about a failed renewal before visitors do. Many uptime monitoring services include SSL expiry alerts. From a terminal, this command shows a site’s certificate dates:
echo | openssl s_client -connect example.com:443 -servername example.com 2>/dev/null | openssl x509 -noout -datesReplace example.com with your domain. The notAfter line is the expiry date.
6. Automate reloads and copies
Renewing the certificate isn’t enough if your web server keeps using the old file in memory, or if the certificate is copied by hand to a mail server, load balancer or CDN. Make sure the server reloads after renewal and that any copies update automatically.
When Let’s Encrypt checks that you control a domain, it remembers that check for a while so it doesn’t have to repeat it at every renewal. That period drops from 30 days to 10 days in February 2027, and to seven hours in 2028. Let’s Encrypt says you only need to act if you specifically designed your setup to rely on that reuse. For most site owners, nothing changes.
Practical example: one certificate, three renewal rules
Say a certificate is issued on 15 February 2027, after the change. It is valid for 64 days, so it expires on 20 April 2027. Here is what different renewal rules do with it:
- Renew at about two-thirds of the lifetime (recommended): renewal happens around day 43, which is 30 March 2027. You have three weeks of safety margin if a renewal fails.
- A script hard-coded to renew 60 days after issue: renewal happens on 16 April 2027, only four days before expiry. One failed run or one weekend can be enough to cause a browser warning.
- Manual renewal when you remember: no schedule at all. This is the setup most likely to fail with shorter certificates.
Common mistakes to avoid
- Assuming the host handles it without checking. Most do, but a two-minute check of your hosting panel’s SSL page, or a quick message to support, removes the guesswork.
- Relying on expiry emails. Let’s Encrypt ended its expiry reminder emails on 4 June 2025, so don’t wait for an email warning from it. Use your own monitoring.
- Renewing too often by hand. Repeated manual requests can hit rate limits. Let’s Encrypt says rate limits are not affected by this change, but scripted retries that loop can still cause trouble.
- Forgetting non-web services. Mail servers, FTP and admin panels often use the same certificate and are easy to miss.
Troubleshooting: “Your connection is not private” after renewal
- Certificate renewed, but site still shows the old one: reload or restart the web server, and clear the CDN cache if you use one.
- Renewal fails with a challenge error: check that the domain’s DNS still points to your server and that port 80 is open for HTTP validation, or that your DNS API credentials still work for DNS validation.
- Only some visitors see an error: the certificate may be fine, but one server in a group or a CDN edge has an old copy.
Not sure a renewal happened? Run the openssl command from the checklist above and compare the notAfter date before and after your renewal time. If the date did not move forward, the renewal did not run or the server is still using the old file.
If a certificate problem stops your WordPress site loading entirely, our guide to fixing error establishing a database connection covers other common outages. Choosing hosting? See shared vs VPS hosting and our list of free static website hosting options; most include automatic SSL.
Source: Let’s Encrypt: 64-Day Certificate Lifetimes Coming Feb 2027 and Decreasing Certificate Lifetimes to 45 Days.
More sources: Let’s Encrypt: Expiration Notification Service Has Ended and the CA/Browser Forum ballot SC-081v3.
Frequently asked questions
When do Let’s Encrypt certificates change to 64 days?
From 10 February 2027 for the default profile. Any certificate issued or renewed on or after that date is valid for 64 days. Staging switches on 14 October 2026.
Will my current SSL certificate stop working?
No. Let’s Encrypt is not revoking existing certificates. The shorter lifetime applies at your next renewal after 10 February 2027.
Is Let’s Encrypt still free?
Yes. The change affects how long certificates last, not the price.
Can my Let’s Encrypt certificate renew automatically?
Yes. Most hosting panels and ACME clients such as Certbot renew automatically. Check that renewal is scheduled and that it doesn’t use a fixed day count tuned for 90-day certificates.
How long will SSL certificates be valid in the future?
Let’s Encrypt plans 45 days from February 2028. Industry rules cut the maximum for all public certificates to 47 days from March 2029.
What is the SSL certificate lifetime for Let’s Encrypt right now?
90 days for default certificates issued before 10 February 2027. Certificates issued or renewed on or after that date last 64 days, and 45 days from 16 February 2028.

