Security 8 min read ·
SSL Certificate Validity Is Now 200 Days: What Changes by 2029
SSL certificate validity is 200 days since March 2026, then 100 days in 2027 and 47 in 2029. What it means for 1-year SSL and how to check auto-renewal.
As of 15 November 2026, a new public SSL/TLS certificate can be valid for at most 200 days, down from 398 days, under a rule that took effect on 15 March 2026. The limit drops to 100 days on 15 March 2027 and 47 days on 15 March 2029, under CA/Browser Forum ballot SC-081v3. You can still buy a "1-year SSL", but it now means installing at least two certificates a year, and at least four from March 2027, so automatic renewal over ACME is the only practical way to keep a site on HTTPS.
The short version:
- The limit applies to the date a certificate is issued. A certificate you already have stays valid until its own expiry date.
- Claims that certificates drop to 47 days in 2027 are wrong: 2027 brings 100 days, and 47 days arrives in 2029.
- Let's Encrypt is moving faster than the rules require: 64-day certificates by default from 10 February 2027 and 45-day certificates from 16 February 2028.
- If your renewal is a cron job that runs every 60 days, fix it before February 2027.
SSL certificate validity in 2026: the official timeline
Browsers and certificate authorities (CAs) agree on the rules for public certificates through the CA/Browser Forum. Its ballot SC-081v3 closed on 11 April 2025 with 25 CAs in favour, none against and 5 abstaining, and all four browser makers voting yes: Apple, Google, Microsoft and Mozilla. The dates below are from the Baseline Requirements that ballot changed.
| Certificates issued from | Maximum validity | Domain validation can be reused for | New certificates a year, at least |
|---|---|---|---|
| Before 15 March 2026 | 398 days | 398 days | 1 |
| 15 March 2026 (now) | 200 days | 200 days | 2 |
| 15 March 2027 | 100 days | 100 days | 4 |
| 15 March 2029 | 47 days | 10 days | 8 |
"Domain validation reuse" is how long a CA may rely on an earlier check that you control the domain before it must check again. From March 2029 it is 10 days, so in practice every new certificate needs a fresh check: a DNS record, a file on your server or an email link. For OV and EV certificates, which carry your company's name, the company details can be reused for up to 398 days from March 2026, so that paperwork stays roughly yearly.
Will SSL certificates be valid for only 47 days in 2027?
No. Some articles say "47 days in 2027", but the rule is 100 days for certificates issued from 15 March 2027, and 47 days only from 15 March 2029. What does happen sooner is at Let's Encrypt, whose own certificates get shorter faster than the rules require: 64 days from February 2027 and 45 days from February 2028. Those are Let's Encrypt's choices for its free certificates, not the industry limit.
Our older guide, what an SSL certificate is, covers DV, OV and EV certificates and the "Not secure" warning if you need the basics first.
What a "1-year SSL" from a reseller means now
Registrars and resellers still sell SSL by the year, often with multi-year plans on top. Under the new rules, no CA can issue one certificate for that long. What you buy is a subscription: the CA issues a certificate for the maximum allowed period, and you reissue to cover the rest of the term. Sectigo's reseller store puts it this way in its help article on the 2026 changes: "re-issuing your order will result in a new certificate with the maximum possible validity period". It adds that existing multi-year plans stay usable through the term you paid for.
| A 1-year SSL bought | Certificates you install in that year | Domain checks |
|---|---|---|
| Now (200-day limit) | At least 2 | Up to 2 |
| After 15 March 2027 (100 days) | At least 4 | Up to 4 |
| After 15 March 2029 (47 days) | At least 8 | Practically every time |
Each manual reissue means creating a key and CSR, passing the domain check, downloading the files, installing them on the server and reloading it. Do that eight times a year and one missed reissue leaves your visitors looking at a "Your connection is not private" page. Before you renew a paid certificate, ask the seller three things:
- Does the plan support ACME, so your server can fetch each reissue by itself?
- Are reissues included in the price, and how many are allowed?
- What does the renewal cost, and does it differ from the first-year price?
Whoever issued your current certificate, check that its CA is still trusted. In October 2026 browsers began removing eMudhra's emSign roots after a key-generation failure; our guide to the emSign SSL distrust shows how to check your issuer and replace an affected certificate.
Let's Encrypt's move from 90 to 64 to 45 days
Let's Encrypt, the free, non-profit CA, has published its own schedule in two posts: From 90 to 45 (December 2025) and 64-day certificates (October 2026). Its profiles page lists the options you can choose today.
| Date | Let's Encrypt change |
|---|---|
| 13 May 2026 | The opt-in tlsserver profile issues 45-day certificates, with a 7-hour authorisation reuse period. |
| 14 October 2026 | The staging (test) environment starts issuing 64-day certificates. |
| 10 February 2027 | The default classic profile switches from 90-day to 64-day certificates, and authorisation reuse falls from 30 days to 10. |
| About 11 May 2027 | The last 90-day Let's Encrypt certificates expire. |
| 16 February 2028 | The default becomes 45-day certificates, with 7-hour authorisation reuse. |
A shortlived profile with 160-hour (about six-day) certificates is also available. The changes apply when a certificate is next renewed. Let's Encrypt says certificates that are already valid won't be revoked, and rate limits aren't affected.
Why a fixed "renew every 60 days" cron job will break
Some servers still renew on a fixed schedule written for 90-day certificates. A job that renews every 60 days leaves only 4 days of margin on a 64-day certificate, so a single failed attempt, from a DNS change, a closed port 80 or a rate limit, ends with an expired certificate. On a 45-day certificate it fails outright, because the certificate expires on day 45, before the job runs. Let's Encrypt's December 2025 post says plainly that "renewing at a hardcoded interval of 60 days will no longer be sufficient".
Its advice:
- Use ACME Renewal Information (ARI) if your client supports it. ARI, standardised as RFC 9773 in June 2025, lets the CA tell your client when to renew, and move that date earlier if it has to revoke certificates. The eMudhra incident is a reminder that mass revocations do happen.
- Otherwise, renew at about two-thirds of the lifetime: around day 43 of a 64-day certificate, or day 30 of a 45-day one.
- Search your scripts for old numbers. Let's Encrypt suggests grepping cron jobs, wrapper scripts and runbooks for 83, 80 or 60.
Certbot's own timer is already in good shape if it is recent. According to the Certbot changelog, version 4.0.0 (April 2025) renews when a third of the lifetime is left, instead of a fixed 30 days before expiry, and version 4.1.0 (June 2025) checks ARI automatically. A renew_before_expiry setting in a certificate's renewal file (/etc/letsencrypt/renewal/) still overrides the one-third default, so look for one.
How to check your SSL auto-renewal setup
On a Linux VPS that uses Certbot, these commands show what is installed, what it manages and whether renewal is scheduled:
certbot --version # 4.1.0 or later checks ARI
sudo certbot certificates # each certificate, its domains and expiry date
systemctl list-timers | grep certbot # systemd timer (snap: snap.certbot.renew.timer)
grep -rn certbot /etc/crontab /etc/cron.d 2>/dev/null # or a cron job instead
sudo grep -rn renew_before_expiry /etc/letsencrypt/renewal/
sudo certbot renew --dry-run # a full test renewal
Certbot's instructions say its packages come with "a cron job or systemd timer" that renews certificates automatically, and that you can find it in /etc/crontab, /etc/cron.*/* or systemctl list-timers. If none of those shows Certbot, nothing is renewing your certificates.
The --dry-run test runs against Let's Encrypt's staging server and doesn't save anything, so it is safe on a live site. Staging has issued 64-day certificates since 14 October 2026, so a passing dry run also shows that issuance works with the shorter lifetime. If it fails, the usual causes are a firewall blocking port 80, a domain that no longer points at the server, or a CAA record that excludes Let's Encrypt (see DNS records explained).
To check expiry from outside, on any certificate from any CA:
echo | openssl s_client -connect example.com:443 -servername example.com 2>/dev/null | openssl x509 -noout -issuer -enddate
Automation can fail without telling you, so add an outside check too: an uptime monitor that warns you about certificate expiry, or at least a calendar reminder two weeks before the date this command prints.
Do I need to buy an SSL certificate every year?
For most websites, no. A free domain-validated certificate from Let's Encrypt gives the same encryption as a paid DV certificate, and good hosting issues and renews it for you. Paying makes sense when you need an OV or EV certificate with your company's name (some tenders, banks and enterprise clients ask for one), want a warranty or support from the CA, or a client insists on a particular CA. Even then, the shorter lifetimes mean the yearly price buys a series of reissues, so automation matters as much as with a free certificate.
SSL on HostEthical hosting and Cloud VPS
On our web hosting, every site gets a free Let's Encrypt certificate. It is requested automatically once your domain points to us and renewed automatically, so nothing changes for you when certificates drop to 64 days in February 2027. There is no SSL add-on to buy, and the plan renews at the same price as the first year, from ₹99 a month, or about ₹82.50 a month when billed yearly.
A Cloud VPS is unmanaged: you get full root access, and the certificate setup is yours to run. Install Certbot or another ACME client, then use the checks above. Plans start at ₹860 a month, or about ₹774.17 a month when billed yearly, with a small monthly fee for the Mumbai location. Our guide to setting up a VPS covers the steps before you add SSL.
Frequently asked questions
What is the maximum SSL certificate validity in 2026?
Public SSL/TLS certificates issued on or after 15 March 2026 can be valid for at most 200 days, down from 398 days. The limit comes from CA/Browser Forum ballot SC-081v3, passed in April 2025 with the support of Apple, Google, Microsoft and Mozilla. It falls to 100 days for certificates issued from 15 March 2027 and to 47 days from 15 March 2029. Certificates already issued stay valid until their own expiry dates.
Do I need to buy an SSL certificate every year?
For most websites, no. A free domain-validated certificate from Let's Encrypt gives the same encryption as a paid one, and many hosts issue and renew it automatically. A paid certificate makes sense if you need your company name in it (OV or EV), a warranty, or a specific CA. Even a paid 1-year SSL now means reissuing at least twice a year, and at least four times a year from March 2027.
Will SSL certificates be valid for only 47 days in 2027?
No. Under the CA/Browser Forum schedule, certificates issued from 15 March 2027 can last up to 100 days. The 47-day limit applies only to certificates issued from 15 March 2029. Let's Encrypt moves faster with its own free certificates: 64 days by default from 10 February 2027 and 45 days from 16 February 2028, which may be where the 2027 claims come from.
How long is a Let's Encrypt certificate valid?
As of November 2026, Let's Encrypt's default certificates last 90 days. From 10 February 2027 the default becomes 64 days, and Let's Encrypt expects the last 90-day certificates to expire around 11 May 2027. From 16 February 2028 the default drops to 45 days. An opt-in 45-day profile has been available since May 2026, and a short-lived profile issues certificates of about six days.
How do I check if SSL auto renewal is working?
On a server that uses Certbot, run sudo certbot certificates to see each certificate and its expiry date, check systemctl list-timers or your crontab for a certbot entry, and run sudo certbot renew --dry-run to test a renewal against Let's Encrypt's staging server. On shared hosting, check the SSL section of your hosting dashboard for the expiry date. Add an outside expiry alert as well, because automation can fail silently.