Negotiated TLS version
The reported version belongs to the browser-to-Cloudflare connection. It describes a completed negotiation, rather than every TLS version this browser could support.
BrowserCheck · Browser environment diagnostics
TLS & HTTP Connection Test
Inspect the negotiated TLS version, cipher and HTTP protocol for this browser’s request to BrowserCheck at the Cloudflare edge.
This test makes a fresh request to BrowserCheck and reads connection metadata provided by Cloudflare. It shows what was negotiated for that request, with missing fields reported separately. No IP address, cookies or raw ClientHello are included in the result.
Results in this browser
Reading connection metadata…
Copied and printed output omits IP addresses, the full User Agent, exact versions, fingerprint hashes, and precise location.
What is tested and how to read it
Cipher suite
The cipher is the suite selected for this connection. This endpoint does not capture the browser’s full offered cipher list, extension order or signature algorithms.
HTTP protocol
HTTP/1.1, HTTP/2 or HTTP/3 is reported when the edge exposes it. Protocol selection can vary by connection, browser, network and service configuration.
Observation point
The TLS connection terminates at Cloudflare. The reported fields describe that edge connection; an origin server’s separate TLS connection is outside this measurement.
Test limitations
- These three fields do not produce a JA3 or JA4 fingerprint, identify a browser uniquely, or measure HTTP/2 frame settings.
- Local HTTP previews have no browser TLS handshake. Missing edge metadata is shown as unavailable, rather than replaced with a default TLS version.
- A proxy that terminates and recreates TLS may affect the observations. A matching result does not prove that every network request uses the same route.
Next steps
- Run the test on the HTTPS site, then repeat after changing one browser or network setting.
- Use environment snapshots to compare connection fields alongside browser and graphics observations. Share the safe summary when exact environment data is unnecessary.
Frequently asked questions
Is this a JA4 checker?
This first version reports basic TLS and HTTP connection metadata. JA4 needs additional handshake instrumentation or an eligible Cloudflare Bot Management service.
Why is TLS unavailable in a local preview?
A local HTTP request does not establish TLS. Development metadata can be simulated, so the tool does not treat it as a browser handshake measurement.
Does this rate my VPN or browser security?
No. It records a connection’s selected parameters and their measurement scope. It cannot establish VPN routing, certificate validation behavior or overall security.