Hyperping watches the certificate on your uptime monitors. CertPost watches everything around it too.
Verified 19 Aug 2026
Hyperping is a clean uptime and status-page tool, and its SSL check is better than most bundled ones: it detects an incomplete chain and a Common Name that does not match, not just the expiry date. If you use Hyperping for status pages, its SSL check is a fair start.
It is still a sub-check that rides on your uptime monitors, capped by your plan's monitor count, and it stops at expiry, chain, and name matching. The failure modes it does not cover are the ones that need a certificate-first tool:
• Certificate Transparency — an alert the same day a certificate is issued for your domain, whether or not you issued it.
• Domain-registration expiry. The certificate can be fine while the domain name itself lapses; they are different clocks.
• DNS record drift — the A or MX record quietly changing under a name that still resolves.
• Mail and admin ports. SMTP 465/587, IMAPS 993, panels on 8443 each hold a certificate an HTTPS monitor never opens.
CertPost does all of that, plus the chain, hostname, SAN, and fingerprint-change checks Hyperping's SSL check already does — every one from a real TLS handshake over IPv4 and IPv6. Three certificates are free forever; paid is a flat $29/month for unlimited certificates, rather than counting against a monitor cap.
Run Hyperping for uptime and status pages. Run CertPost for the certificate, the domain, and the DNS around it.
Pairing them:
1. Keep Hyperping monitoring uptime and hosting your public status page.
2. Sign up for CertPost free and paste every TLS hostname, mail and admin ports included.
3. Route both to the same channel so an incident and a certificate warning land in the same place.
Import your domain list in 2 minutes — 3 certificates free, no card.
Start free