Which Websites Support IPv6, and How to Check a Site Yourself

· Updated:

Many of the largest platforms, including Google, YouTube, Facebook, Instagram and Wikipedia, publish IPv6 addresses, but plenty of well-known sites still answer only over IPv4. Support changes over time and can differ between a site's main domain and the subdomains it loads, so the reliable answer is to check the specific hosts you need. This guide shows how to run that check with dig, nslookup and curl -6, and what it means for choosing a proxy.

IPv4 works everywhere; check IPv6 before you rely on it

Which websites support IPv6 today

A site supports IPv6 when its domain publishes an AAAA record in DNS and its servers accept connections on that address. When we checked a sample of popular domains in November 2026, these returned AAAA records: google.com, www.youtube.com, www.facebook.com, www.instagram.com, www.wikipedia.org, www.linkedin.com, www.netflix.com and www.amazon.com. Two large sites did not: x.com and github.com returned no AAAA record, so they were reachable over IPv4 only.

That snapshot is a starting point, not a rule. Sites add and remove IPv6, large companies run many domains with different setups, and DNS answers can vary by region. Treat any list, including this one, as something to verify for your own targets.

Why the main domain is not the whole answer

A page loads resources from several hosts: a login domain, an API, a CDN for images, a payment provider. The main domain can be dual-stack while one of those hosts is IPv4-only. If your tool can only reach IPv6, the page may load and then fail at sign-in or checkout. Open your browser's developer tools, look at the Network tab, and note every hostname the workflow touches before you check them.

How to check IPv6 support for a website

There are two separate questions: does the domain publish an IPv6 address, and can you actually connect to it over IPv6? The first is a DNS lookup. The second needs a connection test from a machine that has working IPv6.

AAAA record check with dig

On Linux and macOS, dig asks DNS for the AAAA record directly:

dig +short AAAA example.com

If it prints one or more addresses with colons, such as 2001:db8::1, the domain publishes IPv6. The output may start with a hostname line, which is a CNAME the name points to; the colon addresses after it are what count. Empty output means there is no AAAA record, so clients will use IPv4.

AAAA record check with nslookup on Windows

On Windows, nslookup is available in Command Prompt and PowerShell:

nslookup -type=AAAA example.com

An IPv6 address in the answer means the record exists. A reply such as Can't find example.com: No answer, or one that lists no IPv6 address, means it does not. The exact wording differs between operating systems, so look for the presence or absence of an address rather than a specific message. In PowerShell, Resolve-DnsName example.com -Type AAAA gives the same information.

Connection test with curl -6

A published AAAA record does not prove the server accepts IPv6 connections. curl -6 forces curl to use IPv6 only:

curl -6 -sS -o /dev/null -w '%{http_code} %{remote_ip}\n' --max-time 10 https://example.com

A status code with an IPv6 remote_ip means the connection worked. Could not resolve host usually means there is no AAAA record. A timeout, Couldn't connect to server or a network-unreachable error can mean the site's IPv6 is broken, but it can just as easily mean your own machine has no IPv6 route. Run the same command against a domain you know is dual-stack first; if that fails too, the problem is your connection, not the site.

Bulk check in Python

To check a list of hostnames for AAAA records, the standard library is enough. This only checks DNS, not reachability:

import socket

hosts = ["example.com", "www.wikipedia.org", "github.com"]
for host in hosts:
    try:
        infos = socket.getaddrinfo(host, 443, socket.AF_INET6, socket.SOCK_STREAM)
        addrs = sorted({info[4][0] for info in infos})
        print(f"{host}: IPv6 {addrs}")
    except socket.gaierror:
        print(f"{host}: no IPv6 address")

What this means for IPv6 proxy compatibility

An IPv6 proxy is only useful for targets that are reachable over IPv6. If a proxy can only send traffic out over IPv6, it cannot reach an IPv4-only host unless the provider adds a translation layer or an IPv4 exit, and you would need to ask that provider how they handle it.

No automatic fallback through the proxy

On a normal dual-stack connection, browsers and tools such as curl use Happy Eyeballs: they try IPv6 and IPv4 close together and use whichever connects first. That hides a lot of broken IPv6. When all traffic has to leave through a proxy's IPv6 address, that fallback is gone, so an IPv4-only API or a broken AAAA record becomes a hard failure instead of a silent switch.

Sites may treat a whole IPv6 block as one user

IPv6 addresses are usually handed out in large blocks, often a /64 per customer or site. Because one user can hold millions of addresses, some sites apply rate limits or reputation to the block rather than to the single address. Many addresses from the same block do not necessarily count as separate visitors. See IPv4 vs IPv6 proxies for a fuller comparison.

Where private IPv4 fits, and where it does not

IPv6 proxies are a separate ProxyV4 product that only works on IPv6-ready sites. What ProxyV4 sells is IPv4: private datacenter IPv4 in the United States, Vietnam, Japan, South Korea, Singapore, the United Kingdom and Hong Kong, and static ISP IPs in the United States and Vietnam. Private IPv4 works on every IPv4 and dual-stack site, so you do not need to check each target for AAAA records before you use it.

