Security and SSL
Free SSL checker for any website
Check a website’s SSL certificate in seconds: whether it is valid for the name, when it expires, whether the server sends the full chain to a trusted root, which TLS versions it accepts, and whether HTTP redirects to HTTPS. Every problem comes with a plain-English fix for your host, Let’s Encrypt, Nginx or Apache.
- Expiry and chain
- TLS 1.0 to 1.3
- Fixes for each problem
Free, no sign-up. Results are only saved if you share them.
This tool needs JavaScript. Turn JavaScript on and reload the page.
SSL checker
Check a website's SSL (TLS) certificate: whether it is valid for the name, when it expires, whether the chain is complete and trusted, which TLS versions the server accepts, whether http:// redirects to HTTPS, HSTS, and the CAA records that say which certificate authorities may issue for the domain.
What this check looks at
- One TLS connection reads the certificates the server sends. The chain is checked against the trusted root certificates on this server, the way browsers check it, without fetching missing certificates.
- One connection for each TLS version (1.0, 1.1, 1.2 and 1.3) shows which ones the server accepts. If this server's TLS library cannot offer an old version, the result says it was not tested rather than guessing.
- On port 443, one HEAD request to http:// (without following redirects) and one to https:// for the HSTS header. Other ports skip these website checks.
- CAA records are looked up with Google Public DNS, from the name up to its parent domains.
- Every connection goes to an address that was checked to be public. At most seven connections are made to the server, each with a short time limit.
- OCSP stapling, certificate revocation, Certificate Transparency and cipher suites are not checked. A pass here does not mean the server has no other security problems.
Read more: Let's Encrypt: how it works (opens in a new tab), Mozilla's recommended TLS settings (opens in a new tab) and RFC 8996 (TLS 1.0 and 1.1 deprecated) (opens in a new tab).
What you can do
-
Certificate name, issuer, key and expiry date
-
Chain check against trusted roots, with missing intermediates found
-
TLS 1.0, 1.1, 1.2 and 1.3 tested one by one
-
HTTP to HTTPS redirect, HSTS and CAA records
-
Plain-English fixes for Let’s Encrypt, Nginx and Apache
How to check an SSL certificate
-
Enter the website name
Enter a name such as example.com, or paste the https:// address. To check a mail server or another TLS port, add the port, such as mail.example.com:993.
-
Run the check
A quick Cloudflare security check runs first. The result appears in a few seconds, with every finding marked as passed, to improve, a problem or a note.
-
Fix the problems
Start with the problems. Each one says what was found, why it matters and how to fix it, with links to the matching free tools. Copy the summary or download the result as JSON.
What the SSL checker tests, and what it does not
The checker connects to the website the way a browser does and reads the certificates the server sends. It checks that the certificate covers the name you entered (a wildcard such as *.example.com covers www.example.com, but not example.com or a.b.example.com), that it is inside its dates, that its key and signature are strong, and that the chain leads to a root certificate browsers trust. A missing intermediate certificate is the most common reason a site works in one browser and fails in another.
TLS versions, redirects and HSTS
It then makes one connection for each TLS version, so you can see whether TLS 1.2 and TLS 1.3 are on and the deprecated TLS 1.0 and 1.1 are off. On port 443 it also checks that http:// redirects to HTTPS and whether the site sends HSTS; the HSTS checker explains that header in detail. CAA records show which certificate authorities may issue certificates for the domain.
Fixing what it finds
On most WordPress hosts the certificate is a free Let’s Encrypt certificate that the host renews; the fix is usually in the hosting panel’s SSL page. On your own server, the advice covers certbot, Nginx and Apache. The Nginx configuration tool and the .htaccess generator can write the HTTPS redirect and HSTS rules for you.
Know the limits
The checker does not test OCSP stapling, revocation, Certificate Transparency or cipher suites, and it checks one address of the name, so servers behind a load balancer can differ. A pass means the certificate and TLS setup look right from here; it does not mean the website has no other security problems.
Frequently asked questions
Is the SSL checker free?
Yes. There is no sign-up. A limit on how many checks one visitor can run each day keeps the tool available for everyone.
What is the difference between SSL and TLS?
TLS is the current name for the protocol that secures HTTPS; SSL is the older name that stuck. An “SSL certificate” is the certificate a server uses for TLS. All SSL versions are long retired, and the checker tests TLS 1.0 to 1.3.
Why does my site work in my browser but the checker says the chain is incomplete?
Some browsers download a missing intermediate certificate themselves, or remember it from another site. Many apps, older phones, other servers and some browsers do not, so they show an error. Install the full chain, for example fullchain.pem in Nginx.
How do I renew a Let’s Encrypt certificate?
Most WordPress hosts renew it for you; check the SSL or TLS page in your hosting panel. On your own server, certbot renews automatically: run sudo certbot renew --dry-run to test it, and sudo certbot renew to renew now, then reload the web server.
How do I turn off TLS 1.0 and TLS 1.1?
In Nginx, set ssl_protocols TLSv1.2 TLSv1.3; and reload. In Apache, set SSLProtocol -all +TLSv1.2 +TLSv1.3. Behind Cloudflare or another CDN, also set the minimum TLS version in its dashboard, because visitors connect to the CDN, not to your server.
Why does it say a TLS version was not tested?
The checker can only offer the versions its own TLS library allows. When it cannot offer TLS 1.0 or 1.1, or the server did not answer, the result says “not tested” instead of guessing.
Can I check a mail server or another port?
Yes: add the port after a colon, such as mail.example.com:993. These TLS ports can be checked: 443, 465, 993, 995, 2053, 2083, 2087, 2096 and 8443. The redirect and HSTS checks only run on port 443.
Is the name I check stored?
The result is not saved. A short summary (the domain and the headline numbers) is kept for an hour in case you choose to share it, then deleted; a result you share stays up as a public page for 12 months. To count how the tool is used, this site keeps the domain you checked (without a port or path) for 12 months, with the time, the outcome, your approximate location (country, region and city), the site you came from and your type of device and browser, but no IP address. The server you check sees the connections, as it does for any visitor.
Can I share my result?
Yes, for a website checked on port 443. Press Share result under the result to make a public page with its headline: the domain, the verdict, the date the certificate is valid until, who issued it, the TLS versions accepted and how many checks passed. Never anything about you. The page has its own preview image for Facebook, LinkedIn, X and WhatsApp, asks search engines not to list it and stays up for 12 months. You also get a link to remove it at any time: keep it, as it is shown only once. The page goes straight away; posts that already show it may keep the old preview for up to an hour. The privacy policy has the details.
Related tools
-
Check a site’s Strict-Transport-Security policy: max-age, includeSubDomains and preload.
-
Check a URL’s HTTP response headers and redirect chain.
-
SEO report
New (added recently)Check one page’s SEO basics and PageSpeed, then download the report as a PDF.
-
Email DNS
New (added recently)Build and test MX, SPF, DKIM, DMARC, MTA-STS and BIMI records, with the exact values for Google Workspace, Microsoft 365 and over 25 email services.