Back to blog
FILE 0xF4·CERTWATCH PRO NOW LETS YOU SET CUSTOM ALERT THRESHOLDS PER D

CertWatch Pro now lets you set custom alert thresholds per domain

June 12, 2026 · certwatch, saas, python, monitoring, devops

The default CertWatch alert ladder — 30, 14, 7, and 1 day before expiry — is a reasonable default for most domains. But it's not right for every domain.

A customer-facing wildcard cert might need a 60-day heads-up because the renewal process involves an external CA with a two-week lead time. An internal test domain might not need any reminder until 3 days out. A domain you manage for a client under a specific SLA might need weekly reminders from 45 days out.

CertWatch Pro now lets you set a custom alert ladder per domain.


How it works

PATCH /domains/example.com
{"alert_days": [60, 30, 14, 7, 1]}

That's it. CertWatch stores the alert_days list in the domain record and uses it instead of the global default. The daily cron reads the custom list and fires alerts at exactly those intervals.

To reset a domain back to the global default:

DELETE /domains/example.com/thresholds

Validation rules

If you pass unsorted values (like [7, 60, 30, 1]), CertWatch sorts them for you before saving.


Idempotency still works

The existing idempotency guarantee applies to custom thresholds too. If CertWatch has already fired a d60 alert for a domain today, it won't fire again until tomorrow's run — even if you update the threshold mid-day. The same last_alert_at_<label> stamp mechanism that prevents duplicate emails at d30 or d7 works exactly the same way for custom rungs.


Dashboard visibility

GET /domains now includes alert_days in the response for each domain where a custom ladder is set. Domains on the global default don't include the field — so your API consumer can tell at a glance which domains have been customized.


Who should use this


CertWatch is on the Pro plan at $15/mo. Per-domain custom thresholds are a Pro feature.