Monitor your SSL Certificates
Learn when certs are about to expire so you can deal with them, annoy the person who needs to know, or go fix the system that should have handled it for you, again. See the status of your domain certs in the dashboard. Paid accounts get daily status reports sent to their Email inbox.
- Too many certs to manage?
- Random certs periodically fail to renew yet renew fine when you shell in to manually re-run the command this month?
- Does a cert always somehow magically fall under the radar until the day your boss wants to pitch someone a small side project you forgot about?
Let this tool help perform your sanity checks, especially since Let's Encrypt plans to reduce the maximum certificate lifespan all the way down to a maximum of 45 days eventually.
Dashboard
The dashboard allows management of the domain library and viewing the status of the certs.
I'm rather fond of the Reverse DNS sort myself as I run a lot of projects off subdomains.
Domains (By Status)
Daily Reports
Daily reports are dispatched to your inbox so you don't have to visit just to check up.
Plans & Pricing
| Free | Tier 1 | Tier 2 | |
|---|---|---|---|
| Price | $0/mo | $4/mo | $10/mo |
| Domains | 10 | 20 | 60 |
| Daily Email |
Roadmap
- JSON API (Mid 2026) (Paid Plans Only)
- Your system can ask this system questions.
- JSON Webhooks (Mid 2026) (Paid Plans Only)
- When our system notices a change in a cert status, we ping your endpoint to notify you.
- Domain Registrar Info (Late 2026) (Paid Plans Only)
- Remind your boss to renew that domain before you really have a bad day. To do this correctly without pissing off registrars is important - I am not going to build a spam farm of 4000 servers to scam the WHOIS system.
ashbox.sh (acme.sh box)
On the other end of the problem is actually getting the certs issued and keeping them renewed. Ashbox is a lightweight Bash Script only wrapper for the acme.sh SSL tool to make certs a little easier to deal with in a contained, portable fashion.
When using DNS with API support issuing a certificate is as easy as this...
$ ashbox.sh issue opsat.net --digitalocean
Or a locally sourced webroot...
$ ashbox.sh issue opsat.net --webroot /opt/web-opsat/www
Certs are kept up to date via a cron task setup by the acme.sh. It also provides helpers to generate configuration settings for things like Apache that can be copy pasted into config files.