SSL monitoring for web development agencies

When an agency launches a client site, the certificate becomes the agency’s problem for as long as the relationship lasts. The client does not think about TLS; they think about the agency that built the site. So when a certificate expires or a chain breaks, the call comes to you, usually on a weekend, usually as an emergency.

Most of these failures are invisible until they are urgent. A certificate renews on disk but the server never reloads it. An intermediate above it lapses while the leaf still looks fine. A re-issue drops a subdomain. None of it shows up in an uptime check, and none of it is something you can reasonably watch by hand across thirty or a hundred client sites.

Watch every site you have ever launched from one place. Paste the whole list once — CertPost auto-discovers the certificate on each host — and every certificate is then read from a real handshake on a schedule: chain, hostname and SAN, expiry, and unexpected changes, across the mail and admin ports too, plus the domain registration and DNS around it. When something is heading for a break, the alert lands in your inbox or a team channel before the client notices, which turns the Saturday emergency into a Tuesday task.

Because the plan is flat — $29/month on Team, $79/month on Agency — adding a client costs nothing extra, so there is no reason to leave a launched site unwatched. That is the difference between monitoring you bill into a care plan and monitoring you avoid because it is priced per domain.