Early warnings
Checks fail when a certificate is within 30 days of expiry, which leaves time for renewal and change approval.
SSL monitoring
Expired certificates cause some of the most avoidable outages. Get warned well before any customer-facing certificate lapses.
Direct answer
SSL certificate monitoring connects to each hostname, reads the certificate and warns before it expires. PingAlert SSL checks flag certificates within 30 days of expiry and alert through the same channels as your uptime checks, so renewals happen on a weekday, not during an incident.
Checks fail when a certificate is within 30 days of expiry, which leaves time for renewal and change approval.
Monitor API, CDN, image and checkout subdomains, not only the main site, since any of them can break a page.
A failed TLS handshake or missing certificate alerts immediately.
SSL checks sit next to uptime, API, multi-step and DNS checks with the same alert routing and incidents.
Track certificates per client workspace so renewals for each client are visible to the right team.
Renew before code freezes and holiday peaks; expiry warnings make the renewal a planned change.
How it works
List every hostname customers and integrations touch.
Create a check per hostname and route alerts to the owning team.
Note who renews each certificate and how.
Treat the 30-day warning as the renewal deadline.
Direct answers
SSL checks fail and alert when a certificate is within 30 days of expiry.
Yes. Certificates are per hostname or SAN set, so add a check for each customer-facing hostname you depend on.
No. It covers certificate health; combine it with uptime, API and DNS checks for full coverage.