SSL certificate expiry notifications & alerts
CertFleet notifies you before a certificate expires — at 30, 14, 7 and 1 day — on the channel your team actually watches. Each threshold fires once, and the countdown resets on its own after a renewal.
Notification settings are per domain: tick the thresholds you want, add the channels that should receive them.
An SSL certificate that expires silently takes your site, API or internal tool offline the moment a client connects: browsers show a full-page security error, API clients refuse the handshake. Most teams find out from a customer. An expiry notification exists to create lead time — enough warning that the renewal goes through normal change management instead of a midnight page.
Why staged thresholds: 30, 14, 7 and 1 day
Each threshold maps to a different action. At 30 days: check that auto-renewal is configured, that the ACME challenge will succeed and that the payment method of a commercial CA is valid. Most ACME clients renew Let's Encrypt certificates at 30 days left, so a 30-day notification usually means renewal has not run. At 14 days: renew manually — there is still time for a normal change. At 7 days: escalate and renew today. At 1 day: emergency, production goes down within hours. A single notification on expiry day leaves only that last, worst option.
SSL notification settings, per certificate
Notification settings live on each monitored domain, not on the account, because certificates do not all carry the same risk:
- Thresholds — choose any combination of 30, 14, 7 and 1 day before expiry. A staging certificate can notify at 7 days only; the certificate in front of your checkout notifies at every step.
- Channels — each domain has its own list of recipients and channels, each of which can be switched off without being deleted.
- Maintenance windows — mute notifications for a domain during a planned certificate swap or migration, so nobody is paged for work in progress.
- Check frequency — the served certificate is checked every hour on the free plan and down to every minute on paid plans.
Notification channels
| Channel | Plan | How it is delivered |
|---|---|---|
| Free | Pre-filled with your account address on every new domain. | |
| Slack | Free | Incoming-webhook URL — route to a dedicated #cert-alerts channel. |
| Microsoft Teams | Free | Incoming-webhook card in the channel your ops team watches. |
| Discord | Free | Embed message via a Discord webhook. |
| PagerDuty | Free | Events API v2 with a dedup key per domain and threshold. |
| Opsgenie | Free | P1 alert with an alias per domain and threshold. |
| Webhook (JSON) | Starter | HMAC-SHA256 signed payload for any receiver or automation. |
| SMS | Starter | For the 7-day and 1-day thresholds nobody can miss. |
One notification per threshold — never a storm
A monitor that alerts on every check — every five minutes, "your cert expires in 3 days" — teaches on-call engineers to ignore it. CertFleet records every notification it sends against the domain, the threshold, the channel and the certificate's expiry date. Crossing the 14-day threshold sends one notification per channel; the next one comes at 7 days. Because the certificate is identified by its expiry date, a renewal starts a fresh countdown on its own: nobody has to acknowledge or reset anything.
Is the expiring certificate the one being served?
The most common certificate outage is not a missing renewal but a renewal that was never deployed: the CA issued a new certificate, the load balancer still serves the old one. CertFleet reads the certificate from a live TLS handshake on the hostname and port you monitor, so the notification reflects what clients actually receive. If renewal ran and was deployed, the notifications stop by themselves; if it was not deployed, they keep coming — and that is the alert that matters.
Signed webhook payload
On Starter and above, a webhook sends the same JSON structure for every threshold — only
threshold and daysRemaining change — so you can route 30-day notifications to a
ticket queue and 7-day or 1-day ones to an incident. The raw body is signed with HMAC-SHA256 in the
x-signature header so your receiver can verify the request came from CertFleet.
POST https://your-receiver.example.com/certfleet
content-type: application/json
x-signature: <HMAC-SHA256 of the raw body>
{
"type": "ssl.expiring",
"hostname": "api.example.com",
"port": 443,
"daysRemaining": 7,
"threshold": 7,
"notAfter": "2026-12-01T23:59:59.000Z",
"issuer": "R11",
"status": "expiring"
} New-certificate alerts from Certificate Transparency
Expiry notifications tell you a certificate is about to lapse. Certificate Transparency alerts (Starter and above) tell you a new certificate was issued for one of your domains — by your own renewal, or by someone else. An unexpected issuance is a security signal: it can mean a compromised DNS account or a mis-issuing CA, and seeing it early is what lets you request revocation.
SSL certificate notification FAQ
How many days before expiry should I get an SSL certificate notification?
Use staged notifications rather than a single one: 30 days to check that auto-renewal is set up, 14 days to renew manually if it has not run, 7 days to escalate, and 1 day as the emergency alert. Let's Encrypt certificates last 90 days and most ACME clients renew at 30 days left, so a 30-day notification that keeps firing means renewal is broken.
Can I choose which expiry notifications I receive?
Yes. In CertFleet's alert settings you pick the thresholds (30, 14, 7 and/or 1 day before expiry) and the channels separately for each domain. A staging certificate can notify only at 7 days by email, while the production API certificate notifies at every threshold on Slack and PagerDuty.
Will I get an alert on every check?
No. Each combination of domain, threshold, channel and certificate fires once. The certificate is identified by its expiry date, so after a renewal the thresholds reset automatically for the new certificate without any manual acknowledgement.
Which notification channels are free?
Email, Slack, Microsoft Teams, Discord, PagerDuty and Opsgenie are available on the free plan (10 certificates, hourly checks). Signed webhooks and SMS start with the Starter plan at $15/month.
Can I pause SSL alerts during planned maintenance?
Yes. Maintenance windows suppress notifications for a domain while the window is active, so a planned certificate swap or server migration does not page anyone.
Does the notification reflect the certificate actually served?
Yes. CertFleet reads the certificate from a live TLS handshake on the port you monitor, not from your CA account or renewal logs. If a renewal ran but was never deployed, the served certificate is still the old one and the notification keeps firing — which is exactly the failure you need to see.
Certificates sorted by days remaining — each EXPIRING or EXPIRED badge matches a notification already sent on the configured channels.
10 certificates · hourly checks · 30/14/7/1-day notifications · email, Slack, Teams, Discord, PagerDuty, Opsgenie.
25 certificates · 1-minute checks · signed webhooks · SMS · CT new-certificate alerts · REST API.
100 certificates · private certificates · team roles · 3 users.
Add a domain, pick your thresholds and channels — notifications are live in under a minute. Free for 10 certificates, no credit card.
Built in France · Architecture & RGPD · All plans