Configuring SSL Certificates and HTTPS Tools: From Alerts to On-Call

Certificate failures can usually be detected in advance. By monitoring expiration dates, chain integrity, domain coverage, and mixed content—and routing alerts …

Insights:Configuring SSL Certificates and HTTPS Tools: From Alerts to On-Call

Three-Layer Tools

Layer Tool Purpose
Instant check openssl, curl Check certificate, chain, and validity period
Periodic testing SSL Labs, online chain checker Check ratings, protocols, and compatibility
Continuous monitoring Existing monitoring system or probe service Expiry alerts, handshake failure alerts

No need to set up all three layers at once; start by using your existing monitoring for Layer 3.

Command-Line Checks

openssl s_client -connect example.com:443 -servername example.com -showcerts
curl -I https://example.com

Check three things: certificate validity period, whether the SAN covers the current domain, and whether the returned chain includes intermediate certificates.

How to Set Up Expiry Alerts

  • 30 days before expiry: notify the responsible person.
  • 14 days before expiry: escalate to the team group chat.
  • 7 days before expiry: enter on-call handling.
  • 1 day before expiry: phone call or urgent escalation if unresolved.
  • After successful renewal: auto-reload and verify.

Alerts must include the domain, certificate type, expiry date, owner, and an action link.

What Metrics to Monitor

  • Whether the TLS handshake succeeds.
  • Certificate remaining validity days.
  • Whether the certificate chain is complete.
  • Domain name match.
  • Protocol version meets requirements.
  • Whether the page still serves HTTP resources.
  • Whether redirects are looping.

On-call Responsibilities

  • Who handles renewal: operations or the provider.
  • Who manages deployment: at the entry layer or per server.
  • Who performs review: business or technical team.
  • Who takes over during holidays.
  • Rollback plan in case of failure.

An alert without an owner is no alert at all.

One-time Configuration Steps

  1. Inventory all domains and entry points.
  2. Consolidate certificate inventory and expiry schedule.
  3. Connect to monitoring and alerts.
  4. Configure auto-renewal and reload.
  5. Schedule quarterly reviews; decommission unused domains.

Boundaries

Monitoring can catch certificate and handshake issues, but cannot replace application availability monitoring. CDN, load balancer, and client differences still need validation along the actual traffic path.

Related Articles: