Get an alert before an SSL certificate or domain expires
An expired SSL certificate takes a site down as surely as a crash: browsers refuse it, and API clients stop with a certificate error. Certificates are getting shorter and one of the most common reminders is gone. An expiry check on every request gives you weeks of warning before the certificate or the domain runs out.
What changed
- Shorter certificates. In April 2025 the CA/Browser Forum passed ballot SC-081, which lowers the maximum lifetime of public TLS certificates in steps, from 398 days to 47 days by March 2029. The first step took effect in March 2026, when the maximum became 200 days. More renewals mean more chances for one to fail.
- No more reminder emails from Let's Encrypt. Let's Encrypt announced in January 2025 that it would stop sending expiration notification emails, and the service ended in June 2025. If your renewal automation breaks, nobody tells you any more.
- Domains, too. Since 28 January 2025, RDAP has replaced WHOIS as the definitive source of registration data for generic top-level domains (ICANN). It also makes the domain's expiry date easier to read automatically, for the domains whose registry publishes it.
Renewal automation usually works, which is exactly why nobody watches it. A changed DNS record, a firewall rule that blocks the validation request, a certificate renewed on one server but not on the load balancer: each one leaves the old certificate in place until the day it expires.
Check the certificate on every request
A TaskBeacon website check requests your address every 1 to 60 minutes from our server. For an https:// address it reads the certificate's expiry date each time, so it sees the certificate visitors actually get, after load balancers and CDNs. You get:
- Odd data when the certificate expires within 14 days, or the domain within 30 days (both adjustable).
- Failed when the certificate is already invalid or expired, the site is down, answers with an error status, or misses a word that should be on the page. A failure is checked again about a minute later before it alerts.
- Odd data when the site answers far slower than usual twice in a row.
The domain's expiry date is looked up once a day through RDAP. Not every registry publishes it: many country-code domains have no RDAP service, and then the job page says unknown and you get no domain warning for it. Nothing to install; add the address and you are done. Details are in Website and API checks.
Certificate and domain expiry alerts and 1-minute checks are part of Pro, open to everyone for now; Free includes 3 website checks every 5 minutes or less often. See Pricing.
Internal sites and services
We only check public addresses: anything that resolves to a private or local network is refused, so a check can't be used to look inside a network. For an intranet site or an internal API, run a small scheduled script on your side that does the check and pings TaskBeacon, like any other job; see heartbeat monitoring.
Without TaskBeacon
Run a daily script that connects to each site, reads the certificate's notAfter date (for example with openssl s_client and openssl x509 -enddate) and emails you when fewer than 14 days are left. Calendar reminders for domains work too, if someone keeps them up to date. And check that your ACME client or hosting panel logs and reports renewal failures; with shorter certificates, that log matters more than it did.
Connected Claude or ChatGPT to TaskBeacon? Ask it "what failed last night, and why?" and it answers from your jobs. How that works.
Related
In the Docs: Website and API checks · SSL and domain expiry · Alerts.
- Get an alert when a website is down or slowDown, wrong status, missing text or much slower than usual.
- Heartbeat monitoring (a dead man's switch) for scheduled scriptsThe job checks in on every run; silence is the alert.
- Find out when a scheduled job didn't run at allA run that never happened leaves no error to alert on.
TaskBeacon is free to start, with every feature open for now and no credit card. Create a job, paste the code, and the first ping shows up on the job page.
Start free View live demoSources
- Let's Encrypt: Ending support for expiration notification emails (2025-01-22)
- Let's Encrypt: Expiration notification service has ended (2025-06-26 (service ended 2025-06-04))
- CA/Browser Forum: Ballot SC-081v3, schedule of reducing certificate validity (2025-04-11)
- CA/Browser Forum Baseline Requirements 2.3.1, section 6.3.2: 200 days from 2026-03-15, 100 from 2027-03-15, 47 from 2029-03-15 (2026-10-04)
- ICANN: Launching RDAP; sunsetting WHOIS (2025-01-27)
Page checked against its sources on 2026-11-09. Menus and limits of other products change; if something here no longer matches, write to support@taskbeacon.io.