GEARCHECK LABMake three small same-origin requests and inspect the connection protocol your browser reports for them.
READY — choose an action below
No measurement yet.
The nextHopProtocol value comes from Resource Timing for a completed request. Common values include http/1.1, h2 and h3; an empty value is shown as unavailable. The result describes this connection to GearCheck Lab, not every site you visit or the entire network path. HTTP/3 support does not force a particular request to use it. Connection reuse, intermediaries and browser policy can change the negotiated protocol. Response timing includes the browser and server path rather than just a protocol handshake.
This cannot reveal all TLS settings, certify encryption strength or prove that a router supports a particular protocol. Missing timing data is not a failed connection. The test uses unique request URLs and reads only its own resource-timing entries, preserving unrelated page timing. Stop and hiding the tab cancel pending requests. No external domains or local files are probed; the requests contain only a generated test identifier.
Device previews, recordings, selected files and report notes stay in your browser. Downloaded files remain on your device. Network tests send generated probes to GearCheck Lab. DNS lookup sends your requested public domain name and type to our server and the Cloudflare public resolver only after you start a query. Local recordings, drawings, files, device names and battery logs are not uploaded. Ordinary page requests and usage measurement are described in our privacy policy.