HTTP/3 is the newest version of the protocol behind every web page. It runs over QUIC, a transport built on UDP instead of TCP, and has been a standard since June 2022. Four years on, how many of the web’s biggest sites actually offer it? We checked the top 10,000 domains, the same list behind our IPv6 adoption study, and looked at what it means for anyone sending traffic through a proxy.
The headline numbers
Of the 10,000 domains, 7,873 answered a web request. The rest are mostly infrastructure domains with no website.
| Signal | Sites | Share |
|---|---|---|
| Offer HTTP/3 by either method | 2,812 | 35.7% |
| Alt-Svc header lists h3 | 2,791 | 35.5% |
| DNS HTTPS record lists h3 | 1,601 | 20.3% |
| Both | 1,580 | 20.1% |
| Any DNS HTTPS record | 2,747 | 34.9% |
About a third of top sites offer HTTP/3. Almost all of them say so in the Alt-Svc header; only 21 rely on the DNS record alone.
That is in line with other measurements. W3Techs puts HTTP/3 at 41.2% of websites, using its own method and site list. The HTTP Archive’s 2024 Web Almanac found “around 27% of all websites” announcing HTTP/3 through Alt-Svc, across a far larger and less popular set of sites.
Cloudflare does most of the work
| Who serves the site | Sites | Offer HTTP/3 |
|---|---|---|
| Cloudflare | 2,724 | 61% |
| Amazon CloudFront | 877 | 31% |
| Akamai | 571 | 26% |
| Fastly | 356 | 25% |
| Google’s own servers | 163 | 100% |
| Own servers or other providers | 3,182 | 15% |
Cloudflare sites account for 1,651 of the 2,812 sites with HTTP/3, or 59%. That reflects a default: Cloudflare says HTTP/3 “is on by default for zones using Cloudflare’s free tier of service, while paid customers have the option to activate support.” On Fastly and Akamai, it is a setting customers turn on. Without Cloudflare, only 22.5% of top sites offer HTTP/3.
Sites on their own servers lag furthest behind. Popular web servers either need extra configuration for HTTP/3 or do not support it out of the box, and it also means opening UDP port 443 in the firewall.
Big names, split down the middle
The top 100 sites lead, at 47%, but the rest of the list is flat:
| Rank | Sites that answered | Offer HTTP/3 |
|---|---|---|
| Top 100 | 74 | 47.3% |
| 101 to 1,000 | 660 | 37.6% |
| 1,001 to 5,000 | 3,050 | 34.1% |
| 5,001 to 10,000 | 4,089 | 36.4% |
Among the biggest brands, the split is clear:
| Offer HTTP/3 | Do not |
|---|---|
| Google, YouTube, Facebook, Instagram, WhatsApp, Amazon, LinkedIn, X, Bing, Pinterest, Zoom, Vimeo, Adobe, OpenAI | Microsoft, Apple, GitHub, Wikipedia, Netflix, TikTok, Yahoo, Spotify, Roblox, Baidu, Yandex, ChatGPT, WordPress.com, Mozilla |
Some results are a matter of setup, not of the company. OpenAI’s main site advertises HTTP/3; chatgpt.com, also on Cloudflare, does not.
We also found 453 sites, 16% of those with HTTP/3 headers, still advertising draft versions such as h3-29 alongside the final one. Browsers ignore them, but they show how many configurations were set up years ago and never revisited.
Why HTTP/3 matters
Google’s 2017 paper on QUIC, the protocol HTTP/3 grew from, reported that it “reduces latency of Google Search responses by 8.0% for desktop users and by 3.6% for mobile users, and reduces rebuffer rates of YouTube playbacks by 18.0% for desktop users and 15.3% for mobile users.” The gains come from faster connection setup, better recovery from lost packets and the ability to keep a connection when a phone switches from Wi-Fi to mobile data.
The gains are not universal. In a 2020 test, Cloudflare found that for a real page HTTP/3 “still trails HTTP/2 performance, by about 1-4% on average in North America”. Our Core Web Vitals study shows that slow servers and heavy scripts usually matter far more.
There is also a catch in how browsers find HTTP/3. As the Web Almanac puts it, “HTTP/3 is typically only used from the second page load of a site onward”. The first visit uses HTTP/2 or HTTP/1.1 and only learns about HTTP/3 from the Alt-Svc header. The DNS HTTPS record fixes that, which is one reason to publish it.
What HTTP/3 means for proxies
Most proxies, including ours, work by opening a TCP tunnel to the website. That is what HTTP CONNECT does, and it is what SOCKS5 does in browsers: Chrome’s documentation says SOCKS5 “is only used to proxy TCP-based URL requests. It cannot be used to relay UDP traffic.” curl’s manual is just as plain: “curl cannot do HTTP/3 over any proxy.”
So traffic through a standard proxy reaches the website over HTTP/2 or HTTP/1.1, never HTTP/3. In practice, that is not a problem:
- Every site still speaks TCP. All 2,812 sites that offered HTTP/3 in our scan answered our request over TCP. HTTP/3 is an extra option, not a replacement.
- TCP is the normal fallback. Many company firewalls block UDP port 443 on purpose. Palo Alto Networks’ guidance says “Blocking QUIC forces the browser to fall back to TLS and enables the firewall to decrypt the traffic.” Sites have to work without HTTP/3, and they do.
- Consistency matters more than the version. Sites do look at how clients connect, as our guide to TLS and HTTP/2 fingerprinting explains. A client that presents itself as Chrome should connect the way Chrome does over a TCP connection.
Proxying HTTP/3 itself needs newer standards from the IETF’s MASQUE group: CONNECT-UDP (RFC 9298) and CONNECT-IP (RFC 9484). Apple’s iCloud Private Relay uses them, describing MASQUE as “a way of using HTTP/3 and QUIC as secure proxying technologies,” and Cloudflare began rolling it out in its WARP app in late 2024. For most web scraping and testing work, a standard HTTP or SOCKS5 proxy remains the right tool. Our comparison of HTTP and SOCKS5 proxies covers when to use which.
How we did it
On 20 November 2026 we took the top 10,000 domains in the Tranco ranking (list Q2K34). For each one we requested the home page at the www address, then the bare domain, following redirects, with a Chrome user agent, and recorded the Alt-Svc header on the final response. We then queried the DNS HTTPS record (type 65) for the final host through 1.1.1.1. A site counted as offering HTTP/3 if either listed h3, including draft versions. We identified the provider from response headers, so sites behind more than one provider are counted under the one that answered. We checked what sites advertise, not whether a QUIC connection succeeded, and a site may advertise HTTP/3 on other pages but not its home page.
The bottom line
About a third of the web’s top 10,000 sites offer HTTP/3, and Cloudflare’s defaults account for well over half of them. Many of the biggest names, including Microsoft, Apple, Wikipedia and Netflix, still do not. For teams using proxies, the practical message is simple: standard proxies carry traffic over TCP, every site still supports it, and that is what residential proxies and most other tools will keep using until MASQUE becomes common.
Sources and references
- IETF, RFC 9114, HTTP/3 (June 2022): rfc-editor.org
- IETF, RFC 9000, QUIC (May 2021): rfc-editor.org
- IETF, RFC 9460, SVCB and HTTPS DNS records (November 2023): rfc-editor.org
- IETF, RFC 9298, Proxying UDP in HTTP (August 2022): rfc-editor.org
- IETF, RFC 9484, Proxying IP in HTTP (October 2023): rfc-editor.org
- W3Techs, usage statistics of HTTP/3: w3techs.com
- HTTP Archive, Web Almanac 2024, HTTP chapter: almanac.httparchive.org
- Cloudflare, Radar 2025 Year in Review: blog.cloudflare.com
- Cloudflare, HTTP/3 usage one year on (June 2023): blog.cloudflare.com
- Cloudflare, Comparing HTTP/3 vs. HTTP/2 performance (April 2020): blog.cloudflare.com
- Langley et al., The QUIC Transport Protocol: Design and Internet-Scale Deployment (SIGCOMM 2017): research.google
- Chromium, proxy support in Chrome: chromium.googlesource.com
- curl manual: curl.se
- Palo Alto Networks, PAN-OS 10.0, define traffic to decrypt: docs.paloaltonetworks.com
- Apple, iCloud Private Relay overview (December 2021): apple.com
- Cloudflare, MASQUE now powers 1.1.1.1 and WARP apps (December 2024): blog.cloudflare.com
- Tranco, list Q2K34: tranco-list.eu