7 comments

[ 2.9 ms ] story [ 25.9 ms ] thread
Ever had your site or API go down because of an expired SSL certificate? It happened to us, and the fix was surprisingly painful. So we built SSL Guardian, a simple, automated SSL/TLS monitoring platform.

What it does:

- Tracks SSL/TLS certificates across all your domains and services - Sends timely alerts (Email, Slack, Webhooks) - Performs chain validation and health checks - Quick setup, zero vendor lock-in

Why? Because one missed renewal can mean hours of downtime, lost trust, and customer churn.

We’re offering free access for early testers (Pro plan for 12 months) in exchange for feedback.

Try SSL Guardian

Would love your thoughts on: - How do you handle SSL/TLS monitoring today? - Biggest pain points you’ve hit? - Features you’d want in a tool like this?

Unrelated to the marketing attempt here but it should be noted that the CA Browser forum voted to drastically shorten certificate lifetimes. Look for 200 day expiration cycles starting next year, 100 days in 2027, and 47 days in 2029.
Don't the current monitor solutions do this? Nagios was doing this in 2005. A quick search shows dozens of providers. Hard to see the UVP here.
I use Caddy, and it handles cert renewal automatically for me, so I've never had to deal with SSL expiry issues. Pretty handy!
Traefik does certbot autorenewals, really neat
Or just use traefik or caddy or certbot.

Oncidentally, I wonder how the SSL companies still run when we have the wonderful LE or ZeroSSL. A cert is a free utility today and not worth overthinking.

In the cases where certificates cannot be automatically issued and renewed, what does this offer that a calendar reminder cannot do?

Certs have built in lifetimes in a standardized format, reading a certs expiration date, setting a calendar reminder X number of days before then and inviting the team responsible for that infrastructure certainly that doesn’t need another tool? Just a check box in the process?