An expired certificate takes your site down on a date known months in advance. Cronitorex watches every certificate you list, inspects the whole chain and reminds you before renewal day, not after.
Each monitor has a warning threshold and an alert threshold, for example 14 and 7 days. The warning means schedule the renewal; the alert means do it today.
Cronitorex inspects every certificate in the chain, not only the leaf. An expiring intermediate or a name mismatch anywhere in the chain fails the check just like an expired leaf would.
leaf CN=checkout.example.com 38d intermediate CN=R11 203d root CN=ISRG Root X1 1580d chain complete · hostname ok thresholds warn 14d · alert 7d
Agencies renew certificates for domains they do not host, issued by providers they did not pick, on dates nobody wrote down. One expired client domain costs more than a year of monitoring.
Add every client domain, tag it per client and route alerts to Telegram, Discord or Slack, where your team already works. The dashboard sorts the portfolio by days to expiry, so renewal work plans itself.
Add the domain, set two thresholds, done. No DNS records, no verification files, no code changes on your side.
From then on Cronitorex checks the certificate on schedule and walks it down the timeline: quiet while the date is far, a warning when it gets close, an alert when it gets urgent.
At least once a day per monitor. After renewing you can trigger a check manually to clear the warning immediately instead of waiting for the next scheduled run.
Yes. Wildcard and SAN certificates are inspected like any other. Add each host name you care about as its own monitor and each one is validated against the certificate it actually serves.
Yes, one certificate monitor is one monitor. The Free plan includes 30 monitors, enough for a serious portfolio of domains, and you can mix cron, HTTP and SSL monitors freely.
Sign up, get an API key, paste the curl into your cron. That's it.