How to use
- Enter
example.comorhttps://example.com/app.jsunder Address to check. If you add a path, that file is checked, and the port is fixed at 443. - Pick one or more regions. South Korea is the default. Sites behind a CDN can differ by region, so comparing several is useful.
- Press Check HTTP/2 and HTTP/3. A probe in each region tries to connect with HTTP/2.
- In the table, read per-region HTTP/2 support, the HTTP/3 (h3) advertisement from alt-svc, TLS version, status code, time and server header.
- Read the support status and next steps under What it means, and use Copy result to take the text.
How it decides
HTTP/2: the tool asks the measurement service to use the HTTP2 protocol option. If the server accepts HTTP/2 a response comes back, and the first line of that response (for example HTTP/2.0 200) tells which version was actually negotiated. If the server does not support HTTP/2, ALPN (application protocol negotiation) is rejected during the TLS handshake and the attempt ends in an error without any response. The tool reports that case as “HTTP/2 seems unsupported”. It says so only when the error text looks like a rejected negotiation, and other failures such as timeouts or refused connections are shown as “Failed”.
HTTP/3: HTTP/3 runs over QUIC on UDP instead of TCP, so this tool does not open that connection itself. It reads the alt-svc response header, where a server announces that “h3 is also available”. Browsers use the same announcement to try HTTP/3 on the next visit.
Sample results (October 2026, from a South Korea probe; site settings can change):
| Site | Negotiated | alt-svc |
|---|---|---|
| www.google.com | HTTP/2 | h3=":443"; ma=2592000 and h3-29 |
| example.com | HTTP/2 | h3=":443"; ma=86400 |
| www.naver.com | HTTP/2 | none |
| www.nate.com | HTTP/2 negotiation rejected (ALPN error), seems unsupported | n/a |
The ma value in alt-svc is how many seconds the advertisement may be remembered: 2592000 is 30 days and 86400 is 1 day. Names such as h3-29, with a suffix, are draft versions from before the specification was final, and browsers now use only the final h3.
HTTP versions and how to enable them
| Version | Transport | Notes |
|---|---|---|
| HTTP/1.1 | TCP | Requests go one after another per connection, so browsers open several connections |
| HTTP/2 | TCP + TLS | Many requests share one connection, and headers are compressed |
| HTTP/3 | UDP (QUIC) | A lost packet does not block other requests, and connections start faster |
- On a web server: in nginx add
http2 on;(1.25.1 or later) or uselisten 443 ssl http2;. In Apache enable mod_http2 and setProtocols h2 http/1.1. - HTTP/3 needs a server or CDN with QUIC support and UDP port 443 open. If you do not run the server yourself, switching on the HTTP/3 option in your CDN settings is easier.
- HTTP/2 is used only over TLS, so a certificate problem breaks it too. Check the certificate with the SSL Checker first.
What is sent, and the limits
- The address you enter is sent to the measurement service Globalping, and the probe IP is logged by the target server. See the privacy policy for details. Results are not stored.
- Private and internal addresses are not measured, and there is an hourly request limit.
- This sends one HEAD request per region for one address as a checking tool. It is not meant for generating load or scanning, and it never repeats automatically.
- For HTTP/3 only the advertisement is checked. If a firewall blocks UDP 443, the connection can still fail even when the advertisement exists.
- To see all response headers use the HTTP Header Viewer, and for compression settings the Gzip and Brotli Checker.
Frequently asked questions
If HTTP/2 is not supported, does the site fail to open?
No. Browsers fall back to HTTP/1.1 automatically, so the site opens normally. Pages with many images and scripts are often faster over HTTP/2, so enabling it is worthwhile. This tool asks for HTTP/2 and reports “unsupported” when that is rejected.
Without alt-svc, can HTTP/3 not be used?
If the server does not advertise HTTP/3, browsers do not try it, so it is effectively off. To turn it on, enable HTTP/3 in the server or CDN and make sure the response carries alt-svc: h3=":443".
The result differs by region.
Sites behind a CDN are answered by a nearby server in each region, and servers can be configured differently. If only some regions are unsupported, check the server or CDN settings there.
The status code is 301 or 302.
That response sends visitors elsewhere. The HTTP version is still the one read from that response, but the final address (for example the www one) may be configured differently, so check it as well. The Redirect Checker shows the path.
Which version did my own browser use?
Open the Network tab in your browser developer tools and look at the Protocol column (h2, h3 and so on). This tool shows what a probe got, which can differ from your environment.
The address you enter is sent to an outside measurement service (Globalping) and is never stored on this site’s servers.