Security · Available on All tiers

The outage nobody sees coming until it's Monday morning.

Add expiry monitoring to any HTTP(S) check and get a warning email once the certificate's remaining validity drops below the threshold you set — before your customers see a browser warning instead of your site.

Start Free → See pricing

Free forever plan, no card required.

Why it matters

SSL certificate expiry

Certificates don't fail loudly — they expire quietly, usually over a weekend, and the first sign is a support ticket from a customer staring at "Your connection is not private." By then it's already an incident, not a maintenance task. It's a particularly frustrating way to go down, too, because nothing about your server or application actually broke — the code is fine, the database is fine, the deploy from three weeks ago is fine. A date on a certificate just quietly passed, and now every browser hitting your site shows a full-page security warning instead of your homepage, which looks far worse to a first-time visitor than a plain 500 error ever would. Renewal is usually a five-minute task. The problem was never the renewal — it was nobody knowing it needed to happen before a customer found out for you. It's the monitoring equivalent of a smoke alarm with a dead battery — everything looks fine until the exact moment it matters. That's what makes it such an unforgiving failure mode — everything was fine right up until a date on a calendar nobody was watching.

No separate check to configure

Turn it on for any existing HTTP(S) monitor in one click — nothing new to set up from scratch. There's no separate certificate-monitoring product to configure, no second dashboard to check, and no extra monitor eating into your plan's limit; it just rides along with the check you already have running against that endpoint. It's designed to be the easiest security control you'll ever turn on. There's no learning curve and no new workflow to adopt, just one extra option turned on.

One-time warning, not noise

A single email once you cross the threshold, not a daily reminder you learn to ignore and eventually miss. Daily nag emails are how expiry warnings end up filtered straight to a folder nobody opens — one well-timed email, sent once, is far more likely to actually get read and acted on before the certificate lapses. That restraint is deliberate — the goal is one email you actually read, not an inbox you learn to skim past. Fewer, better-timed emails beat a flood of reminders that eventually blur into background noise.

Set your own runway

Choose how many days of warning you want, based on how fast your team can actually renew and redeploy. A team on a fully automated renewal pipeline might only need a couple of days as a backstop; a team that renews manually and redeploys by hand is usually better off with two or three weeks of runway so it's never a last-minute scramble. There's no one-size-fits-all number here, because every team's renewal process moves at a different speed. Whatever number you pick today can always be adjusted later as your team's own process changes.

FAQ

SSL certificate expiry, answered.

Do I need a separate monitor for this?

No — turn it on for any existing HTTP(S) monitor in one click. There's nothing new to configure from scratch, no extra monitor slot spent from your plan's limit, and no separate dashboard to remember to check — it's just an option on the check you already have running. It's a toggle on the monitor's existing settings page, not a separate product to purchase. It genuinely is that simple — no extra billing, no extra dashboard.

How many warning emails will I get?

Just one — a single email once the certificate's remaining validity crosses the threshold you set, not a recurring reminder you'll eventually start ignoring. If you'd rather have more runway, raise the threshold; the alert still only fires once per approaching expiry, so it stays something you actually pay attention to. If the threshold you originally picked turns out to be wrong, adjusting it takes a few seconds. That restraint is what keeps the warning meaningful instead of routine.

Does it renew the certificate for me?

No — it only warns you before the certificate expires. Renewal still happens wherever you currently manage it, whether that's an automated tool like Let's Encrypt's certbot or a manual process through your certificate authority; this feature exists to make sure that renewal happens on your schedule instead of on a customer's. Think of it as a second set of eyes on a deadline you already own, not a replacement for owning it. It's a nudge at the right moment, not a substitute for having a renewal process at all.

Get Started

SSL certificate expiry. Free, starting now.

Start Free →