Warned in days, not minutes
Set the threshold at 30 days, 14 or 7, and the check turns degraded while there is still time to renew. It only goes down once the certificate is actually invalid.
SSL Monitoring
A certificate expiring is the one failure you always get warning about, as long as something is watching for it.
Free plan, no card needed.
SSL · api.acme.com:443
Renew before October 31
Issued by Let’s Encrypt R3 · checked from 5 regions
Set the threshold at 30 days, 14 or 7, and the check turns degraded while there is still time to renew. It only goes down once the certificate is actually invalid.
Trust, hostname match, and chain completeness are all verified. A certificate that is technically valid but missing an intermediate still breaks clients, and still gets flagged.
Point a check at any host and port. API endpoints, admin subdomains, mail servers, and the internal service that nobody remembered had its own certificate.
$ statuscheck check api.acme.com/health --region fra { "location": "frankfurt", "type": "http", "target": "https://api.acme.com/health", "up": true, "status": 200, "dns": 0.687, "tcp": 9.433, "tlsHandshake": 30.141, "firstByte": 18.313, "download": 0.11, "total": 59.059, "redirects": 0, "assertion": true, "sslExpiration": 57, "sslNotAfter": "2026-10-31T21:41:26Z", "date": "2026-09-04T12:41:07.617Z"} The specifics
Written out in full, because “monitoring” means something different at every vendor.
Every part of StatusCheck is on every plan. These are the pieces this one talks to most.
The free plan needs no card. Add a monitor, pick the regions, and see the first check in under a minute.