HTTP/2 Test
Check whether a site negotiates HTTP/2 over TLS, or still answers with HTTP/1.1.
- Runs on our servers
- Free to use
About this tool
The HTTP/2 Test connects to the host over TLS, offers h2 through ALPN and reports which protocol the server picked. It is a one-second way to confirm that your web server, load balancer or CDN really delivers HTTP/2 to visitors, which is not always the case even when the option is switched on.
Combine it with the Gzip and Brotli tests for a quick performance checklist.
How to use it — quick steps
- 01
Enter the url
Type or paste the url in the field above, for example https://www.example.com/
- 02
Press "Test HTTP/2"
Press "Test HTTP/2" or Ctrl + Enter. The result appears below in a few seconds. Results can be copied.
- 03
Read the result
It appears in the dark panel under the form in a few seconds. Every block has [copy] and other actions.
Key features of this tool
External lookups
The lookup runs from our infrastructure, so you see what the public internet sees without exposing your own IP address or network.
Fast and cached
Results come back in seconds; identical lookups are cached for a few minutes to keep the service fast and responsive for everyone.
Easy to reuse
Every result block can be copied with one click or downloaded as a text file, and tables can also be saved as CSV for your reports.
Frequently asked questions
Why does HTTP/2 matter?
Multiplexing, header compression and server-side prioritisation make pages with many assets load noticeably faster, especially on high-latency connections.
My server has HTTP/2 enabled but the test says no
HTTP/2 is negotiated with ALPN during the TLS handshake. Old OpenSSL builds, a proxy in front of the server, or a CDN setting can prevent the h2 token from being offered.
What about HTTP/3?
HTTP/3 runs over QUIC/UDP and needs a separate check; the APIVoid HTTP3 Status API covers it.