HTTP Protocol Checker
Report the negotiated HTTP protocol for a real request.
Run the http protocol checker
Public website checkWhat http protocol checker helps you do
Report the negotiated HTTP protocol for a real request. HTTP/2 can multiplex requests over one connection. A site still needs efficient resources; a protocol upgrade will not remove unused scripts or reduce oversized images.
Prepare a useful input
Example input: https://example.com/ Save the original input alongside the result so another person can reproduce the check and judge whether a proposed change addresses the same page or file.
Read the result before making changes
Protocol negotiation depends on the requesting client and connection path; this does not test every visitor or HTTP/3 support. Record the checked URL and observation time. Compare the evidence with the intended page behavior, then verify the affected page again after a change instead of assuming the issue is resolved.
Avoid treating the protocol as a performance score
A site delivered over HTTP/2 can still transfer a large JavaScript bundle and wait on slow application data. Record the negotiated protocol, then measure the resources and execution work that affect the actual page. A proxy, load balancer or client capability can change the result, so compare like-for-like requests when investigating configuration. HTTP/2 support does not imply HTTP/3 support and should not be described as a complete transport audit. If the observed protocol differs from the hosting configuration, inspect the edge connection as well as the origin connection before deciding which layer needs a change.
Verify the result and continue
Record whether the observation came from the public edge URL or another endpoint. If hosting advertises one protocol but the check sees another, investigate connection negotiation before changing application code. Evaluate protocol findings alongside actual request behavior rather than using a version number as a speed grade. Continue with the page request counter or explore the performance tool cluster.
How this tool works
Report the negotiated HTTP protocol for a real request. The server fetches the submitted public URL with bounded redirects and response sizes. The result reports observed HTML, headers or network evidence for this specific check.
What the result does and does not establish
Protocol negotiation depends on the requesting client and connection path; this does not test every visitor or HTTP/3 support.
Use this check as part of a repeatable website review. Record what you found, make a specific change and run the same check again.
Browse all toolsContent and technical review workflow