TLS Version & Cipher Viewer
See the TLS version and cipher suite this connection actually negotiated.
Where this comes from
The version and cipher suite negotiated for the connection that fetched this page are read from the edge. The distinction worth holding is that this is a negotiation rather than a property of your browser: a client offers what it supports and the server picks, so seeing TLS 1.2 tells you about this pair rather than about your browser. TLS 1.3 is the meaningful improvement — it removed every cipher suite with a known weakness rather than deprecating them gradually, and it completes the handshake in one round trip instead of two, which is a visible speed difference on a high-latency connection.
What the results mean
- TLS version
- What this pair negotiated. 1.3 is current; 1.2 is still secure and widely used.
- Cipher suite
- The algorithms chosen for this connection. TLS 1.3 offers a deliberately short list with nothing weak in it.
- HTTP protocol
- Which HTTP version rides on top. HTTP/3 requires TLS 1.3.
- Certificate
- Not covered here. A separate question from the channel.
Common problems and fixes
- I get TLS 1.2 and expected 1.3
- The server chose it. Your browser offers 1.3 and a server that does not support it will settle on 1.2, which is still secure.
- How do I disable old TLS versions?
- On a server, not a browser — modern browsers already refuse 1.0 and 1.1. On a server it is a configuration change, and the SSL checker will show what a given host accepts.
- Is TLS 1.2 a problem?
- No. It remains secure when configured with modern cipher suites. TLS 1.3 is better because it removes the weak options entirely rather than leaving them available to misconfigure.
Frequently asked questions
What is the difference between TLS 1.2 and 1.3?
1.3 removed every cipher suite with a known weakness rather than deprecating them slowly, and it completes the handshake in one round trip rather than two — which is a noticeable speed difference on a high-latency connection.
Why does my version differ between sites?
Because it is negotiated. Your browser offers what it supports and each server picks from that, so the answer describes the pair rather than you.
Does a modern TLS version mean the site is safe?
No. It means the channel is encrypted properly. Whether the site at the other end is who it claims to be is the certificate's job, and whether it is trustworthy is neither.
Put this on your own site
Free to embed, no attribution required beyond the source link the frame carries itself. It runs entirely in your visitor's browser, sets no cookies and loads no third-party script.
<iframe src="https://runthetests.com/embed/tls-version-check/" width="100%" height="560" style="border:1px solid #e5e5e5;border-radius:8px" title="TLS Version & Cipher Viewer" loading="lazy"></iframe>
Preview it at https://runthetests.com/embed/tls-version-check/. Embedded pages are marked noindex, so yours stays the canonical copy — not this one.