For twenty years, IPv6 has been the future of the internet. In 2026 it is roughly half of the present. About half of Google’s users now reach it over IPv6, and IPv4 addresses are scarce enough that clouds charge for each one. But how much of the web itself can you actually reach over IPv6?
On 17 November 2026 we tested the top 10,000 domains in the Tranco ranking, the same list we used for our llms.txt study. For each site we looked up its IPv4 and IPv6 addresses and opened a real encrypted connection over each. This is what we found, and what it means if you are thinking about cheap IPv6 proxies.
The headline numbers
| Count | Share | |
|---|---|---|
| Domains tested | 10,000 | |
| Running a website | 8,008 | |
| Publishing an IPv6 address | 4,052 | 50.6% |
| Actually answering over IPv6 | 4,013 | 50.1% |
| Publishing IPv6 that does not work | 39 | 0.5% |
IPv6 on one of the bare domain or www, but not both | 1,136 | 14.2% |
Half of the top websites work over IPv6. A small number advertise an IPv6 address that fails, which is the worst case: visitors on IPv6 networks can see slow loads while their device falls back to IPv4. And one in seven sites supports IPv6 on only one of its two usual addresses, often www but not the bare domain.
The biggest sites lead
| Rank | Websites | Working over IPv6 |
|---|---|---|
| Top 100 | 74 | 71.6% |
| Top 1,000 | 742 | 53.0% |
| 1,001 to 5,000 | 3,110 | 50.0% |
| 5,001 to 10,000 | 4,156 | 49.7% |
Wider samples are lower still. W3Techs, which tracks millions of sites, put IPv6 at 33.0% of websites in November 2026. The further you go from the top of the web, the less IPv6 there is.
Who is still IPv4 only
Some of the most-used sites on the internet had no IPv6 address at all on their main domain:
| IPv6 | Sites |
|---|---|
| Yes | Google, YouTube, Facebook, Instagram, Amazon, Microsoft, Apple, Netflix, Wikipedia, Reddit, LinkedIn, ChatGPT, Spotify, WhatsApp, Telegram |
| No | GitHub, X, TikTok, Pinterest, Twitch, PayPal, Stripe, Shopify, eBay, Walmart, Discord, Baidu |
Payments and commerce stand out: PayPal, Stripe, Shopify, eBay and Walmart were all IPv4 only. GitHub’s absence is the best known; a community request for IPv6 support for cloning repositories has been open since January 2022.
By domain ending, government sites lead: 81% of .gov websites worked over IPv6, and 66% of .org. Russian .ru sites were at 9%, Japanese .jp at 19% and Italian .it at 28%.
The CDNs did most of the work
Most sites did not move to IPv6 on their own. When we looked up who runs the IPv6 addresses, at least 73% belonged to five networks: Cloudflare (41%), Akamai (11%), Amazon (11%), Google (6%) and Fastly (4%). Content delivery networks turn on IPv6 for every customer, so a site gets it the day it moves behind one. That also explains the gaps: sites that run their own front ends, as many payment companies do, have to do the work themselves.
Why IPv4 still matters
IPv4 has been out of new supply for years. The European registry, RIPE NCC, ran out on 25 November 2019. Addresses now trade on a market, at about $14 to $24 each in October 2026 depending on block size, and since February 2024 AWS has charged “$0.005 per IP per hour for all public IPv4 addresses”. IPv6 addresses, by contrast, are effectively free.
On the user side, IPv6 is growing slowly. Google measured that 48.3% of its users reached it over IPv6 in the first half of November 2026, against 46.2% a year earlier. It varies hugely by country: 88% in France, 77% in Germany, 55% in the US and under 7% in China.
What this means for IPv6 proxies
IPv6 proxies are cheap because IPv6 addresses are plentiful: providers sell them in blocks of millions. Our results show the two catches.
- Half the web is out of reach. An IPv6-only proxy cannot connect to an IPv4-only site. GitHub, PayPal, Stripe, eBay and Walmart were all IPv4 only in our test, and the share is lower outside the top sites.
- Many addresses can count as one. A home connection normally gets a whole /64 block of IPv6 addresses, so sites often treat that block as a single user. Wikipedia’s blocking policy says plainly that “a single user will generally use the same /64 range”. Thousands of addresses from one block do not spread your requests the way separate IPv4 addresses do. Our piece on blocked IP neighbours covers the same effect on IPv4.
So IPv6 proxies suit sites you have checked support IPv6 and do not rate-limit by block. For everything else, including most commerce and payments, you still need IPv4, and for sites that judge visitors by IP reputation, residential proxies on real home connections. Run a quick test like ours on your own target list before you buy.
How we did it
On 17 November 2026 we took the top 10,000 domains in the Tranco ranking (list Q2K34). For each domain and its www address, we looked up IPv4 (A) and IPv6 (AAAA) records and, where an address existed, opened a TLS connection on port 443 over that protocol. A site counted as a website if either protocol answered, and as working over IPv6 if a TLS connection over IPv6 succeeded. We excluded IPv4 addresses that the operating system presents in IPv6 form. Tests ran from a network in Romania; content networks can give different answers in different places, but whether a site publishes IPv6 at all rarely depends on where you ask. Network owners come from our IP Info service.
The bottom line
Half of the top 10,000 websites now work over IPv6, and nearly three-quarters of the top 100, mostly because content networks switched it on for their customers. The other half, including GitHub, PayPal, Stripe and the big retailers, are still IPv4 only. For anyone collecting web data, that makes IPv6 a useful extra for the sites that support it, not a replacement for IPv4.
Sources and references
- Tranco, list Q2K34: tranco-list.eu
- W3Techs, usage of IPv6 for websites (November 2026): w3techs.com
- Google, IPv6 statistics: google.com
- RIPE NCC, The RIPE NCC has run out of IPv4 addresses (25 November 2019): ripe.net
- CircleID, October 2026 IPv4 market report (10 November 2026): circleid.com
- AWS, public IPv4 address charge (28 July 2023): aws.amazon.com
- GitHub community, IPv6 support for cloning Git repositories (opened 25 January 2022): github.com
- Wikipedia, blocking IP addresses: en.wikipedia.org
- RFC 6146, stateful NAT64: rfc-editor.org
- RFC 8305, Happy Eyeballs version 2: rfc-editor.org