Skip to content

Free TLS version checker

See which TLS versions a website still accepts, and whether it supports TLS 1.3.

Connects on port 443 as a browser would. No login access needed. What happens to the domain you enter

Example report

example.com
  • 2 Medium
  • 1 Information
  • 4 passed
  • TLS 1.0 is enabledexample.comMedium

    example.com answered a ClientHello offering only TLS 1.0.

    Next step

    Configure the server to require TLS 1.2 or later.

    View fix guide

  • TLS 1.1 is enabledexample.comMedium

    example.com answered a ClientHello offering only TLS 1.1.

    Next step

    Configure the server to require TLS 1.2 or later.

    View fix guide

  • TLS 1.3 is not supportedexample.comInformation

    example.com refused a handshake that allowed TLS 1.3 alone.

    Next step

    Enable TLS 1.3 alongside TLS 1.2.

    View fix guide

What the TLS version check looks at

  • Negotiated version

    See the version a modern client gets: TLS 1.3 or TLS 1.2.

  • Obsolete versions

    Probe SSL 3.0, TLS 1.0 and TLS 1.1 one at a time.

  • TLS 1.3

    Check that TLS 1.3 is available alongside TLS 1.2.

  • Each name

    Test the domain and its www name on their own rows.

TLS 1.2 is only shown as accepted when it is the version negotiated; it is not tested on its own.

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.

  1. Enter your domain
  2. Review the findings
  3. Follow the fix guides
Example finding

TLS 1.0 is enabledMedium

The server accepted a TLS 1.0 connection.

Offered: TLS 1.0
Answer: accepted

Common TLS version issues you can put right

  • 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.

    Read the fix guide

  • TLS 1.3 is not supportedInformation

    TLS 1.2 on its own remains acceptable, but TLS 1.3 connects faster and drops legacy options. Current servers and CDNs support it.

    Read the fix guide

  • SSL 3.0 is enabledHigh

    The server accepted an SSL 3.0 connection.

    Read the fix guide

  • TLS 1.1 is enabledMedium

    The server accepted a TLS 1.1 connection.

    Read the fix guide

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.

  1. NewIssue detected
  2. FixedConfirmed by recheck
  3. ReopenedDetected again

How the check works

  • The version a modern client negotiates on port 443: TLS 1.3 or TLS 1.2.
  • Three separate probes, each a ClientHello offering a single obsolete version (SSL 3.0, then TLS 1.0, then TLS 1.1), and whether the server replies in that same version.
  • TLS 1.3 support, taken from the first handshake when it settled on 1.3, otherwise from a second handshake that permits TLS 1.3 alone.
  • Every name on its own row: the domain and its www. name, or the single subdomain entered.

Reading a result

The protocol version sets the rules for the whole connection: how keys are agreed, which ciphers are allowed and how the handshake itself is protected. SSL 3.0 is broken by the POODLE attack and was prohibited in 2015 (RFC 7568). TLS 1.0 and TLS 1.1 were deprecated in 2021 (RFC 8996), and current browsers no longer connect with them.

An old version left enabled rarely breaks anything for visitors, which is why it lingers. It still offers an attacker a weaker protocol to aim for, and baselines such as PCI DSS require early TLS to be turned off.

A pass on obsolete versions means all three probes were refused. A missing TLS 1.3 is reported as a hardening recommendation rather than a problem: TLS 1.2 with sound cipher suites remains acceptable, while TLS 1.3 connects in one round trip fewer and removes the legacy options behind past attacks.

What it does not do

  • TLS 1.2 is reported only when it is the version a modern client gets. Whether a server that prefers TLS 1.3 also accepts 1.2 is not tested.
  • Each obsolete-version probe offers a short list of suites common in that era. A server that accepts an old version only with a suite outside that list could be missed.
  • SSL 2.0 is not probed.
  • Mail servers, VPN gateways and other services that use TLS away from port 443 are outside this check.

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

Should I disable TLS 1.0 and TLS 1.1?
Yes. RFC 8996 retired both, and no current browser needs them. Anything that still depends on them is usually an old system, better upgraded than accommodated.
Do I need TLS 1.3?
It is recommended rather than required. TLS 1.2 with modern cipher suites is still acceptable, but TLS 1.3 is quicker to connect and leaves out options that caused earlier vulnerabilities. Current web servers and CDNs support it.
Why is TLS 1.2 shown as not tested?
When the server negotiates TLS 1.3, this checker does not open a separate TLS 1.2-only connection, so it cannot say whether 1.2 is also accepted. Most servers keep TLS 1.2 on for clients that lack 1.3.