ismycodesafe.com

SSL/TLS Certificate Checker

Check a site's SSL certificate expiry, issuer, and negotiated TLS version in seconds. No signup required.

Reading your result

A passing check shows four rows. Here is what each one means and what it leaves out.

Subject is the name on the certificate, normally your domain. If it shows a different host, you are looking at a shared or default certificate from your hosting provider.

Issuer shows the issuing certificate's common name, so expect a short code rather than a company name. YR1, YE2, R11 and similar codes belong to Let's Encrypt. Its certificates currently run for 90 days, so renewal has to be automated.

Expires is the notAfter date from the certificate, in UTC. The "Expires in N days" line above it is computed in your browser and rounded down. Under 30 days on a Let's Encrypt certificate usually means renewal already failed at least once.

Protocol is the version this one connection agreed on, typically TLSv1.3 or TLSv1.2. It is not a list of everything your server accepts. The checker connects with Python's default client settings, which refuse anything older than TLS 1.2. A server that still offers TLS 1.0 alongside 1.3 will pass here and show TLSv1.3. The commands further down test for that.

There is no cipher row. The checker does not test cipher suites.

When it fails: the error text, decoded

If the handshake fails you get the raw error instead of the four rows, and an expired certificate shows up here rather than as a negative day count. These are the messages the checker's code returns for the public test hosts at badssl.com (checked October 2026, Python 3.12 with OpenSSL 3.0):

Error containsWhat is wrongUsual fix
certificate has expiredPast notAfterRenew, then find out why auto-renewal stopped
Hostname mismatch, certificate is not valid forCertificate does not cover this nameReissue with the hostname as a SAN, often the www or apex variant
unable to get local issuer certificateServer sends the leaf certificate without the intermediateServe fullchain.pem, not cert.pem. Some browsers paper over this, API clients do not
self-signed certificateNo public CA signed itReplace with a CA-issued certificate
self-signed certificate in certificate chainChain ends at a root the client does not trustUsually a private or corporate CA. Public sites need a public root
sslv3 alert handshake failureNo protocol or cipher in commonSeen against a TLS 1.0-only server. Despite the name, it is rarely about SSLv3
timed out or Connection refusedNothing answered on port 443Firewall, wrong DNS record, or the service is down

SSL handshake failed: find out which side gave up

"SSL handshake failed" is a family of errors, not one. The client and the server opened a connection and either could not agree on how to encrypt it, or the client refused the certificate it was shown. The words depend on the client. This checker prints sslv3 alert handshake failure, curl reports error 35, Chrome shows ERR_SSL_VERSION_OR_CIPHER_MISMATCH or ERR_SSL_PROTOCOL_ERROR, and a site behind Cloudflare shows error 525 when the handshake between Cloudflare and your origin fails.

One command tells the two main causes apart:

openssl s_client -connect example.com:443 -servername example.com </dev/null 2>&1 \
  | grep -E "no peer certificate|Cipher is|Verify return code"

no peer certificate available together with Cipher is (NONE) means the handshake died before any certificate was sent. The two sides have no protocol version or cipher in common. If a cipher was agreed and Verify return code is anything other than 0 (ok), the connection worked and the certificate is the problem: the text after the code says which (expired, wrong name, missing issuer).

For a Cloudflare 525, run the same command against the origin server's IP address and keep -servername set to your domain. That shows what Cloudflare sees when it connects to you. If only one office network or one laptop fails, suspect a proxy or antivirus product that intercepts TLS before it reaches the site.

Unable to get local issuer certificate: server or client?

Two different faults print this message. Either the server sends its own certificate without the intermediate that links it to a trusted root, or the client's CA store lacks that root (an outdated bundle, or a company proxy that re-signs traffic with an internal CA). Count the certificates the server actually sends:

openssl s_client -connect example.com:443 -servername example.com -showcerts </dev/null 2>/dev/null \
  | grep -E "^ *[0-9]+ s:"

A single line starting with 0 s: means the server sends only its own certificate. Point the server at fullchain.pem instead of cert.pem and reload it. If you see 1 s: as well, the chain is complete and the client is the side to fix: update its CA bundle, or for Node.js add the internal CA with NODE_EXTRA_CA_CERTS. Turning verification off (curl -k, NODE_TLS_REJECT_UNAUTHORIZED=0) hides the error and removes the protection with it.

What this checker does not test, and what does

For the protocol versions your server still accepts:

openssl s_client -connect example.com:443 -servername example.com -tls1_1 </dev/null

A completed handshake means TLS 1.1 is still enabled. Swap -tls1_1 for -tls1 to test 1.0. Recent OpenSSL builds may refuse to offer these old versions at all, in which case the next command is more reliable.

For the full cipher list per protocol, with a grade per cipher:

nmap --script ssl-enum-ciphers -p 443 example.com

For the expiry date alone, which is handy in a cron job:

echo | openssl s_client -connect example.com:443 -servername example.com 2>/dev/null \
  | openssl x509 -noout -enddate

For a deeper report covering chain paths and every protocol, see how this checker compares with SSL Labs.

How to Fix SSL Issues

Most SSL problems have straightforward fixes. Here's a practical checklist:

