About this http/2 checker
HTTP/2 lets a browser load many files over one connection and compresses headers, which usually makes pages load faster than HTTP/1.1. A server only uses it over HTTPS, after the client and server agree on a protocol during the TLS handshake with an extension called ALPN. This checker performs that negotiation from our server, offering HTTP/2 first, and reports exactly which protocol the server chose.
If the answer is HTTP/1.1, the server does not offer HTTP/2, or a proxy in front of it removed the option. That is common on old hosting plans and on servers where an outdated TLS library or configuration is in use. The tool also reads the Alt-Svc header, which is how a site announces HTTP/3 over QUIC. It reports that hint only; it does not open a QUIC connection.
The result also shows the final status code, the response time and the server header. The address you enter is sent to our API at /api/http2-checker.php and tested from our server. Private addresses are refused, up to three redirects are followed, and searches are not stored by the app.
Which controls should I check first?
The HTTP/2 Checker form labels its controls as Website address. Use those labels to keep the source and settings separate. A sample argument that selects a mode is not additional source text. Choose the setting matching your intended operation before copying a result, and change it explicitly when comparing another mode. The labels describe what this form accepts; the worked examples below demonstrate only the stated supplied values.
How should I interpret this specific operation?
Protocol negotiation belongs to the specific connection used for the check. An HTTP/2 result is evidence about that attempt, not every hostname, path or client. TLS settings, proxies and client capabilities can affect negotiation. Keep the queried address and reported protocol together. If the result differs from another client, compare the connection context before changing server settings. A prepared request-helper example does not perform negotiation and cannot prove HTTP/2 support.
Worked helper values
These values come from the reproducible calculation examples supplied with this tool. Each row identifies the complete supplied arguments and the returned value. A visible ↵ denotes a line break and ⇥ denotes a tab in text examples. Settings appear alongside source data so that a different mode is not mistaken for an identical input. These are helper calculations, not observations of a live device, fetched target, image decoder, browser preview or downloaded file. Use the stated method above to relate the returned fields to the actual operation.
| Supplied values | Calculated return value |
|---|---|
| http2-checker; a b.com | /api/http2-checker.php?q=a%20b.com |
| example.com ; x | example.com |
Whose network view does this result represent?
A server-side check observes the target from the checking service's network location. Your browser, a mobile connection and another resolver can see different answers because of caching, geolocation, routing, filtering or load balancing. Keep the exact queried target and the time of your check when comparing observations. A timeout means this attempt did not obtain a result within its limit; it does not prove the target is unavailable everywhere. To investigate a discrepancy, compare the same target and protocol from the relevant client environment as a separate step.
How should I prepare a target?
Use a public target whose spelling and scope you can explain. A hostname, an IP address and a complete URL carry different information. A URL includes a scheme, path and possibly a query string, while a hostname identifies a host without those request details. Follow this page's stated input convention and omit credentials or confidential query values from demonstration targets. Correct an invalid-target message before retrying. The address is sent to the checking service for processing, so this workflow is different from a local parser that merely splits the supplied text into components.
What can I infer from missing fields?
A missing field can reflect the target, the available response or the check's scope. It should not be replaced with a guessed value. Read any status or explanation beside the output and distinguish an empty answer from an error. Compare the same type of evidence across repeated checks rather than treating every field as an independent verdict. A registration record, resolver result and HTTP response describe different layers and can disagree without any of them being fabricated. Follow a discrepancy to the layer it concerns before changing DNS, application settings or certificate configuration.
How can I document a reproducible observation?
Record the exact input, result fields that matter, and any timeout or error text. If the target is a URL, preserve the path and protocol because checking the homepage can differ from checking a specific resource. When a value appears to change, repeat a narrowly scoped check and compare the complete response, including intermediate context if the tool exposes it. Avoid attributing a difference to a named provider or person based only on one field. These outputs are observations from a limited check, not a record of ownership or an exhaustive audit of every configuration on the target.
Is HTTP/2 faster than HTTP/1.1?
Usually yes for pages with many files, because requests share one connection. Gains are small for a single large download.
What if my site shows HTTP/1.1?
Enable HTTP/2 in your web server or hosting panel, or in your CDN. Most current platforms support it by default.
Does this prove HTTP/3 works?
No. It reports whether the Alt-Svc header advertises HTTP/3. Browsers decide whether to connect with it.
Why HTTPS only?
Browsers only use HTTP/2 over TLS, so a plain http check would not be meaningful.