−50%

50% off your first month on any paid plan · code WELCOME50 · until Nov 30

Start free →
Feature · Features

SSL Certificate Monitoring

Let's Encrypt certificates renew themselves every ninety days, until the renewal quietly breaks. WatchCron checks your certificates daily, alerts you well before expiry, and reminds you every day until you renew. Built into every uptime monitor, on by default.

Start monitoring free 20 checks free · no credit card
FIG 03example.com · SSL + WHOIS
The expiry window is marked ahead of time, and the alert goes out before it starts.

SSL monitoring is the simplest check WatchCron runs. Point it at a domain, it reads the certificate the server presents: who issued it, when it expires, whether the hostname matches. No agent to install, no DNS to change. The check is built into your existing uptime monitor and turned on by default, so if you're already watching a site's availability, the certificate is covered. This page covers why auto-renewal breaks more than you'd expect, what a manual check looks like versus an automated one, how alerts work, and where the honest limits are.

01 — Why a certificate lapses with no warning#

An expiry date is baked into a certificate the moment it's issued. The certificate works flawlessly right up to that second, then stops. No slow degradation, no error in your logs the week before. Fine one day, dead the next.

Auto-renewal is supposed to handle it, which is exactly why it's dangerous: when renewal works, it hides the deadline completely. The one time it fails, nobody has been looking at that date in months. Renewals break for boring reasons: a server migration, a changed DNS record, a rate limit on Let's Encrypt, a cron entry someone dropped during a Friday deploy. None of them announce themselves.

When you manage more than a handful of sites, the problem multiplies. A team with a dozen domains and subdomains has a dozen certificates, each with its own expiry, its own issuer, and no single place showing all those dates. WatchCron puts them in one column. A certificate with eight days left glows amber long before it turns into a browser warning.

Creating an uptime monitor with SSL certificate check enabled

02 — What checking by hand actually looks like#

You can inspect any certificate from a terminal:

$ openssl s_client -connect example.com:443 -servername example.com 2>/dev/null \
  | openssl x509 -noout -dates -issuer

notBefore=Jan 15 00:00:00 2026 GMT
notAfter=Apr 15 23:59:59 2026 GMT
issuer=C = US, O = Let's Encrypt, CN = R11

Three lines. That's all you need: valid-from, expires, who signed it. The problem isn't getting the information. It's remembering to ask. For one domain you'll check when something feels off. For twelve domains across three servers, you won't. And the certificate that lapses is never the one you were already worried about.

Online checkers like SSL Labs and Why No Padlock give you a one-time snapshot with a grade, but they don't watch the clock for you and they don't send an alert when a cert drops below 14 days. Certbot's --dry-run verifies that renewal would work, but only if someone runs it. Monitoring fills the gap between knowing how to check and actually checking, every day, across every domain.

03 — Built into every uptime monitor#

There's no separate SSL product to buy or configure. Certificate checking is a property of every uptime monitor, a checkbox that's on by default. The moment you add a site for availability monitoring, you're watching its certificate too. If uptime monitoring is already running, certificates are covered without touching another setting.

This is the certificate side of an uptime monitor, not the request-and-response side. Same check, different layer. One monitors whether the site answers. The other monitors whether the padlock stays green.

04 — What WatchCron reads off the certificate#

