networkutils.org

Home / Security Tools / Certificate Monitor

Certificate Monitor

Security Tools

Days remaining and issuer for every SAN.

Run this tool: the interactive Certificate Monitor loads here (requires JavaScript). Input: Domain — e.g. example.org.

Description

The Certificate Monitor reports the days remaining until each TLS certificate for a domain expires, listing every Subject Alternative Name (SAN) covered by the certificate and the issuing CA.

Features

✓ Days-to-expiry for every SAN on the certificate
✓ Issuer and validity window display
✓ Multi-SAN coverage report
✓ Expiry warning thresholds

How to Use

Enter a domain name (example.org) and run the tool. The probe retrieves the certificate and lists every name it covers with its expiry.

Input: Domain — e.g. example.org.

Understanding the Results

The output shows the issuer, the not-before and not-after dates, and a table of every SAN with the days remaining until expiry. Certificates within 14 days of expiry should be renewed immediately; an expired certificate triggers browser security warnings and breaks automated clients.

Common Use Cases & Examples

→ Track days-to-expiry for all SANs on a multi-domain certificate.

→ Get an early warning before a certificate expires.

→ Verify renewal succeeded by checking the new not-after date.

→ Audit certificate coverage across many hostnames.

Frequently Asked Questions

What is a SAN and why are there many on one certificate?

A Subject Alternative Name is a hostname the certificate is valid for. Modern certificates are multi-SAN (UCC) so one certificate can cover example.org, www.example.org and api.example.com — cheaper and simpler than one cert per host.

When should I renew my certificate?

Renew at least 30 days before expiry to leave buffer for automation failures and propagation. Many ACME clients auto-renew at 20–30 days remaining. Treat anything under 14 days as urgent.

Why does my certificate expire if I use a CDN?

If the CDN terminates TLS, the certificate shown is the CDN’s edge certificate, not your origin’s. Check your origin certificate separately by connecting directly to the origin hostname, and ensure the CDN is configured to serve a cert covering all your SANs.

About this tool

Maintained by
networkutils.org editorial team
Last updated
September 2026
Testing methodology
TLS checks perform a real TLS handshake with Node.js tls against port 443 and inspect the presented certificate chain; the Security Headers and Exposure Check tools issue HTTP requests from the server; Subdomain Discovery and CT Log Search query the public crt.sh Certificate Transparency service.
Technical references
RFC 5280 — X.509 Certificate Profile · RFC 8446 — TLS 1.3