If you're a developer, you've probably met this one: you open a site or call an API and get a full-page browser warning or a certificate error. Nothing in the code changed. The certificate expired.
When that happens, the site, API or app behind it stops working at once. Mobile apps can't connect and integrations fail. Expired certificates are one of the most common causes of avoidable outages, and they catch out large companies as often as small ones.
Automated renewal helps, but a renewal job running is not the same as the right certificate being served. CertHalo, built and run by IncubXperts, checks what each server actually presents to the internet and warns teams before a certificate expires or quietly breaks. It was announced on 21 October 2026 and replaces our earlier tool, SSL Expiry Tracker.
SSL/TLS certificates in brief
An SSL/TLS certificate ties a website's identity to a cryptographic key, so a browser or app can confirm it has reached the right site and set up an encrypted connection. TLS is the current protocol and SSL is its older name. Every certificate has an expiry date, after which browsers and apps stop trusting it.
Where automated renewal still leaves gaps
Renewal can fail without anyone noticing: an expired API token, a changed DNS record, a new firewall rule or a rebuilt server can stop the job. A certificate can also renew and never go live, with the web server, load balancer or CDN still serving the old one. And vendor portals, appliances, older servers and customer-managed domains still depend on someone remembering the date, while Let's Encrypt ended its expiry reminder emails in June 2025.
The pressure is rising too. The maximum certificate lifetime fell to 200 days in March 2026 and falls to 100 days in March 2027 and 47 days in March 2029. More renewals means more chances for one to fail.
How CertHalo checks certificates from the outside
CertHalo doesn't look at the renewal job or the certificate store. It checks what each server actually shows the internet, so it catches all of the cases above, whichever tool did the renewal. There is nothing to install, and it works with any website or server, any hosting provider and any certificate authority, including custom ports.
It runs alongside your existing renewal setup, which doesn't have to change. If the renewal stops, a new certificate isn't deployed or a CDN keeps serving the old one, you get an alert while there is still time to act, instead of an outage. It also covers the assets automation never reached, such as appliances, vendor portals and customer-managed domains.
What CertHalo monitors and how it alerts your team
Expiry reminders go out 60, 30, 14, 7, 3 and 1 day before a certificate expires. Paid plans can choose their own reminder days.
Change alerts fire the moment a certificate is renewed, changes issuer, stops matching its hostname, loses its trusted chain, is revoked or becomes unreachable. Because it checks the server itself, the expiry countdown continues even if a renewed certificate was never deployed.
A health check grades each certificate from A to F. It looks at the certificate chain, the hostname, revocation status (OCSP and CRL), key strength and TLS versions. OCSP checks the status of a single certificate in real time, while a CRL is a list of revoked certificates published by the certificate authority.
Alerts go to email, and on paid plans to Slack or Microsoft Teams channels. Pro and Business plans add shared team workspaces with Owner, Admin and Member roles.
Who gets the most from CertHalo
IT and DevOps teams responsible for many websites and services can monitor all of them. Agencies and service providers can watch the sites they look after for clients. Product teams whose APIs and mobile apps depend on a valid certificate get a warning before a failure reaches users. Small businesses without a dedicated IT person get reminders without running anything, and anyone with a personal site or side project can use the free plan.
CertHalo plans and how to get started
| Plan | Certificates | Checked every | Price |
Free | 3 | Day | $0 |
Starter | 25 | 6 hours | $3 a month or $30 a year |
Pro (up to 5 people) | 100 | 6 hours | $9 a month or $90 a year |
Business (up to 20 people) | 300 | 6 hours | $29 a month or $290 a year |
IncubXperts customers get Pro or Business at no extra cost, and their account lead can arrange access.
To try it, run a one-off check at certhalo.com without an account, or sign up at certhalo.com/signup and add your first three certificates. New features are listed at certhalo.com/changelog.
Questions about CertHalo or how it fits your setup? Contact the IncubXperts team.
Conclusion
Automated renewal handles most certificates, but a certificate that renewed is not always a certificate being served. CertHalo checks what each server presents to the internet, so failed renewals, undeployed certificates and assets nobody automated show up as alerts before they become outages. With maximum certificate lifetimes falling to 47 days by March 2029, that outside-in check matters more with every renewal cycle. You can start free at certhalo.com/signup or run a one-off check at certhalo.com/ssl-checker.