On each check, WatchCron connects to the host on port 443, reads the certificate the server presents, and records what matters: the subject (who it was issued for), the issuer (Let's Encrypt, DigiCert, Cloudflare, and the like), the valid-from date, and the expiry date. It verifies the certificate chain and confirms the hostname matches, so a cert issued for the wrong name doesn't quietly pass as healthy.

Everything is cached. The dashboard shows issuer, validity window, and days remaining instantly, without reconnecting every time you look.

Uptime monitor detail tracking SSL certificate expiry

05 — Alerts fire early and repeat until you renew#

You set the warning threshold per monitor: anywhere from 1 to 90 days before expiry, defaulting to 14. When a certificate crosses that line, the alert goes through whatever channels that monitor uses. Then WatchCron reminds you once a day until the certificate is actually renewed. One lost email doesn't cost you the deadline. Renew the cert and the reminder resets, ready for the next cycle.

SSL certificate lifecycle timeline with configurable warning thresholds at 30, 14, and 7 days before expiry

Already-expired certificates alert too, with the days-remaining counter ticking into the negative. Negative twelve means twelve days past expiry and every visitor sees the browser warning.

One detail keeps the signal clean: certificate warnings don't touch the up/down status. A site with a cert expiring next week is still serving traffic, so an expiring certificate is a warning, not a downtime alarm. It won't page someone at 3 AM as if the site were offline.

Alerts route through the same channels as everything else in WatchCron. Free includes 3 channels (pick from email, Slack, Telegram, webhooks, or any other supported type); Starter raises that to 10, Pro to 25, Business removes the cap. SMS opens on Pro, voice calls and WhatsApp on Business.

06 — What teams actually watch#

The most common setup is straightforward: one uptime monitor per production domain, SSL checking on by default, a 14-day warning threshold. For most solo developers and small SaaS teams, that's enough.

Agencies managing client sites run one monitor per client domain, organized into separate projects with per-client alert channels. When a client's staging cert expires, the alert goes to the right person, not the whole team. Some agencies deal with wildcard certs on shared hosting where one renewal failure takes down SSL for every client site behind it. Catching that early is worth more than catching a single-domain cert.

E-commerce teams care most about the checkout subdomain. A lapsed cert on a blog post costs you some SEO trust. A lapsed cert on checkout.example.com costs you every sale until someone notices. Different stakes, same 14-day warning.

Multi-domain setups are where the dashboard view earns its keep. Fifteen domains, three different issuers, renewal dates scattered across the calendar. No one tracks that in a spreadsheet for long. And self-signed certificates on staging environments are the ones people forget entirely: they set a one-year expiry during setup and never think about it again.

07 — What it doesn't check#

The check reads the certificate the server hands over on port 443, which sets its honest boundaries. It won't tell you a certificate has been revoked: it doesn't query OCSP or CRL. It doesn't grade key strength or cipher choice. It validates the leaf certificate your server presents, not every intermediate in the chain individually. Checks come from a single location.

Because the certificate check rides on an uptime monitor, you can't watch a certificate in isolation without also monitoring the site. For almost every site, that pairing is exactly what you'd want. For the rare case where you need cert-only monitoring (an API endpoint you don't want uptime checks on, say), it's not the right fit today.

Worth separating: domain registration runs on a completely different clock. A domain can lapse while every certificate is perfectly valid. That's a separate check: domain expiration monitoring, a different deadline on a different clock. The comparison of monitoring types and the docs cover how the layers fit together.

Every uptime monitor checks its certificate by default, warns you with days to spare. Free plan: 20 checks, 3 alert channels, no credit card. No separate SSL tool to wire up.

08 — Start watching your certificates#

Add your first site and SSL checking turns on automatically. See what each plan includes on the pricing page, or create an account and let the countdown start working for you instead of against you. You can also check any certificate right now with our free tool.

09 — FAQFrequently asked#

No. Certificate checking is built into every uptime monitor as a checkbox that's on by default, so monitoring a site's uptime already covers its certificate. There's no separate tool or config.

You choose, anywhere from 1 to 90 days, with 14 as the default. After the first warning it reminds you once a day until the certificate is renewed, so a single missed alert doesn't cost you the deadline.

No. The certificate layer is separate from the up/down status. A site with a soon-to-expire certificate is still up, so you get an SSL warning without a false downtime alarm.

It reads whatever certificate the server returns for the host you're monitoring, so a wildcard or multi-domain certificate serving that host is read normally. It doesn't enumerate every name on the certificate separately.

Revocation (OCSP or CRL), key strength, and each intermediate certificate on its own. It focuses on the leaf certificate the server presents on port 443.

Your first check takes a minute.

Free plan includes 20 checks · No credit card required
Pricing Docs
Log in Start free →