SSL Checker - Test Certificate, Expiry Date and Security Headers
SSL certificate checker
Enter a domain to check its HTTPS certificate: validity, days left, covered names, chain and TLS version, plus a report on its security headers.
Our server connects to the domain on port 443 and reads only the certificate and the response headers of the home page; redirects are not followed. For security, IP addresses and names that point to private or local networks are refused. The domains you check are not stored.
What the SSL checker tells you
An SSL/TLS certificate proves that a website really belongs to the name in the address bar and lets the browser encrypt the connection. This checker connects to a domain the way a browser does and reports what it finds: whether the certificate is valid and trusted, how many days are left, which names it covers, the chain the server sends, the TLS version and cipher, and which security headers the site sets.
How to use it
- 1 Type a domain such as www.example.com (a full https:// address also works; only the name is used, on port 443).
- 2 Press “Check”. The verdict at the top shows the most important problem first; the days-left box turns amber at 30 days and red at 7.
- 3 Review the chain and the security headers. If the site redirects (for example to www), use the button to check the target address too.
Common certificate errors
An expired certificate is the most frequent problem and usually means automatic renewal stopped working. A name mismatch appears when the certificate does not list the exact name you visit, for example a certificate for example.com used on www.example.com; a wildcard such as *.example.com covers one level only. A self-signed certificate is not vouched for by any certificate authority, and an incomplete chain happens when the server forgets to send the intermediate certificate: some browsers can repair this, others and many apps cannot.
Why certificates expire so often
Shorter lifetimes limit the damage if a private key leaks and force renewal to be automated. Publicly trusted certificates have been limited to 398 days since September 2020; under a CA/Browser Forum decision the maximum fell to 200 days in March 2026 and is planned to reach 47 days in 2029. Most sites therefore renew automatically every few weeks, which is why a renewal that silently fails is noticed only when the certificate expires.
TLS versions and cipher suites
TLS 1.3 is the current version: its handshake is faster and every cipher suite it allows offers forward secrecy. TLS 1.2 is still safe with modern ciphers such as ECDHE with AES-GCM or ChaCha20. TLS 1.0 and 1.1 were formally deprecated in 2021 and current browsers refuse them. The checker shows the version and cipher suite negotiated with our server, which supports every version from 1.2 up, so the result reflects the best the site offers.
Security headers in brief
HTTP response headers tell the browser how strictly to treat a page. Strict-Transport-Security (HSTS) makes it refuse plain HTTP for the time set in max-age; Content-Security-Policy restricts where code may load from; X-Frame-Options or CSP frame-ancestors prevent clickjacking; X-Content-Type-Options: nosniff stops content type guessing; Referrer-Policy limits what leaks to other sites; Permissions-Policy switches off features the page does not need. A missing header is not an error by itself, but each one closes a common attack path.