SiroPing
Open App
Community · Pro · Business

SSL Monitoring

Detect expiring or invalid TLS certificates before your clients do.

SSL Monitoring

SiroPing checks the TLS certificate of every HTTPS monitor and warns you before it expires — so a certificate renewal never becomes an outage.

How it works

SSL is a capability of the HTTP monitor, not a separate monitor type. Every HTTPS check:

  • Validates the certificate chain and hostname.
  • Reads the expiry date.
  • Flags a certificate that is about to expire as a Warning (with the days left).

Configuration

  1. Create/Edit an HTTP monitor.
  2. Enable SSL monitoring and set the days threshold (e.g. alert when ≤ 14 days remain).
  3. Save.

A certificate entering the warning window shows its remaining days on the monitor row and in reports, and (optionally) triggers an alert channel.

What you get

  • Days-to-expiry visible per monitor.
  • SSL health included in Reports (uptime/downtime summary per project).
  • Warnings feed the same incident pipeline as HTTP failures (dedup + cooldown).
NOTE

SSL checks need a reachable HTTPS endpoint. Monitors that only use plain HTTP can't be

SSL-checked — use HTTPS URLs.

What SiroPing does NOT do

  • It does not install or renew certificates (use certbot for that).
  • It does not store private keys.

See HTTP Monitoring for the rest of the HTTP monitor options.

Was this page helpful?