upsonar.io

Free SSL Certificate Monitoring

upsonar.io monitors your SSL/TLS certificates and alerts you before they expire. Records the issuer, the hostnames the certificate covers and the TLS protocol version — automatically, every day.

How it works: Upsonar connects to each HTTPS site once a day, reads the certificate, and records the expiry date, issuer and TLS version. The free plan includes a 7-day expiry alert by email and Telegram; paid plans pick their own lead times up to 90 days and add Slack and webhooks.

Expiry alerts up to 90 days ahead · Chain check · Free plan available

What is SSL certificate monitoring?

SSL certificate monitoring is the continuous automated checking of a website's TLS certificate to verify it is valid, correctly installed, and not approaching expiration. A monitoring service fetches the certificate from the domain on a regular schedule (typically daily), parses the expiry date and issuer, lists the hostnames the certificate covers (SANs), and checks supported TLS protocol versions. When the expiry date approaches a configured threshold, the monitor sends an alert — usually via email, Telegram, Slack, or webhook. Independent SSL monitoring is the only reliable safety net against silent auto-renewal failures.

90 days
Let's Encrypt certificate lifetime — short enough that manual tracking fails
2014
Year HTTPS became a Google search ranking signal (Search Central)
30 / 14 / 7
Days before expiry that Upsonar sends alerts
8
Global regions Upsonar checks certificates from

Why SSL Monitoring Matters

Browser Warnings

Expired SSL = full-page security warning. Most visitors leave immediately. Your site is effectively offline.

Silent Renewal Failures

Auto-renewal fails silently due to DNS changes, firewall rules, or expired payment methods. Independent monitoring catches this.

Early Warning You Choose

An alert 7 days before expiry on the free plan; paid plans warn you up to 90 days ahead, with time to fix auto-renewal issues.

How SSL Monitoring Works

The monitor opens a TLS connection. Every check cycle, Upsonar opens a fresh TLS 1.2 or 1.3 connection to your domain on port 443 from each region the monitor is assigned, out of 8 worldwide. The server's certificate is captured during the TLS handshake along with any intermediate certificates the server sends. No browser is involved — the check is a pure protocol-level handshake that takes under a second.

The certificate is parsed and validated. Upsonar extracts the notBefore and notAfter dates, the issuer (Common Name of the issuing CA), the subject alternative names (SANs) the certificate covers, and the signature algorithm. The certificates the server sent are then verified up to a trusted root CA. Missing intermediates are not fetched, so an incomplete chain — one that works in desktop Chrome but fails in mobile Safari and curl — shows up on the check and in the grade.

Alerts fire before expiry: 7 days ahead on the free plan, at the lead times you choose on paid plans. When the notAfter date crosses any alert threshold, Upsonar creates an incident and sends a notification through every configured channel (email, Telegram, Slack, webhook). Each alert includes the certificate expiry date, days remaining, issuer, and a direct link to the incident with the full diagnostic data. Multi-threshold alerting is critical because troubleshooting a broken ACME auto-renewal can take days — the first 30-day alert gives teams time to fix the underlying problem without an emergency page.

What We Check

Validity Window — The certificate is already valid and has not expired yet.
Expiration Date — Exact expiry date and days remaining. Alert 7 days ahead, up to 90 on paid plans.
Security Grade — An A–F grade for the TLS setup, tracked from check to check.
TLS Protocol Version — TLS 1.2, 1.3 support. Detects deprecated protocols.
Issuer Details — Certificate Authority name and organization.
Covered Hostnames — The domains and wildcards listed in the certificate (SANs).

Check Your SSL Certificate Now

Free instant SSL check — expiry, issuer, chain, TLS version. No signup required.

Loading regions…

Frequently Asked Questions

