Notes

Check whether a site uses HTTP/3

Check client support, inspect HTTP/3 advertisements, then confirm the actual connection protocol with curl or browser DevTools.

An Alt-Svc header advertising h3 means a server offers HTTP/3; it does not prove that your request used it. Confirm the negotiated protocol in curl’s output or the browser’s Network panel. Test from the network where the problem occurs, because HTTP/3 needs a working UDP path.

Check the client first

curl --version
curl --http3-only --max-time 15 -o /dev/null \
  -w 'HTTP version: %{http_version}\n' https://example.com/

Look for HTTP3 in curl’s Features line. A recent version number alone is insufficient: HTTP/3 depends on the libraries and features selected at build time. The local curl 8.18.0 build lists HTTP2 but not HTTP3. Its actual output is:

curl: option --http3-only: the installed libcurl version does not support this

That error describes the client, before it tests the website. On an HTTP/3-enabled build, --http3-only requires HTTP/3 and does not fall back to TCP. A successful result should report version 3. The general curl manual documents the option and write-out variable.

Separate discovery from use

curl -sS -D - -o /dev/null --max-time 15 https://cloudflare.com/

A representative header looks like this; values vary by site and time:

Alt-Svc: h3=":443"; ma=86400

It advertises an alternative service for the same origin, at UDP port 443, with an advertisement lifetime of 86400 seconds. The original origin still controls certificate verification. An alternative host or port does not let the peer present an unrelated certificate.

On a capable curl build, compare these probes:

curl --http3 --max-time 15 -o /dev/null \
  -w 'HTTP version: %{http_version}\n' https://cloudflare.com/
curl --http3-only --max-time 15 -o /dev/null \
  -w 'HTTP version: %{http_version}\n' https://cloudflare.com/

--http3 attempts QUIC while allowing a TCP fallback. A successful request reporting 2 therefore does not establish HTTP/3 connectivity. --http3-only removes that ambiguity, but a timeout still has several possible causes: blocked UDP, an unreachable alternative endpoint, server configuration or routing. Compare another network and server-side logs before assigning blame. Curl’s HTTP/3 guide explains build support and fallback.

Confirm in the browser

Open DevTools, select Network, enable the Protocol column and reload. Look at the actual document or resource row for h3; other rows can use h2 or HTTP/1.1 because they come from different origins or connections. A later navigation may use HTTP/3 after an earlier TCP response taught the browser an Alt-Svc advertisement. Proxies, enterprise policy and cached connection state also affect the result.

Check HTTPS DNS records

dig cloudflare.com. HTTPS

An HTTPS record can advertise an alpn value containing h3 before the first HTTP response. A supporting client can discover QUIC without first learning Alt-Svc over TCP. That saves a discovery step; it does not bypass TLS authentication, guarantee client support, or make UDP pass through a firewall. Address hints are connection hints, not a substitute for all address resolution rules. See RFC 9460.

For the discovery and transport sequence, use the HTTP/3 dive. For interpreting the DNS answer, use the DNS record dive.