Skip to content

SSL Certificate Monitoring

SSL/TLS certificate checks run automatically on every HTTPS API check. There is no separate SSL monitor to create or configure: as soon as an API check targets an https:// URL, LoadFocus inspects the certificate on every run.

For an overview of the feature and its plans, see SSL certificate monitoring. To check one certificate right now, use the free SSL Checker.

That means certificate coverage comes for free with the monitoring you already have. Every scheduled run refreshes the certificate data. Multistep, browser, TCP, DNS and heartbeat checks do not carry a certificate check.

Expiry warnings are sent at 14, 7, 3 and 0 days before the certificate expires. They go through the alert channels enabled on the check. If none of them delivers the warning, it is emailed to the email address on the check.

The 14-day first warning is deliberate. Healthy Let's Encrypt setups auto-renew at about 30 days remaining, so a 30-day warning would fire on every normal rotation and train you to ignore it. If your certificate reaches 14 days remaining, renewal has genuinely stalled and it is time to act.

You get one warning per threshold per certificate, even when the check runs from many regions, so a multi-region check does not multiply the emails.

Each check captures:

  • Validity of the certificate.
  • Issuer and subject.
  • Valid-from and valid-to dates.
  • Days remaining until expiry.

Warnings are on by default. To switch them off for one check, clear an SSL certificate expires soon under the notification options of that check. A check with Skip SSL enabled does not capture certificate data, so it sends no expiry warnings.

Warnings re-arm automatically when the certificate is renewed. As soon as the expiry date changes, the warning ladder resets, so you get a fresh set of 14, 7, 3 and 0 day warnings for each certificate lifetime. No manual reset or acknowledgement is needed.

For a one-off instant certificate inspection, without creating any check, use the free SSL Checker. It is handy for verifying a renewal right after you deploy it.

Read more about continuous certificate coverage on the SSL Monitoring page. To set up the HTTPS checks that carry these certificate checks, see How to Create a New API Check.