Names Organizer
Windows 10 & 11 Buy license · $49.95
Reference

SSL Certificate Validity Period: The 200, 100 and 47-Day Schedule

The SSL certificate validity period is shrinking: 200 days from March 2026, 100 days from 2027 and 47 days from 2029. What changes and how to keep up.

Updated 5 minute read The Names Organizer team

The maximum validity period for a publicly trusted SSL/TLS certificate is getting shorter in three steps. Certificates issued from March 15, 2026 can be valid for at most 200 days. From March 15, 2027 the limit drops to 100 days, and from March 15, 2029 it drops to 47 days. Before March 2026 the limit was 398 days, roughly 13 months. The schedule was agreed by the CA/Browser Forum, the body of certificate authorities and browser makers that sets the rules for public certificates, and it applies to every certificate authority that browsers trust.

In practice this means certificates will need replacing several times a year, and by 2029 almost monthly. If you still renew certificates by hand, now is the time to automate, and to have an independent way to spot one that did not renew.

The schedule at a glance

Certificates issuedMaximum validityDomain validation can be reused for
Before March 15, 2026398 days398 days
From March 15, 2026200 days200 days
From March 15, 2027100 days100 days
From March 15, 202947 days10 days

The limits apply by issue date. A certificate issued on March 14, 2026 with a 398-day life stays valid for its full term; it is only the next one that is shorter.

The right-hand column matters as much as the left. Domain control validation is the check a certificate authority runs to confirm you control the domain, for example by finding a DNS record or a file on your web server. Today a successful check can be reused for later certificates for a while. By 2029 that reuse window shrinks to ten days, so in practice every certificate will need a fresh validation.

How we got here

Certificate lifetimes have been falling for over a decade. Public certificates once lasted up to five years. The maximum was reduced to 39 months, then to 825 days in 2018, and to 398 days for certificates issued from September 1, 2020. The 2026 to 2029 schedule continues the same direction.

The reasoning is about security. A certificate is a statement that, when it was issued, a particular key belonged to a particular domain. The longer it lasts, the longer a stolen key or outdated information remains trusted. Revocation, the mechanism for cancelling a bad certificate early, has never worked reliably across all browsers, so shorter lifetimes limit the damage instead. Short lifetimes also force automation, which makes it easier to replace certificates quickly when something like a cryptographic weakness is found.

What changes for you

If your certificates already renew automatically

If your host or server uses the ACME protocol, the standard used by Let's Encrypt and many other certificate authorities and hosting control panels, you are mostly ready. Many automated certificates already last 90 days or less. Check that renewal is genuinely automatic for every site, not just the main one, and that it validates successfully each time.

If you buy and install certificates by hand

This is where the change hurts. At 200 days you replace each certificate about twice a year; at 100 days about four times; at 47 days about eight times. For each certificate you will need to:

  1. Check your certificate authority or host supports automated issuance and installation (ACME or their own agent).
  2. Move to automation now, while the interval is still 200 days, so you have time to fix problems.
  3. Check how your current certificate subscription works. Many certificate authorities sell annual or multi-year plans that cover as many reissues as you need within the term.
  4. Identify devices and services where certificates are installed by hand, such as load balancers, firewalls, mail servers or appliances, and plan for them separately.

These limits apply to publicly trusted certificates used by websites and other public services. Certificates from a private certificate authority, used inside your own network, follow whatever policy that authority sets.

Why automation still needs monitoring

Automatic renewal removes most of the work, but it fails silently more often than people expect. Common causes include:

  • A DNS change, such as a host move or new nameservers, that breaks the validation step.
  • A firewall or redirect rule blocking the validation file.
  • An API token for DNS validation that expired or was revoked.
  • A server where the new certificate was issued but the web service was never reloaded to use it.
  • A site that moved to another server where nobody set up renewal.

With 47-day certificates, a renewal that fails quietly gives you very little time before visitors see a security warning. Our guide to fixing an expired SSL certificate covers what to do when it happens.

A planning checklist for 2026 to 2029

  1. List every certificate you are responsible for: websites, subdomains, mail servers, APIs and devices. Our domain audit checklist is a good place to start.
  2. Mark how each one renews: automatic through the host, automatic through your own ACME client, or manual.
  3. Automate the manual ones before the 100-day limit in March 2027, when manual renewal becomes a quarterly job.
  4. Prefer DNS or HTTP validation that runs unattended, since by 2029 validation will need to happen for almost every certificate.
  5. Set alerts that do not depend on the renewal system itself.

How to check a certificate's validity period

  1. Open the site in Edge or Chrome and click the icon to the left of the address.
  2. Choose Connection is secure, then Certificate is valid.
  3. The General tab shows Issued On and Expires On. The difference is the validity period.
  4. The Details tab lists the names the certificate covers under Subject Alternative Name.

See how to check an SSL certificate's expiration date for other methods.

Keeping track as lifetimes shrink

Checking certificates by hand was manageable when they lasted a year. With certificates turning over several times a year across many sites, an independent check is worth having. Names Organizer, a domain manager for Windows, records the SSL certificate for each domain and includes certificate expiry in its alerts, with a dashboard countdown and desktop and optional email reminders at intervals you choose. As lifetimes shorten, shorter warning intervals such as 14 and 3 days make sense. Names Organizer's expiring-soon report lists domains and certificates due in the next 30, 60 or 90 days, which is a quick way for an agency to confirm that every client site renewed. It does not issue or install certificates, which stays with your host or certificate authority, but it tells you when one did not renew in time.

Frequently asked questions

Do the new limits affect certificates already issued?

No. They apply to certificates issued on or after each date. A certificate issued before March 15, 2026 keeps its original validity.

Do shorter certificates cost more?

Pricing depends on the certificate authority. Most sell annual or multi-year subscriptions that cover several reissues.

Do the limits apply to internal or private certificates?

No. They apply to publicly trusted TLS certificates. Private certificate authorities set their own policies.

Get three guides like this every month, plus software update notices.Subscribe →