Healthchecks

SSL / TLS Certificate Monitoring

Check that a certificate is trusted, matches the host and isn't about to expire.

Overview

SSL/TLS certificate monitoring makes sure your certificates are valid and not close to expiring. Expired or untrusted certificates cause browser warnings, failed API connections, and broken trust with your users. Uptimy checks the certificate on every run and shows it as Degraded while there is still time to renew.

Each run also records details about your TLS setup: the TLS version, cipher suite, certificate chain and issuer.

Configuration

ParameterDescriptionDefault
HostThe hostname to check. The certificate must be valid for this nameRequired
PortThe port to connect to for the TLS handshake443
Expiry warning (days)How many days before expiry the check turns Degraded. Under Advanced settings30

Degraded Before Down

Inside the warning window the check is Degraded, not Down. Degraded alerts you only if Alert when degraded is on, on the check's Alerting tab: it then opens a medium incident and runs your workflows. Degraded time doesn't count as downtime in uptime or SLA reports, but status pages that show the check show it as Degraded too. With 7 or fewer days left the check is Down. A warning of fewer than 7 days moves Down to that many days, with no Degraded stretch, so certificates that last only a few days can still be monitored.

How It Works

When an SSL health check runs, Uptimy completes a TLS handshake with the target host and verifies the certificate as a client would: the chain must lead to a public certificate authority, and the certificate must be valid for the host. The check is Down when:

  1. The TLS handshake fails
  2. The certificate isn't trusted, for example a self-signed certificate or one from a private certificate authority
  3. The certificate doesn't match the host
  4. The certificate has expired or isn't valid yet
  5. 7 or fewer days remain before it expires (or fewer, if the warning is set below 7)

Otherwise it is Degraded while the days left are within Expiry warning (days), and Up when more days are left. Revocation isn't checked.

A failed run says why, for example certificate is self-signed, certificate is valid for a.com, www.a.com, not b.com, certificate is issued by an untrusted authority, or certificate expires in 5 days (2026-11-19). A Degraded run carries a warning such as certificate expires in 12 days (2026-11-26), which is also the message of the incident it opens.

Response Data

Each SSL health check execution captures comprehensive certificate and connection data:

FieldDescription
TLS Handshake StatusWhether the TLS handshake completed successfully
TLS VersionThe negotiated TLS protocol version (e.g., TLS 1.2, TLS 1.3)
Cipher SuiteThe cipher suite used for the connection
Certificate Chain LengthNumber of certificates in the chain (leaf + intermediates)
SubjectThe certificate subject (typically the domain name)
IssuerThe certificate authority that issued the certificate
Serial NumberThe unique serial number of the certificate
Valid FromThe date the certificate became valid
Valid UntilThe date the certificate expires
Days Until ExpiryNumber of days remaining before the certificate expires
WarningSet when the run passed inside the warning window: what made the check Degraded

Example Configuration

SSL/TLS is healthcheck type 6. This is its config as the API and uptimyctl take it. The interval and timeout aren't part of it: they are set on the check itself, as intervalSeconds and timeoutSeconds.

SSL check config
{
  "host": "example.com",
  "port": 443,
  "expiryWarningDays": 30
}

Check Frequency

SSL certificates change infrequently, so checking every hour or every few hours is usually sufficient. More frequent checks are unnecessary and consume monitoring resources without added benefit.

Common Use Cases

  • Expiration Prevention — See certificates nearing expiry while there is still time to renew
  • Trust and Hostname Errors — Catch a self-signed certificate, an untrusted issuer or a certificate for another name
  • Renewal Verification — Confirm that automated renewals (Let's Encrypt, ACM) are working
  • Security Auditing — Track TLS versions and cipher suites across all domains
  • Multi-Domain Monitoring — Monitor certificates for all your domains from a single dashboard
  • Non-Standard Ports — Monitor TLS on services like SMTPS (465), IMAPS (993), or custom ports

Best Practices

  • Set up SSL checks for every domain and subdomain you manage
  • Set the warning so the Degraded window leaves you time to renew, and turn on Alert when degraded for certificates you renew by hand
  • Many automatic renewals, such as certbot's, run with about 30 days left. For those certificates, a warning below that (14 or 21) only turns Degraded when a renewal didn't happen
  • Monitor non-standard TLS ports alongside standard HTTPS on port 443
  • Review TLS version and cipher suite data regularly to ensure you meet security standards

Certificate Chain Issues

The chain is verified from the certificates your server sends. If it leaves out an intermediate certificate, the chain can't be verified and the check is Down, as it is for many API clients. Make sure your server sends every intermediate certificate.