Updated 2026-06-17
Certificate expiry is one of the most common causes of a "surprise" outage — the site is otherwise fine, but the certificate quietly lapsed. Status tracks this separately from plain uptime.
How it works
Every https:// HTTP check verifies the
certificate as part of its normal request (verifyTls). You can also add a
standalone SSL check against a host and port (443 by default) purely to
track certificate health independent of any HTTP monitoring.
Expiry warnings
Rather than a single up/down state, certificate expiry is tracked against a set of thresholds — by default 30, 14, 7, and 1 days before expiry. Status sends a warning once per threshold as the expiry date approaches, so you get advance notice instead of finding out when the certificate has already lapsed. See SSL and domain expiry warnings for how these warnings behave and how to adjust the thresholds.
When to use it
Any HTTPS endpoint you care about, especially certificates that renew manually rather than through automation — Status gives you a heads-up well ahead of the deadline instead of an unexpected TLS error.