Setting up your expiration alerts

An alert is only useful if it arrives at the right time, in the right place and to the right person. Everything is configured from the Notifications page of your account.

Choose when to be notified

For each channel, select one or more reminders: 30, 15, 7, 5, 3 or 1 day before expiry. By default, email is enabled with reminders at 30, 15, 7, 3 and 1 day.

A few guidelines:

• Commercial certificate (manual renewal): keep 30 and 15 days. Placing an order and completing validation can take several days.
• Let's Encrypt or automatic renewal: a 15-day reminder is often enough. The certificate is normally renewed about 30 days before expiry. If the alert arrives anyway, it means the automation failed.
• Always keep a short reminder (3 days or 1 day) as a last safety net.

Available channels

Each channel has its own reminder days. For example, you can get an email at 30 days and a Slack message at 7 days.

Email

Enter the recipient address: by default it's your account's address, but a team address like ops@ or tech@ is often more reliable. Add the sender to your contacts to keep alerts out of the spam folder.

Slack

1. Go to api.slack.com/apps and create an app (From scratch) in your workspace.
2. Under Incoming Webhooks, turn on webhooks, then click Add New Webhook to Workspace.
3. Choose the channel, for example #ssl-alerts, and copy the URL that starts with https://hooks.slack.com/services/….
4. Paste it into the Slack card, choose your reminder days and save.

Telegram

1. In Telegram, open a chat with @BotFather and send /newbot. Follow the instructions: you'll get a token like 123456789:ABC….
2. Open a chat with your new bot and send it a message, any message.
3. Open https://api.telegram.org/bot<your_token>/getUpdates in a browser: the chat.id value is your chat ID.
4. Paste the token and the chat ID into the Telegram card.

To receive alerts in a group, add the bot to the group and use the group's ID: it starts with a minus sign.

Webhook (Agency plan)

To connect alerts to your own tools (monitoring, ticketing, Zapier, n8n…), enter a URL: it receives a JSON POST request for every alert.

{
  "event": "ssl.certificate.expiring",
  "timestamp": "2026-12-01T12:00:00Z",
  "data": {
    "domain": "example.com",
    "expiry_date": "2026-12-31T23:59:59Z",
    "days_until_expiry": 30,
    "is_urgent": false
  },
  "signature": "…"
}

If you set a secret key, the signature field contains an HMAC-SHA256 of the rest of the message. Verify it on your server to make sure the request really comes from us. A PHP example is provided in the Webhook card.

Who receives alerts?

The account owner always receives everything. You can add extra recipients at the bottom of the Notifications page. They get alerts by email, without needing an account.

• Free: just you.
• Pro: up to 5 people in total. Ideal for a small team: the developer, the on-call person, the tech lead.
• Agency: unlimited recipients and, most importantly, domain selection per recipient. Each client only gets alerts for their own sites, while you keep the full picture.

To limit a recipient to certain domains (Agency plan), click Choose domains next to their address, then select Only some domains.

Reports and other alerts

• Weekly report: every Monday, the certificates expiring in the coming weeks.
• Monthly report: at the start of each month, the full status of all your domains.
• Status change: an alert as soon as a certificate becomes invalid (expired, wrong name, broken chain), then again when it becomes valid after a fix. Enabled by default.

Don't forget to click Save preferences at the bottom of the page.

Test your setup

The easiest way: add a domain whose certificate expires soon, or check the following Monday's report. If a Slack or Telegram message doesn't arrive, first check the webhook URL or the token and chat ID pair. These are by far the most common mistakes.