SSL certificate monitoring is the continuous automated checking of a website's TLS certificate to verify it is valid, correctly installed, and not approaching expiration. A monitoring service fetches the certificate from your domain on a regular schedule (typically daily or every few hours), parses the expiry date and issuer, lists the hostnames it covers (SANs), verifies the chain up to a trusted root CA, and records supported TLS protocol versions. When the expiry date approaches a configured threshold, the monitor sends an alert — usually via email, Telegram, Slack, or webhook; other findings, such as a broken chain, are recorded on the check and in the grade. Independent SSL monitoring is essential because auto-renewal via ACME (Let's Encrypt) or commercial CAs can fail silently, and calendar reminders for manual renewal routinely get missed.

At least once per day. Most SSL monitoring services check every 4-24 hours because certificate state does not change often — what matters is reliable detection well in advance of expiry. Checking more often (hourly or per-minute) wastes resources without catching problems faster; checking less often (weekly) is dangerous because you may miss the narrow window between an auto-renewal failure and the old certificate expiring. Upsonar checks SSL certificates at least once daily on every plan and sends an alert 7 days before expiration on the free plan; paid plans choose their own lead times, up to 90 days, which leaves time to renew manually if automation fails.

SSL certificates expire by design to limit the impact of compromised keys and to force regular re-verification of domain ownership. Let's Encrypt, the largest certificate authority on the web, issues certificates with a 90-day lifetime and recommends renewing every 60 days. Commercial CAs like DigiCert, Sectigo, and GoDaddy issue certificates valid for 1 year (since 2020 — previously 2 years). The CA/Browser Forum has proposed reducing maximum certificate lifetime to 47 days by 2029, which will make automation and monitoring even more important than today.

When your SSL certificate expires, all modern browsers display a full-page security warning — Chrome shows "Your connection is not private" (NET::ERR_CERT_DATE_INVALID), Firefox shows "Warning: Potential Security Risk Ahead", Safari shows "This Connection Is Not Private". Most users will not click through. Your site becomes effectively unreachable to the general public. Additional consequences: search rankings drop because Google has used HTTPS as a ranking signal since August 2014 (source: Google Search Central blog); API integrations that validate certificates break immediately; email servers sharing the same certificate start rejecting mail; and third-party services that embed your site (widgets, OAuth, webhooks) begin failing.

Yes. Google officially announced HTTPS as a lightweight ranking signal in August 2014 and has strengthened it since. Chrome has marked all non-HTTPS pages as 'Not Secure' since July 2018, and Google Search actively prefers HTTPS URLs when both HTTP and HTTPS versions of a page exist (the HTTPS version is chosen as canonical). A website with an expired or invalid certificate may be dropped from search results entirely — not because Google penalizes HTTP, but because Googlebot cannot safely crawl a site whose certificate fails validation.

On the free plan Upsonar sends an SSL expiry alert 7 days before expiration. Paid plans choose their own lead times — any of 90, 60, 30, 14, 7, 3 and 1 days — and get a separate alert at each through every configured channel (email, Telegram, Slack, webhook). A 30-day or longer lead time gives teams time to renew the certificate manually, investigate auto-renewal failures, or coordinate with the infrastructure team. That matters because troubleshooting a broken ACME setup or coordinating with a commercial CA can take days.

Yes — auto-renewal fails more often than expected, and it usually fails silently. The most common causes: DNS changes that break the ACME HTTP-01 or DNS-01 challenge, firewall rules blocking inbound connections from the CA's validation servers, expired payment methods for paid certificates, server migrations that skip the renewal cron job, changes to the .well-known/acme-challenge directory during a site redesign, rate-limit caps on Let's Encrypt (5 duplicate certificates per week per account), and account key mismatches after restoring from backups. Because auto-renewal is automatic, teams rarely notice these failures until the old certificate is a few days from expiring. Independent monitoring is the only reliable safety net.

Yes. On every check Upsonar builds the chain from the certificates your server sends up to a trusted root CA, without fetching missing intermediates the way desktop Chrome does. A broken chain is shown on the check and lowers the security grade. This matters because an incomplete chain often works in desktop Chrome but fails in mobile Safari, older Android, API clients and curl.

Never Miss an SSL Expiry Again

Free plan includes SSL monitoring for 3 websites with email and Telegram alerts. No credit card required.

Set up in 30 seconds · Free forever

Last updated: April 2026