Free SSL and TLS checker
Check your certificate and HTTPS settings, and find connection issues that need attention.
Example report
example.com- 1 Medium
- 1 Low
- 10 passed
TLS 1.0 is enabledexample.comMedium
example.com accepted a connection offering only TLS 1.0.
Next step
Configure the server to require TLS 1.2 or later.
Certificate expires soonwww.example.comLow
The certificate for www.example.com expires in 12 days.
Next step
Renew the certificate now, or check that automated renewal is working.
example.com
- HTTPS availability
- Certificate validity
- Certificate expiry
- TLS 1.3 support
- Cipher suites
www.example.com
- HTTPS availability
- Certificate validity
- TLS 1.3 support
- TLS protocol versions
- Cipher suites
Protocol versions
| Version | example.com | www.example.com |
|---|---|---|
| SSL 3.0 | Refused | Refused |
| TLS 1.0 | Accepted | Refused |
| TLS 1.1 | Refused | Refused |
| TLS 1.2 | Not tested | Not tested |
| TLS 1.3 | Accepted | Accepted |
Ironfang offers each obsolete version on its own and notes whether the server answers with it. TLS 1.2 is only shown as accepted when it was the version negotiated; it is not tested on its own.
Negotiated connection
example.com
- Protocol
- TLS 1.3
- Cipher suite
TLS_AES_128_GCM_SHA256- ALPN
- h2
www.example.com
- Protocol
- TLS 1.3
- Cipher suite
TLS_AES_128_GCM_SHA256- ALPN
- h2
The suite above is what a modern client gets. The weak-suite result below comes from a separate handshake that offers only broken or weak suites (RC4, DES, 3DES, NULL, export and anonymous) and notes whether the server accepts one.
What the SSL and TLS check looks at
HTTPS
Check that the site answers over TLS on the domain and its www name.
Certificate
Check trust, the names covered and the days left before it expires.
Protocol versions
Find SSL 3.0, TLS 1.0 or TLS 1.1 still accepted, and check TLS 1.3 support.
Cipher suites
Find broken suites such as RC4, 3DES or export-grade still accepted.
Where a CDN or proxy handles TLS, the results describe that edge, not the origin server behind it.
Understand the issue and your next step
Each finding explains what we found, why it matters and what you can change. Start with the issues that need attention, then open the evidence when you want the detail.
- Enter your domain
- Review the findings
- Follow the fix guides
TLS 1.0 is enabledMedium
The server accepted a TLS 1.0 connection.
TLS 1.0: acceptedTLS 1.0 is obsolete and was formally deprecated in 2021. It lacks modern protections, and PCI DSS and most security baselines require it to be disabled.
Configure the server to require TLS 1.2 or later. For nginx use ssl_protocols TLSv1.2 TLSv1.3;; for Apache SSLProtocol -all +TLSv1.2 +TLSv1.3. CDNs usually have a minimum TLS version setting.
Common TLS issues you can put right
Certificate has expiredHigh
Every visitor sees a full-page browser warning until a renewed certificate is installed. Automatic renewal keeps it from happening again.
TLS 1.0 is enabledMedium
TLS 1.0 has known weaknesses and current browsers no longer use it. Find out whether anything still depends on it, then turn it off at the server or CDN.
Website is not available over HTTPSHigh
The site answers on HTTP but HTTPS connections failed.
Certificate is not trustedHigh
The certificate chain does not lead to a publicly trusted certificate authority.
Certificate does not cover this hostnameHigh
The certificate presented is not valid for the hostname that was requested.
Weak cipher suites acceptedMedium
The server accepted a connection using a cipher suite that is considered broken or weak.
Keep watch after you've fixed it
Ironfang Security rechecks a verified domain every week or every day and tells you what changed: new findings, fixes and certificates nearing expiry.
Free during the preview. Domain verification required.
- NewIssue detected
- FixedConfirmed by recheck
- ReopenedDetected again
How the check works
- A TLS 1.2 or 1.3 handshake on port 443 with the domain and its
www.name (or only the name you enter, for a subdomain), recording the version, cipher suite and ALPN protocol agreed. - The certificate served for each name: trust, hostname coverage, validity dates and the days left before it expires.
- Whether the server answers a client that offers only SSL 3.0, only TLS 1.0 or only TLS 1.1.
- Whether TLS 1.3 is available, using a second handshake that allows nothing older when the first one settled on TLS 1.2.
- Whether the server picks a suite from a list made up entirely of broken ones: RC4, DES, 3DES, NULL, export-grade and anonymous.
Reading a result
SSL (Secure Sockets Layer) was the first protocol for encrypted web traffic. TLS (Transport Layer Security) replaced it in 1999, and SSL 2.0 and SSL 3.0 have both since been prohibited (RFC 6176, RFC 7568). A browser showing a secure connection today is using TLS 1.2 or TLS 1.3. "SSL" survives in product names and in "SSL certificate", which means the certificate a TLS server presents.
Results are listed per host, because the bare domain and its www. name can be served by different machines with different certificates. A pass means that one check found nothing to report. It does not show that the site, or the server behind it, is secure.
Certificate findings tend to be the urgent ones: an expired, untrusted or wrongly named certificate puts a full-page browser warning in front of every visitor. Obsolete versions and weak suites are less visible but hand an attacker on the network path known weaknesses to work with. A missing TLS 1.3 is a recommendation, since TLS 1.2 on its own remains acceptable.
What it does not do
- Only port 443 is tested, at one address per host (IPv4 first). Other addresses behind the same name, and TLS on other ports such as mail or admin services, are not checked.
- Where a CDN or reverse proxy terminates TLS, the results describe that edge, not the origin server behind it.
- The cipher test offers a fixed list of broken suites rather than listing everything the server supports, and TLS 1.2 is not tested on its own.
- HTTP behaviour on top of TLS, such as the redirect from plain HTTP and the
Strict-Transport-Securityheader, belongs to the HSTS and security headers checkers.
What happens to the domain you enter
The check runs from Ironfang Security's published scanner address with the same low-impact limits as a scan. Nothing you enter is stored or logged. A result is reused for five minutes, and a certificate log search for an hour, so a repeat check is quick and the domain is not checked again.
Guides
A few things worth knowing
- Is SSL the same as TLS?
- Not quite. TLS is the protocol that succeeded SSL, and every SSL version is now prohibited. People still say SSL out of habit, so an SSL checker in practice tests TLS.
- Does an SSL checker test my server or my CDN?
- Whatever answers on port 443 for the name. If a CDN or proxy handles TLS for the site, the results describe its configuration; the connection from it to your origin server cannot be seen from outside.
- Is a site with a valid certificate safe?
- A valid certificate shows that the connection is encrypted to a server holding a certificate for that name. It says nothing about the site itself, its software or how it handles data.

