CertWatch documentation
CertWatch catches the certificate renewal that didn't happen. Whether your certificates renew automatically or by hand, it checks the certificates your servers actually present and alerts you when a renewal is late, so a failed renewal job, a forgotten manual renewal, or a lapsing domain registration shows up before it becomes an outage. It reads the certificate at any host:port you give it, not just web servers, so it covers APIs, load balancers, mail servers on ports 465, 587 and 993, PostgreSQL on 5432, or any other service that accepts a direct TLS connection. It is built for small engineering teams, consultants, and agencies.
Start with the problem
Certificates and domain registrations fail quietly until a client, browser, mail server, or customer is the first one to notice. Why monitor? explains the failure modes and what external monitoring can and cannot prove. If you are diagnosing one target right now, start with the free tools instead.
What CertWatch monitors
Two related but separate things, both included on every plan:
-
TLS endpoints — a
host:portyou register. CertWatch dials it on a schedule, learns when its certificate renews, and alerts when a renewal is late or the certificate is broken (an incomplete chain, a name it does not cover, an expiry). A certificate that renews on schedule sends nothing. -
Domains — a registrable domain name (e.g.
example.com). CertWatch checks its own expiry and registration signals (transfer lock, DNSSEC, exposed registrant contact) via RDAP, independent of any certificate served on it.
Where to start
- Why monitor? — the operational case for certificate and domain monitoring.
- Free tools — check a live endpoint, decode a certificate, or inspect it locally.
- Setup — creating an account and adding your first endpoint or domain.
- API — the session-based HTTP/JSON API behind the app.
- Monitoring behavior — check intervals, statuses and reasons, when a renewal is late, and check-result retention.
- Supported TLDs — which TLDs CertWatch can read a registration expiry date for.
- Dashboard and Monitors — the Dashboard, Monitors and the monitor card, Metrics, the bell, and the Getting started checklist.
- History — what changed on your monitors, and how to read an entry.
- Alerts — when alerts are sent, Acknowledge, channels, Alert history, and what a real alert looks like.
- Troubleshooting — interpret failures and decide what to do next.
- Old certificate after renewal — the renewal worked and clients still get the old certificate.
- Incomplete certificate chain — fix a missing intermediate.
- Let's Encrypt expiry emails — what to set up now they have ended.
- Certbot renewal failed — find the cause and hear about the next one.
- Billing — plans, limits, and how upgrades/downgrades work.
- Deployment — how CertWatch itself is hosted and released.
- Trust & security — data handling and how we monitor our own monitor.