Website monitoring

SSL certificates now last 200 days. Here is how to never miss a renewal.

An expired certificate does not break your website. It does something worse: every visitor gets a full-page security warning, and most of them leave. Certificate lifetimes have just been cut to 200 days, and they fall to 47 days by 2029, so renewals that used to come round once a year now come round every few weeks. This is what has changed, why renewals still get missed when they are automated, and how to hear about one before your customers do. Domain names get the same treatment at the end.

Updated 14 November 2026Read 8 minutesFor anyone responsible for a website

The short version

  • Public SSL/TLS certificates issued from 15 March 2026 last at most 200 days.
  • That falls to 100 days from 15 March 2027 and 47 days from 15 March 2029.
  • Renewing by hand stops being realistic. Automate it, usually with ACME.
  • Automation fails quietly, so check the certificate your website actually serves, from outside your own network.
  • Domain registrations expire too, and take your website and your email down together.
  • Get a warning weeks ahead, sent to more than one person.

The new timetable

Browsers only trust certificates issued under rules set by the CA/Browser Forum, the body where certificate authorities and browser makers agree them. In April 2025 it voted to shorten how long a public certificate may last, in three steps. It also shortened how long a certificate authority may rely on its last check that you control the domain, so renewals have to prove control far more often.

Certificates issuedLongest a certificate can lastHow long a domain check can be reused
Before 15 March 2026398 days398 days
From 15 March 2026200 days200 days
From 15 March 2027100 days100 days
From 15 March 202947 days10 days

The reasoning is security: a certificate that is stolen or issued by mistake is useful to a criminal for weeks rather than a year, and organisations are pushed into automation that can replace every certificate quickly if it ever has to. The cost falls on anyone still renewing by hand, or relying on a reminder email to one person.

What an expired certificate does

  • Visitors see a warning, not your website. Every major browser shows a full-page alert saying the connection is not private. Most people will not click past it, and they should not have to.
  • Apps and integrations stop. Payment callbacks, APIs, mobile apps and partner systems that call your site usually refuse the connection outright, with no warning to click through.
  • It looks like an attack. To a customer, a security warning on your website is indistinguishable from a compromised one.
  • It is hard to spot from inside. The server is up and the pages are fine, so uptime checks that only ask "did it answer?" can report all clear.

Why renewals get missed

Almost never because nobody cared. Usually because of something like this:

  1. The reminder goes to someone who has left, or to a shared inbox nobody reads.
  2. The renewal job stopped running after a server was rebuilt, moved or upgraded, and nothing said so.
  3. Validation started failing. A firewall rule, a DNS change or a redirect stops the certificate authority checking the domain, so the renewal never completes.
  4. The new certificate never reached the right place. It was issued, but the load balancer, CDN or appliance in front of the website still serves the old one.
  5. A hostname was forgotten. The main site renews, but the client portal, the old marketing site or the mail server has its own certificate on its own schedule.
  6. The payment card expired, so a paid certificate or the hosting that provides it was not renewed.

Shorter lifetimes multiply these. A process that fails one renewal in fifty is a minor nuisance once a year. At 47 days, the same process fails several times a year across a handful of websites.

Automate the renewal

The answer to short lifetimes is to take people out of renewal altogether.

  • Use ACME wherever you can. It is the standard protocol for requesting and renewing certificates automatically, supported by most certificate authorities, web servers, hosting platforms and CDNs.
  • Let the platform manage it. If your hosting provider or CDN offers managed certificates, they renew and install them for you, which removes the "issued but never installed" failure.
  • Renew well before expiry. Renewing when about a third of the lifetime is left gives several retries before anything breaks.
  • Make a list of every certificate, where it is served and how it renews. The ones that cannot be automated, such as some appliances and older systems, are the ones that need a person and a date.

Watch it from the outside

Automation tells you it ran. It does not tell you that visitors are now getting a valid certificate. For that, something has to connect to your website the way a visitor does, read the certificate that comes back, and warn you while there is still time to act.

  • Check what is served, not what is stored. The certificate in your renewal tool and the one your load balancer presents are not always the same.
  • Check every hostname, including the ones nobody visits often.
  • Check from outside your own network and providers, so the check still works when the thing that failed is the system that would have warned you.
  • Warn early, and warn more than one person, so a holiday or a resignation does not turn a reminder into an outage.

How Walters Sentinel Monitoring does this

Monitoring connects to each of your websites the way a browser does and reads the certificate it is actually given. You are warned when 14 days or fewer remain, and again if it expires. It also checks that the website is up, warns 30 days before the domain registration runs out, and tells you when the domain's A, NS or MX records change. Alerts go to a distribution list rather than one person, can escalate if nobody acts, and can reach you by email, SMS, Slack or Teams.

Domain names expire too

A domain registration is renewed once a year or every few years, which makes it easy to forget. When it lapses, the domain stops pointing at your website and your mail servers, so both stop at once.

  • Turn on auto-renew at your registrar, and keep the card on the account current.
  • Keep the registrar contact address on a shared mailbox, not one person's inbox.
  • Lock the domain against transfers you did not ask for, and protect the registrar account with multi-factor authentication.
  • Do not rely on the grace period. Registries usually hold an expired domain for a while so the owner can recover it, often for a fee, but your website and email are down for that time, and a domain left too long can be registered by anyone.

DNS changes nobody made

The records that point your domain at your website and mail servers can change without anyone touching the website: an edit made in the wrong zone, a registrar account taken over, a provider migration that did not copy everything. A change to the name servers (NS), the website address (A) or the mail servers (MX) can quietly send visitors or email somewhere else. Knowing the moment those records change, and being able to say whether anyone meant to change them, closes the gap.

The checklist

Certificate and domain expiry checklist 0 done

Know what you have

Automate

Watch

Protect

Questions people ask

How long can an SSL certificate last in 2026?

A public SSL/TLS certificate issued on or after 15 March 2026 can be valid for at most 200 days. Certificates issued before that date could last up to 398 days, so some of those are still in use until they run out.

When do 47-day certificates start?

From 15 March 2029. The limit falls to 100 days on 15 March 2027 first, then to 47 days in 2029. The CA/Browser Forum, where certificate authorities and browser makers set the rules, agreed the timetable in April 2025.

Do I have to renew by hand every few weeks?

No, and you should not try. Renewal is meant to be automated, usually with the ACME protocol, which most certificate authorities and hosting platforms support. The shorter lifetimes are designed to make manual renewal impractical.

If renewal is automated, why monitor the certificate?

Because automation fails quietly. A renewal job stops after a server move, a firewall change blocks the validation check, or a new certificate is issued but never reaches the load balancer that actually serves it. Checking the certificate your website really presents, from outside your network, is the only way to know.

What happens when a certificate expires?

Browsers show a full-page security warning instead of your website, most visitors leave, and apps and integrations that call your site usually stop working altogether. Nothing about the website itself has changed, which is why it often takes a while to work out what has gone wrong.

What happens if our domain name expires?

Your website and your email stop working, often within days, because the domain no longer points anywhere. Most registries hold an expired domain for a while so the owner can renew it, sometimes for a fee, but leave it long enough and anyone can register it, including whoever wants to receive your email.

Where this comes from

The dates are those set by the CA/Browser Forum for publicly trusted TLS certificates. Certificates from a private, internal certificate authority follow whatever rules that authority sets.