The Hyperping alternative with real SSL monitoring

Hyperping does uptime monitoring and status pages nicely — a generous free tier (20 monitors, one status page, no time limit), multi-region checks, synthetic browser checks, and public status pages that are genuinely one of its strengths. CertFleet does not offer hosted status pages, so if a public status page is your primary need, Hyperping is the better fit.

Where the two diverge is SSL. Hyperping's SSL monitoring is an expiry check — it alerts roughly 30 days before a certificate is due to renew. That covers the simple case but misses the failure modes CertFleet is built for: a certificate renewed at the CA but never deployed to the server (the old one keeps serving until it lapses), and a new certificate issued for your domain by a third party. CertFleet performs a real TLS handshake on every check, reads the X.509 certificate your server actually presents, compares it against the last known one, and queries Certificate Transparency logs to alert the instant a new certificate appears.

On uptime, CertFleet matches the essentials: configurable HTTP method, full URL path, expected status codes, keyword match in the response body, pause/resume, check history, and uptime percentage. Alerts go to email, Slack, HMAC-signed webhooks and SMS, with signed webhooks included at the $15/mo entry tier so your receiver can verify payload integrity. A no-login SSL checker handles one-off certificate diagnostics without an account.

Choose Hyperping if polished public status pages are central to what you're building. Choose CertFleet if you want serious SSL certificate lifecycle monitoring — live probing, CT-log alerts, staged 30/14/7/1-day thresholds, signed webhooks — sitting right next to your uptime checks in a single tool.