Network Tools

SSL Certificate Checker

Check a server's SSL/TLS certificate the way a browser does: expiry, hostname match, chain of trust, key strength, supported TLS versions and cipher, summed up in an A–F grade with the reasons.

A domain or URL. Only public servers can be checked.

About SSL/TLS certificates

An SSL/TLS certificate proves that a server really belongs to the domain in the address bar and lets the browser set up an encrypted connection. Browsers only trust it when it is within its validity period, lists the host name in its Subject Alternative Names, and chains up through one or more intermediate certificates to a root certificate in their trust store.

Most problems are simple to fix: renew before the expiry date (automate it, for example with Let's Encrypt), install the full chain file instead of the bare certificate, include every host name (with and without www) in the certificate, use at least a 2048-bit RSA or a P-256 ECDSA key, and allow only TLS 1.2 and TLS 1.3.

This checker resolves the domain once, connects directly to that public address and sends the domain name as SNI, exactly like a browser. It does not check OCSP stapling or certificate revocation. To inspect a certificate file, a chain bundle or a CSR without connecting to a server, use the X.509 Certificate & CSR Decoder.

Frequently Asked Questions

It connects to the server like a browser, reads the certificate chain and checks the expiry date, whether the certificate covers the host name, whether the chain leads to a trusted root, key type and size, signature algorithm, the negotiated TLS version and cipher, and whether TLS 1.0, 1.1, 1.2 and 1.3 are accepted.

A server starts at A. An expired, untrusted or wrong-host certificate, a broken key or a SHA-1 signature gives F. A key under 2048 bits caps the grade at C. Accepting TLS 1.0 or 1.1, missing TLS 1.3, no forward secrecy or a certificate expiring within 14 days caps it at B. The reasons are listed under the grade.

Your server must send its own certificate plus the intermediate certificate(s) of the CA. Browsers sometimes fill the gap from cache, but many apps, APIs and older devices fail. Install the full chain file (often called fullchain.pem or ca-bundle) from your CA.

Yes, for ports that start TLS immediately: 443, 8443, 465 (SMTPS), 993 (IMAPS), 995 (POP3S), 636 (LDAPS) and 853 (DNS over TLS). STARTTLS ports such as 25, 587 and 143 are not supported.

Both versions are deprecated (RFC 8996) and lack modern protections. All current browsers have dropped them, so leaving them enabled only helps attackers and outdated clients. Allow TLS 1.2 and TLS 1.3 only.

No. Only public host names are checked. Names that resolve to private, loopback or reserved addresses are refused.