If you run websites for other people, one date matters more than most this year: March 15, 2027.

The CA/Browser Forum voted to shorten the maximum lifetime of public TLS certificates in three steps:

From Maximum validity
Today (since March 15, 2026) 200 days
March 15, 2027 100 days
March 15, 2029 47 days

The proof of domain control that a certificate authority accepts is shortened too, down to 10 days in 2029. In practice: a certificate that someone renews by hand once a year will start throwing "Your connection is not private" at visitors, and the hand-renewed ones are the ones nobody remembers until they fail.

Why this hits agencies and hosts first

One forgotten certificate is an incident. A portfolio of 80 client sites, each with its own host, DNS provider and renewal method, is a monthly source of tickets. The rule does not break the automated sites. It breaks the exceptions: the old VPS, the client who bought a certificate on their own, the mail server, the staging site that became production.

A checklist you can run this week

  1. List every certificate you are responsible for, not only the websites: www and apex, API hostnames, mail servers (SMTP and IMAP certificates expire too), admin panels, anything behind a load balancer or CDN.
  2. Mark how each one is renewed. Automatic (ACME with certbot, acme.sh, Caddy, your host's panel) or by hand. Every "by hand" is a ticket waiting to happen in 2027.
  3. Move the manual ones to ACME. With DNS-01 validation you also cover wildcards and servers that cannot open port 80.
  4. Check that renewal actually reloads the service. A new certificate on disk that nginx or Apache never reloaded is the classic failure behind "it renews but the site still shows the old one".
  5. Decide who is alerted when a renewal fails, and on which channel. An e-mail to a mailbox nobody reads is not an alert.
  6. Look at the expiry dates from the outside, the way a visitor sees them, not from your own configuration. What your server says and what the internet sees can differ (wrong certificate on a CDN, a forgotten copy on another IP).
  7. Re-run the check after every migration: DNS change, new host, new CDN.

The point of external checks

Everything above is about your configuration. The only thing that matters to the visitor is what is served on the public internet. A free external check takes seconds: type a domain and read the expiry date, the issuer and the chain.

I built one at AttackScout (free, no account): https://attackscout.com/en/tools/ssl-certificate-check?utm_source=devto&utm_medium=article&utm_campaign=cert-100-days. It shows the expiry date and the days left. Daily monitoring of a portfolio, with an alert before each expiry, is the paid part. Any monitoring tool that checks from the outside does the same job; the important thing is that someone checks.

What to do now

You have until March 2027. Start with the inventory: it is the step that always reveals the forgotten certificate.

If you manage many domains for clients and want to check a whole portfolio, tell me what would help most in the comments.