SSL certificate monitoring with warnings separated from downtime

UptimeSure opens a verified TLS connection, inspects the peer certificate and records expiry information. A certificate that is still valid but close to expiry remains UP and exposes an expiry warning; invalid, expired or failed TLS connections are DOWN.

An SSL monitor checks the certificate presented by a host and port, validates the TLS connection, calculates days remaining and compares that value with your warning threshold.

Actual TLS validation/connectivity failure or an expired/invalid certificate is DOWN. Being within the warning window alone is not downtime.

Certificate metadata is stored with check timing information so the monitor detail UI can show days remaining and warning state while preserving correct service status.

What UptimeSure checks

TLS connection and certificate validation
Certificate expiry timestamp
Days remaining
Issuer and subject metadata
Configurable warning threshold

Common use cases

Public websites
API gateways
TLS-enabled service endpoints
Certificate renewal verification

Configuration

Host/domain
TLS port
Check interval
Timeout
Expiry warning threshold

Alerts and recovery

Downtime alerts follow the normal incident pipeline. V1 surfaces certificate-expiry warnings in the product UI; warning-specific delivery policies can evolve separately from outage alerts.

Example

Example: monitor example.com:443 with a 30-day warning threshold. At 20 days remaining the monitor stays UP and shows a warning; an invalid TLS handshake is DOWN.

Frequently asked questions

Does an expiry warning make the monitor DOWN?

No. A still-valid certificate stays UP.

What makes SSL DOWN?

TLS connection failure, validation failure or an actually expired/invalid certificate.