Skip to content

SSL Certificate Checker

Check any public website's SSL/TLS certificate: whether it is valid and trusted, when it expires, who issued it, which names it covers, the chain the server sends and the TLS version negotiated. Useful before a launch and whenever a browser shows a warning.

Server-assistedFreeNo sign-up

Server-assisted. What you enter here (a domain, URL or test payload) is sent to our server to run the check. We don't save it, but our web server logs record the request, including a domain or address you entered, for about 14 days. Details

How to use the ssl certificate checker

  1. Enter the domain (or paste the site's URL) and press Check certificate.
  2. Read the verdict banner first: it tells you if the certificate is expired, not yet valid, issued for a different name, or not trusted.
  3. Check the days remaining and set a reminder if renewal is close; many certificates now last only 90 days.
  4. Look at the covered names to confirm both the bare domain and www are included, and at the chain to spot a missing intermediate.

Features

  • Verdict on validity, hostname match and trust, with the exact reason when something is wrong
  • Days remaining with a warning at 14 days, plus precise valid-from and valid-until times
  • Issuer, subject, serial number, SHA-256 fingerprint and every Subject Alternative Name
  • The chain exactly as the server presents it, so a missing intermediate is visible
  • Negotiated TLS protocol, cipher suite and key type

What the checks mean

A certificate proves that the party you connect to controls the domain. Browsers verify three things: the current time is inside the validity window, the requested hostname appears in the certificate's names, and the chain leads to a root the browser trusts. This tool performs the same checks from VoltKit's server.

A chain problem is the most common cause of 'works on my laptop, fails on phones': the server omits an intermediate certificate that desktop browsers happen to have cached. The chain section shows exactly what was sent.

Limits of a remote check

The check connects to port 443 with your domain as the server name (SNI) from VoltKit's hosting region. Sites that serve different certificates by region or by client, or that block automated connections, may show something different from what your browser sees. Trust is evaluated against the server's root store, which is very close to, but not identical to, each browser's.

Frequently asked questions

The certificate is valid but my browser still warns. Why?

Common causes: mixed content (HTTP resources on an HTTPS page), a certificate covering example.com but not www.example.com (or vice versa), an old device missing a newer root, or a corporate proxy replacing certificates. The covered-names list here settles the second case.

How early should I renew?

Renew at least two weeks before expiry; automated renewals (Let's Encrypt, most hosts) typically run at 30 days remaining. If days remaining keeps shrinking on an auto-renewed site, the renewal job is broken.

Why does it say the chain is not trusted for a Let's Encrypt site?

Usually the server is not sending the intermediate certificate, so the check cannot build a path to a trusted root. Configure the full chain (fullchain.pem rather than cert.pem) and check again.

Can I check a private or internal host?

No. Only public domains resolving to public addresses are accepted, to keep the checker from being used to probe internal networks.

Other tools people use alongside SSL Certificate Checker.

You might also like

Something useful from another corner of VoltKit.