Each IP has one tenant for the whole term, traffic is unmetered, and renewing before expiry keeps the same address. Every proxy supports HTTP(S) and SOCKS5 with username and password login; on the order's page you choose HTTP only, SOCKS5 only or both on the same port. Switching modes can move the proxy to a new port, so copy the ip:port:user:pass line again afterwards.

It does not fit if you specifically need IPv6 addresses, for example to test how your own service behaves for IPv6 visitors or to reach an IPv6-only network. It also does not fit if you need rotation on every request or mobile carrier IPs, neither of which is on sale. Prices are per IP per month; see live prices, and order a single IP to test first.

Confirm the exit IP before you deploy

Once you have a proxy, check which address the target will see. With an IPv4 proxy, the result should be the proxy's IPv4 address:

curl --max-time 15 -x http://USER:PASS@IP:PORT https://proxyv4.com/api/my-ip

You can also paste the line into the free proxy checker, or open the my IP tool in a browser that uses the proxy. If you get an authentication error, copy the line again from the dashboard and check that the scheme matches the mode you set.

Step by step

  1. 1

    List every host the workflow uses

    Use the browser's Network tab to note the main domain plus login, API, CDN and payment hostnames.

  2. 2

    Check each host for AAAA records

    Run dig +short AAAA <host>, or nslookup -type=AAAA <host> on Windows; addresses with colons mean IPv6 is published.

  3. 3

    Test a real IPv6 connection

    From a machine with working IPv6, run curl -6 against a known dual-stack site first, then against each target.

  4. 4

    Decide on IPv4 or IPv6

    If any required host lacks working IPv6, plan on IPv4; private IPv4 reaches both IPv4-only and dual-stack sites.

Frequently asked questions

How do I know if a website supports IPv6?

Look up its AAAA record with dig or nslookup. If one exists, confirm it accepts connections with curl -6 from a machine that has working IPv6.

Can an IPv6 proxy open an IPv4-only website?

Not if it can only exit over IPv6. Some providers add translation or an IPv4 exit, so ask the provider how their product handles IPv4-only targets.

Why does curl -6 fail on every site I try?

Usually your own network has no IPv6 route. Test a known dual-stack domain first; if that fails too, the issue is local, not the site.

Does ProxyV4 sell IPv6 proxies?

Yes, as a separate product that only works on IPv6-ready sites. ProxyV4 also sells private IPv4 and static ISP proxies, which work on every IPv4 and dual-stack site.

Is bandwidth limited on the IPv4 proxies?

No. Traffic on private IPv4 and static ISP proxies is unmetered and not billed.

IPv4 works everywhere; check IPv6 before you rely on it

Private IPv4 reaches every IPv4 and dual-stack site, with HTTP(S) and SOCKS5 and unmetered traffic. Order a single IP and test it against your own targets.

See live prices

Related articles

Knowledge base
IPv4 or IPv6 Proxy: Choosing the Right Address Family
IPv4 vs IPv6 proxy: why IPv4 costs more, which sites accept IPv6, how platforms group IPv6 by subnet, and a quick DNS test to run before you buy IPv6 in bulk.
Free tools
Check proxies in bulk: status, exit IP and latency
Free online proxy checker: paste up to 100 ip:port:user:pass lines and see which proxies work, their exit IP and latency, plus what each failure result means.
Proxy setup
Using cURL with an authenticated proxy: commands that prove it works
Send cURL requests through an authenticated HTTP(S) proxy with -x and -U, confirm the exit IP, read the CONNECT handshake and time each request on any OS.
Products
IPv6 proxies for high-volume work
IPv6 proxies in all seven of our countries, from the US to Hong Kong: many addresses at a low price per IP, for sites and tools that accept IPv6 connections.
Knowledge base
Using a Static IP for IP Whitelisting on APIs and Admin Panels
Get a static IP for IP whitelisting: route API, admin panel and tool traffic through one fixed outbound IPv4, verify the exit IP, and fix allow-list rejections.
Knowledge base
How to Check an IP Fraud Score Before You Rely on a Proxy
How to check an IP fraud score for a proxy, why IPQualityScore, Scamalytics and others disagree, and what a risk score can and cannot tell you before you buy.
Knowledge base
What Is a Proxy Server? The Middleman Between You and the Web
What is a proxy? A plain-English explanation of how a proxy server relays your traffic, the ways proxies are classified, their common uses and their limits.
Products
Dedicated datacenter proxies: one private IPv4 per customer
Private IPv4 proxies in the US, Vietnam, Japan, South Korea, Singapore, the UK and Hong Kong. One tenant per IP, HTTP(S) and SOCKS5, no traffic metering.
Products
Static ISP proxies: residential IPs on consumer networks
Static ISP proxies in the United States and Vietnam: fixed IPs registered to consumer internet providers, rented to one customer, with unmetered traffic.
Pricing
Proxy prices per IP, by location and volume
Current per-IP rates for private IPv4 and static ISP proxies in the US, Vietnam, Japan, South Korea, Singapore, the UK and Hong Kong, with volume discounts.