CloudSpex

Domain health guide

Let's Encrypt no longer emails you before a certificate expires

For years the expiry notice from Let's Encrypt was the safety net behind automatic renewal. That email service ended on June 4, 2025. Automation still renews certificates; it just no longer has anything behind it when it fails.

Use the SSL Certificate Checker

Türkçe

What changed

Let's Encrypt announced in early 2025 that it would stop sending expiration notification emails, and ended the service on June 4, 2025. The reasons it gave were that most subscribers renew automatically, that storing millions of email addresses was a privacy cost, and that the notices were expensive to run.

Nothing changed about the certificates themselves. They are still valid for ninety days, and ACME clients still renew them, typically with thirty days left.

Why renewals fail without anyone noticing

Automatic renewal depends on things that change. A renewal that worked for two years can stop because of something unrelated to certificates.

  1. The DNS record used for validation was changed or the domain moved to a different DNS provider.
  2. A firewall or CDN rule now blocks the HTTP validation path.
  3. The server was migrated and the scheduled renewal job was not moved with it.
  4. An API token for DNS validation expired or was rotated.
  5. A CAA record was added that does not authorise the certificate authority.
  6. The certificate renewed correctly but the web server was never reloaded, so it still serves the old one.

The last case is the one checks miss

A renewal log that says success is not proof. What matters is the certificate a visitor is actually served. The only reliable check connects to the site from outside and reads the expiry date of the certificate in the handshake.

The same is true for services other than the website: a mail server, an API host or a subdomain can each serve a different certificate with a different expiry.

How to monitor expiry yourself

Check from outside the server, on a schedule, and alert with enough time to act.

  1. List every hostname that serves a certificate, including subdomains and mail hosts.
  2. Check each one externally at least daily and read the served certificate's expiry.
  3. Alert when fewer than fourteen days remain. With thirty-day renewal, that means renewal has already been failing for two weeks.
  4. Send the alert somewhere a person reads, not to the mailbox that used to receive the Let's Encrypt notices.
  5. Check that the certificate covers the hostname and that the chain is complete, not only the date.

For agencies managing client sites

Client sites usually sit on hosting the agency does not control, with renewal set up by someone who has since left. The expiry email was often the only signal that reached the agency at all. External monitoring across every client domain replaces that signal and turns an outage reported by the client into a renewal fixed before it.

What the email used to do for you

The notice arrived when a certificate was getting close to expiry and had not been renewed. On a healthy system it never came, because renewal happened first. Its real function was as an alarm for failed automation: the only message most people ever received from their certificate setup was the one that said something had gone wrong.

That is the gap left behind. Nothing about issuing or renewing changed. What disappeared is the single independent signal that reached a human when renewal had silently stopped.

Find out what you have

The first task is to list the certificates and how each is renewed. On a server that uses Certbot, the client can report this itself, and a dry run shows whether renewal would succeed today without issuing anything.

Listing certificates and testing renewal with Certbot
certbot certificates
certbot renew --dry-run
systemctl list-timers | grep -i certbot

Read the served certificate, not the file

A renewed certificate on disk does not help if the web server is still running with the old one in memory. The check that matters connects from outside and reads the certificate in the TLS handshake. Compare its expiry date with the file on disk; if they differ, the server was not reloaded after renewal.

The certificate a visitor is served
openssl s_client -connect example.com:443 -servername example.com </dev/null 2>/dev/null \
  | openssl x509 -noout -enddate

notAfter=Feb  8 11:42:05 2027 GMT

Make sure renewal reloads the server

The most common silent failure is a successful renewal that never takes effect. ACME clients can run a command after each successful renewal, and that command should reload whatever serves the certificate: the web server, a mail server, a proxy.

Check this for every service that uses the certificate, not just the website. A mail server or a database listener that reads the same files will keep the old certificate until it is restarted.

A deploy hook that reloads the web server after renewal
certbot renew --deploy-hook "systemctl reload nginx"

Shorter certificates are coming

