Free tool

SSL certificate checker

Enter a public host and read the certificate on port 443: who issued it, how many days are left, and the not-after date. The same check reports whether the URL answers over HTTP.

Free 5 checks per hour. Sign up for 24/7 automated monitoring.

How the SSL certificate checker works in 60 seconds

What this SSL certificate checker looks at

We open TLS to port 443 and read the certificate presented for that hostname. You see the issuer (the organization, or the common name if there is no organization) and whole days until the not-after date, in UTC. A negative number means it has already expired.

Browsers reject an expired, self-signed, or mismatched certificate. If a strict handshake fails we try once more without those checks, only so the expiry still shows. The HTTP request stays strict: broken TLS fails it. We do not list every name on the certificate, the chain, or public certificate logs.

How to read the result

“42 days remaining” means the not-after date is still ahead. “Expires today” is the last UTC day. “Expired” means browsers should already be warning people. “No certificate” means port 443 did not yield one: the site may be HTTP-only, the port may be closed, or the handshake died before a certificate was sent.

Check the hostname visitors actually type. A certificate for www.example.com does not cover example.com unless that name is on it. If a CDN terminates TLS, we see the CDN certificate, which can differ from the one on your origin.

Common causes and fixes

Most certificate outages are failed renewals. The site process is often still running while every browser shows a warning.

  • Auto-renew failed: the HTTP challenge was blocked, the webroot was wrong, or the CA rate-limited the account. Read the renewal log and request it again.
  • The name on the certificate does not match the URL. Cover the apex and www, or redirect everyone to the name that is listed.
  • You renewed the origin, but a load balancer or CDN is still serving the old certificate. Reload that proxy, or renew where TLS actually ends.
  • The server clock is wrong, so a valid certificate looks not-yet-valid or already expired.
  • The new host never requested a certificate. Port 443 is only useful if something is listening with one.

Catch the next expiry before visitors do

On a monitor, certificate expiry is re-read about twice a day. When 14 days or fewer remain we warn you once on WhatsApp, Telegram, Slack, or email, and we do not repeat that warning more than weekly. The free plan includes 5 monitors, checked for uptime every 10 minutes. Pro checks every 5 minutes and Business every minute. That interval is the uptime check. The certificate date is the separate twice-daily sweep.

Questions

Does this trust the certificate the way a browser does?

We prefer a verified handshake. If that fails, we still read the expiry so an expired certificate does not look like missing data. Trust your browser for what a visitor actually sees.

Why can this page show days remaining while my browser warns?

You may be seeing a different certificate (CDN versus origin), or the name on the certificate may not match the host you opened. Compare the issuer and the exact hostname.

Do you check the chain and every subdomain?

No. You get the issuer and days remaining for the host you entered, plus the HTTP result. Check www, the apex, and api separately if each has its own certificate.

How often should a certificate be checked?

A stuck renewal is usually obvious within a day. Monitoring warns when fewer than 14 days remain. This public checker is a one-off look, limited to 5 checks per hour.