Skip to content

SSL Certificate Checker

Check an SSL/TLS certificate: trusted or not, when it expires, what it covers and the full chain.

This tool runs on our server, because a browser cannot send DNS queries, pings or raw network connections. Only the domain, address or URL you enter is sent; results are not stored. Privacy

Shows whether the certificate is trusted, when it expires, the names it covers, the full chain and which TLS versions the server accepts.

Report a problem

Don't include personal or sensitive information.

What happened, and what did you expect? (10–2000 characters) 0 / 2000

Your browser and system, screen size and recent error messages on this page. Never what you typed or your files. Privacy

What is sent
 

Enter a domain to inspect its SSL/TLS certificate. The checker connects the way a browser does, then tells you whether the certificate is trusted, whether it covers the name you typed, how many days are left before it expires, which authority issued it, its key type and fingerprint, and every name (SAN) it is valid for.

It also shows the full certificate chain the server sends – a missing intermediate certificate is one of the most common causes of "not secure" errors on some devices – and tests which TLS versions the server accepts, flagging old TLS 1.0 and 1.1 and a missing TLS 1.3. Other TLS ports such as 465, 993, 995 and 8443 can be checked too.

How to use the SSL Certificate Checker tool

  1. Enter the domain name, for example example.com.
  2. Keep port 443 for websites, or choose another TLS port (mail, cPanel …).
  3. Click Check certificate.
  4. Read the summary and fix any problems listed at the top.

Why use ToolOrca SSL Certificate Checker

  • Trust check against the standard root store, with the exact error
  • Days until expiry, valid-from and valid-to dates
  • Host name match and the full list of SANs
  • Complete chain: server, intermediate and root certificates
  • TLS 1.3 / 1.2 / 1.1 / 1.0 support, cipher and ALPN (HTTP/2)
  • Ports 443, 8443, 465, 993, 995, 636, 853, 2083, 2087, 5061, 9443

Common certificate errors and fixes

Expired: renew the certificate; with Let's Encrypt check that the renewal job (certbot, acme.sh) runs and reloads the web server. Name mismatch: the certificate does not list the domain – add both example.com and www.example.com when you request it. Unable to verify / incomplete chain: install the full chain file (fullchain.pem), not only the server certificate.

Self-signed certificates are fine for testing but are never trusted by browsers. Free, trusted certificates are available from Let's Encrypt, ZeroSSL or your hosting provider.

Which TLS versions should be on?

Enable TLS 1.2 and TLS 1.3 and turn off TLS 1.0 and 1.1, which all major browsers stopped supporting in 2020. TLS 1.3 is faster (one round trip less) and safer. In nginx: ssl_protocols TLSv1.2 TLSv1.3;, in Apache: SSLProtocol -all +TLSv1.2 +TLSv1.3.

Frequently asked questions

How many days before expiry should I renew?

Let's Encrypt renews 30 days before expiry. The tool warns when fewer than 30 days are left and shows an error under 14.

Can I check a certificate on an IP address?

Yes, enter a public IP. The name check then compares against IP addresses in the certificate.

Why is a site trusted in my browser but not here?

Browsers can fetch missing intermediate certificates themselves; many apps and older phones cannot. Fix the chain on the server.

Does it check certificate revocation?

No. Revocation checks (OCSP/CRL) are not part of this test.

Can I check a device on my home or office network?

No. For safety, private and local addresses (192.168.x.x, 10.x.x.x, localhost, .local names and similar) are refused. Our server can only test public hosts on the internet.