Resource

What is SSL certificate monitoring?

SSL certificate monitoring checks monitored hostnames over time so teams can catch expiry risk, validation failures, and unexpected certificate changes before customers see browser warnings.

Checker preview

api.example.com

Valid certificate

A one-time read separates connection, identity, chain, and expiry state before a monitor is created.

IssuerDigiCert TLS RSA SHA256 2020 CA1
Runway84 days remaining
Names8 SANs cover this hostname
Checker result

A one-time SSL check before you create a monitor.

The checker result shows issuer, expiry, runway, SAN count, chain depth, fingerprint, and validation state for one public hostname.

01

Choose the right check for the question

Certificate work gets confusing when every tool is treated as the same kind of monitoring. Start with the question you need answered.

Which certificate workflow fits?
QuestionUse thisWhat it answers
What does this endpoint serve right now?One-time SSL checkerIssuer, SANs, expiry, fingerprint, chain, and validation state for one public endpoint.
Will this hostname stay safe over time?Scheduled certificate monitoringExpiry windows, served-certificate history, changes, alerts, and delivery evidence.
Is the website or API available?Uptime monitoringHTTP or availability status across broad service checks, not certificate-specific evidence.
Was a certificate issued for this name?Certificate Transparency monitoringIssuance visibility in CT logs, not necessarily what customers receive at the endpoint.
02

What a one-time checker is good for

A free SSL checker answers what a domain or subdomain serves right now. Use it after renewal, before CDN changes, during incidents, or when a customer reports a browser warning.

  • Read issuer, SANs, serial number, fingerprint, validity dates, chain depth, and validation state.
  • Separate DNS, TCP, TLS handshake, hostname, active-window, expiry, and trust-chain problems.
  • Share a short-lived result with a teammate while diagnosing the hostname.
03

When scheduled monitoring is worth it

Scheduled monitoring is worth adding when the hostname needs recurring ownership. It repeats checks, stores history, applies expiry thresholds, and sends warnings to the channels your team watches.

  • Use it for app, API, checkout, identity, docs, CDN, and client domains.
  • Use it when renewals depend on more than one person or vendor.
  • Use it when certificate changes should be reviewable after platform work.
04

What Domain Trust Watch does

Domain Trust Watch checks monitored public TLS endpoints, records certificate snapshots, tracks expiry windows, detects served-certificate changes, and sends events through email, Slack incoming webhooks, and signed customer webhooks.

05

What Domain Trust Watch does not do

Domain Trust Watch does not issue certificates, renew certificates automatically, request private keys, install an internal agent, or provide live Certificate Transparency alerts.

  • Private/internal certificate monitoring is outside the public-hostname model.
  • Certificate Transparency monitoring is a separate security requirement.
  • Broad uptime, APM, logs, tracing, on-call, status pages, and incident management remain separate tools.
FAQ3 answers
  1. What is SSL certificate monitoring?

    SSL certificate monitoring checks monitored hostnames over time so teams can see expiry risk, certificate changes, validation failures, and alert delivery before a certificate problem becomes customer-facing.

  2. Does Domain Trust Watch need private keys?

    No. Domain Trust Watch reads public certificate metadata from TLS handshakes. It does not ask for private keys, server credentials, or certificate procurement access.

  3. Is Domain Trust Watch an uptime monitoring product?

    No. Domain Trust Watch focuses on certificate risk: expiry, public certificate snapshots, change detection, alerts, and team access. Teams can still use uptime monitoring for availability checks.

Start with one read

Check a hostname now, then monitor the ones that matter later.

The checker answers what is served now. Monitoring keeps checking and warning after the immediate question is answered.