Let's Encrypt no longer sends expiry emails
Let's Encrypt ended its expiry emails on June 4, 2025. If you relied on them as a backstop, a failed renewal now brings no message from Let's Encrypt, and its announcement points subscribers to third-party monitoring.
Why they ended
Let's Encrypt gave four reasons: more subscribers have reliable automation, keeping the emails meant keeping millions of email addresses tied to issuance records, the service cost tens of thousands of dollars a year, and it added complexity to their infrastructure.
What the emails could not tell you
Those emails came from the CA's issuance records, not from your server. They could not tell you that a renewed certificate never reached it, that its chain was incomplete, or that the host had stopped answering.
What to set up instead
- Confirm your renewal is scheduled and passes a test. For certbot, the renewal guide covers both.
- Make a failed renewal reach you. A log nobody reads is what those emails used to cover for.
- Watch the live certificate from outside, so a renewal that worked but never loaded is caught too.
What CertWatch does in their place
Give CertWatch a hostname and port. It connects every hour, on every plan, and reads the certificate clients actually get. It works out when each certificate should renew from your CA's renewal window once your client follows it, its past renewals, or a renewal setting you give it, so a certificate renewed on schedule never alerts. When a renewal is late, it alerts you by email, or on Slack or a webhook where your plan includes them. It also reads Let's Encrypt's renewal windows, so if the CA pulls a window forward ahead of a revocation, the certificate turns Urgent within hours, as soon as CertWatch next reads the CA's renewal window, even with weeks left.
Check a hostname now with the free checker, no account needed, or add it to CertWatch to be told when a renewal is late.