Know before a visitor sees a browser warning
Every HTTPS site's certificate is checked on each monitoring cycle — expiry date and validity — and flagged 30 days before it lapses.
Reads the real certificate, not a guess
A direct TLS connection is opened to your server and the certificate's actual expiry date is read — the same data your browser checks — then compared against today's date.
- Automatic for every HTTPS site, no extra setup
- Flagged 30 days before expiry, giving real time to renew
- Validity confirmed on every check, not just the expiry date
The details
- Runs alongside the regular uptime check, same cycle
- Shown on the site's card and detail page as days remaining
- Does not require re-adding the site if a certificate is renewed — it just clears
Questions people ask
No — it's automatic for any site added with an https:// URL.
Then you'll simply never see the warning — it only fires if the real expiry date actually gets within 30 days.
Think of it as a second, independent check — provider emails can get missed, filtered, or sent to the wrong inbox.
Check a real certificate.
Bring an HTTPS URL — we'll show you exactly what the expiry check returns.