Improving the SSL certificate expiration monitoring

· Updated
SSL digital image


We just updated our SSL certificate expiration monitoring. This update gives you more control over where and when you want to receive alerts.

Before today, certificate alerts were set as part of "Alert Settings" tab, either globally or using specific settings for checks & check groups. This wasn't all that flexible and more granular control was already on our public roadmap.

Today's update improves this by moving the SSL certificate expiration to "Alert Channels" —  the same place where you set failure, degradation and success alerts.

This is how SSL monitoring works:

set SSL expiry alerts per channel

  1. You pick the alert channels on which you want to receive the expiration alerts. Finally! 🤯
  2. You can get alerted for multiple thresholds, for example 30 days and 3 days before the expiration date by setting multiple alerts channels.

Already existing SSL alerts will keep working for 3 months until we deprecate them. Don't worry, we will bug you via email and with a notice in the app.

Your current SSL alerting settings under "Alert Settings" (either account-wide or specific ones to check/group) will be deprecated and will stop working in 3 months on November 13th, 2020.

If you have any questions or feedback, we’ll love to hear about it. Just use the chat bubble in the lower right corner.

Try Checkly

Catch it before your users do

Run Playwright and API checks against production every minute, from locations around the world. Your checks live in your repo and deploy with your code.

Free plan. No credit card.

# scaffold a project with example checks

npm create checkly@latest

# run them from our global locations

npx checkly test

# turn them into production monitors

npx checkly deploy

Related Articles