Let's Encrypt now also offers certificates valid for about six days, intended for fully automated environments, and the industry as a whole is moving to shorter lifetimes in stages over the next few years. Shorter lifetimes reduce the damage a stolen key can do and make revocation matter less.

They also shrink the time between a renewal failure and an outage. With a ninety-day certificate renewed at sixty days, a broken renewal leaves thirty days to notice. With shorter certificates the margin is days. Monitoring that checks once a week is no longer enough; daily is the minimum.

ACME Renewal Information

One change works in your favour. A protocol extension called ACME Renewal Information lets the certificate authority tell a client when it should renew, instead of the client deciding from a fixed number of days. If the authority needs to revoke certificates early, clients that support the extension renew ahead of the revocation without anyone intervening.

Support depends on the client and its version. Updating the ACME client to a current release is the simplest way to get it, and is worth doing in any case: old clients are a common cause of renewal failures after the authority retires an older protocol feature.

Certificate transparency as a second signal

Every publicly trusted certificate is recorded in certificate transparency logs, which anyone can search. They are useful in two ways. They show every certificate issued for your domain, including ones for subdomains you forgot and ones requested by a platform on your behalf. And they show when the last certificate for a name was issued, which tells you whether renewal is still happening.

A certificate for your domain from an authority you do not use is worth investigating. It may be a hosting or CDN platform acting for you, or it may mean someone else has control of a name.

Replacing the alarm

The replacement for the email has three properties: it is external, it is frequent and it reaches a person.

  1. List every hostname that serves a certificate, including mail hosts and subdomains.
  2. Check each from outside at least once a day and record the days remaining.
  3. Alert at fourteen days remaining and again at seven, three and one.
  4. Send alerts to a team address or channel, not to an individual, and not to the address that used to receive the Let's Encrypt notices.
  5. Include in the alert which system renews the certificate and who owns it.
  6. Test the alert path once by checking who actually receives a notification.

If you rely on a hosting platform

Many sites never run an ACME client: the hosting company, site builder or CDN issues and renews certificates in the background. The platform's renewal can fail for the same reasons, most often because a DNS record it depends on was changed. Platforms do not always tell you, and the address they would tell is often the one of whoever created the account years ago.

External monitoring is the same whoever renews. It does not need access to the platform and it reports the only thing that matters: the certificate a visitor gets today, and how many days it has left. CloudSpex reads that certificate for each monitored host, and for the important subdomains, and alerts before it expires. It does not renew certificates and does not need credentials for your server.

What to do this week

If you have not looked at this since the emails stopped, three checks cover most of the risk and take less than an hour.

  1. Run a renewal dry run on every server that uses an ACME client and fix anything it reports.
  2. Read the served certificate on each hostname from outside and note the days remaining. Anything under thirty days on an automated setup means renewal is already failing.
  3. Set up an external expiry check with alerts to a shared address, and confirm who receives them.

Frequently asked questions

Do Let's Encrypt certificates still renew automatically?

Yes. Automatic renewal through an ACME client is unchanged. Only the notification emails ended.

How long is a Let's Encrypt certificate valid?

Ninety days. ACME clients normally renew when about thirty days remain.

Does CloudSpex renew certificates?

No. CloudSpex reads the certificate a host serves and alerts before it expires. Renewal stays with your ACME client or hosting provider.

Did Let's Encrypt recommend an alternative to its emails?

It pointed subscribers to third-party monitoring services and to keeping ACME clients up to date. It does not operate a replacement notification service itself.

Is a renewal log saying success enough?

No. It shows that a new certificate was obtained, not that the server is serving it. Only an external check of the served certificate confirms that.

How do I see every certificate issued for my domain?

Search the certificate transparency logs for the domain name. Public search tools list each certificate with its names, issuer and dates.

Use public checks as a starting point

CloudSpex reads limited public-facing signals. It does not change DNS, website, certificate, or email settings. Confirm the responsible provider and test relevant changes before applying a remediation.

Editorial details

Author and reviewer: CloudSpex. Sources: public technical standards and provider documentation relevant to the topic. Last reviewed: November 10, 2026. We update guides when the product behavior or the underlying guidance changes.