TLS & HTTP/3 Details
Inspect TLS negotiation details and HTTP/3 availability from the edge.
What this tool shows
It reports TLS version, cipher suite, ALPN, and whether HTTP/3 is available.
These signals help explain performance, compatibility, and policy differences across networks.
How the data is collected
The measurements are taken at the edge during the TLS handshake.
They reflect the last hop between your client and the edge, not the full path.
Why HTTP/3 can be off
Some networks, proxies, or middleboxes block QUIC/HTTP/3 for policy or compatibility reasons.
Browser support and enterprise security rules can also downgrade the protocol.
What to check when results look odd
Compare results across VPN on/off to see if a gateway is altering TLS behavior.
If cipher suites differ from expectations, confirm whether an inspection proxy is in place.
Limitations
Edge results do not show internal LAN devices or all upstream hops.
Retest after browser updates, VPN changes, or network switches.
Operational tips
Use this tool alongside the TLS fingerprint test to validate client consistency.
Keep a baseline snapshot so you can spot protocol downgrades later.