1.

Install Let's Encrypt with Certbot

Run sudo certbot --nginx -d yourdomain.com -d www.yourdomain.com and Certbot handles certificate issuance, Nginx configuration, and sets up a systemd timer for automatic renewal. For Apache, swap --nginx with --apache.

2.

Enable auto-renewal and test it

Verify the timer is active: sudo systemctl status certbot.timer. Do a dry run: sudo certbot renew --dry-run. Set up a cron-based alert that checks expiry with openssl s_client and emails you if the certificate has fewer than 14 days left.

3.

Enable HSTS

Add the Strict-Transport-Security header with max-age=31536000; includeSubDomains; preload. This tells browsers to always use HTTPS, preventing SSL-stripping attacks. Check your headers with our HTTP Header Security Checker.

4.

Force HTTPS redirects

Configure a 301 redirect from HTTP to HTTPS at the server level. In Nginx: return 301 https://$host$request_uri;. Don't rely on application-level redirects; they run too late and may leak data on the initial request.

5.

Harden your cipher configuration

Use Mozilla's SSL Configuration Generator to produce a secure config for your specific server and OpenSSL version. Choose the "Intermediate" profile for broad compatibility or "Modern" if you only need to support recent browsers.

6.

Set a Content Security Policy

A strong CSP prevents mixed content by restricting which origins can serve resources. Use upgrade-insecure-requests to automatically rewrite HTTP sub-resource URLs to HTTPS. Generate a policy with our CSP Header Generator.

Frequently Asked Questions

What is the difference between SSL and TLS?
SSL (Secure Sockets Layer) is the predecessor to TLS (Transport Layer Security). SSL 3.0 was deprecated in 2015 due to the POODLE vulnerability (CVE-2014-3566). TLS 1.0 replaced SSL 3.0 in 1999, and the current standard is TLS 1.3, published as RFC 8446 in August 2018. People still say 'SSL certificate' out of habit, but every modern certificate actually uses TLS.
How often should I renew my SSL/TLS certificate?
That depends on your certificate authority. Let's Encrypt issues certificates valid for 90 days and recommends renewing at 60 days. Commercial CAs like DigiCert and Sectigo sell 1-year certificates (the CA/Browser Forum capped public certificate lifetimes at 398 days in September 2020). Apple proposed reducing this to 45 days by 2027. Automate renewal with certbot or ACME clients to avoid unexpected expiration.
What causes 'certificate not trusted' browser warnings?
Four common causes: (1) Self-signed certificates that aren't in the browser's trust store. (2) Missing intermediate certificates in your server's certificate chain. The browser can't trace a path to a trusted root CA. (3) An expired certificate. (4) A hostname mismatch where the domain in the URL doesn't match the certificate's Common Name or Subject Alternative Name. Our checker verifies all four.
Does an SSL certificate improve my Google ranking?
Google confirmed HTTPS as a ranking signal in 2014 and has steadily increased its weight. Chrome marks HTTP pages as 'Not Secure' since version 68 (July 2018). While HTTPS alone won't launch you to page one, missing it actively hurts both rankings and user trust. It's table stakes for any site that wants to compete in search.
What is mixed content and why is it dangerous?
Mixed content happens when an HTTPS page loads sub-resources (images, scripts, stylesheets, iframes) over plain HTTP. 'Active' mixed content (scripts and stylesheets) is blocked by default in all modern browsers because an attacker could modify the HTTP response and inject malicious code. 'Passive' mixed content like images may still load but triggers a warning. Fix it by updating all resource URLs to HTTPS or using protocol-relative paths.
How does the TLS handshake work?
In TLS 1.3, the handshake completes in one round-trip (1-RTT). The client sends a ClientHello with supported cipher suites and key shares. The server responds with its chosen cipher, its certificate, and the finished message. All in one flight. Both sides then derive session keys from the shared secret. TLS 1.2 requires two round-trips because cipher negotiation and key exchange happen in separate steps.
What is Certificate Transparency and why does it matter?
Certificate Transparency (CT) is a public logging system (RFC 6962) where CAs must publish every certificate they issue. Browsers like Chrome require at least two Signed Certificate Timestamps (SCTs) from independent CT logs. This means if someone fraudulently issues a certificate for your domain, it shows up in public logs and you can detect it. Monitor your domains at crt.sh (https://crt.sh/) or use Google's CT search.
Can I use a free SSL certificate for production?
Absolutely. Let's Encrypt has issued over 4 billion certificates since 2015. Their DV (Domain Validation) certificates are cryptographically identical in strength to paid DV certificates. Same RSA-2048 or ECDSA P-256 keys, same browser trust. Paid certificates offer Organization Validation (OV) or Extended Validation (EV) which display the company name, plus warranty coverage and dedicated support. For most sites, Let's Encrypt is sufficient.

Related Security Tools

SSL is just one layer of your site's security. Check these related areas:

Go Beyond SSL

SSL is critical but it's only one piece. Our full security scan runs 150+ checks including OWASP Top 10, exposed ports, CVE lookups, DNS analysis, and more, all from a single URL.

Claude AI helped me with phrasing and proofreading in this article.