Which sites an IPv6 proxy reaches and which it does not: an AAAA table with a check date
An IPv6 plan has one hard limit that no setting works around: through an IPv6 exit you can only reach a host that publishes an AAAA record. Below is a verified table across twenty domains and the command to check your own targets — because on this question you should not take anyone's table on trust.
Why no setting fixes this
To reach a host over IPv6 a client needs that host's IPv6 address, and the address is published in DNS as an AAAA record. If a domain has only an A record it has no IPv6 address — and therefore no route. This is not blocking or filtering but the absence of an address: neither the proxy nor your code can do anything about it.
The converse is true and useful too: where AAAA exists, an IPv6 exit behaves exactly like IPv4 and needs no special configuration.
The table
The check was made through two independent DNS resolvers, and across all twenty domains their answers matched. Negative results were re-queried in a second round to tell a genuinely absent record from a transient failure.
# Checked 17 August 2026, two independent resolvers, answers matched
#
# HOST AAAA
wildberries.ru yes
www.wildberries.ru yes
market.yandex.ru yes
dns.yandex.ru yes
t.me yes
api.telegram.org yes
www.google.com yes
www.recaptcha.net yes
challenges.cloudflare.com yes
#
ozon.ru no
www.ozon.ru no
avito.ru no
www.avito.ru no
hh.ru no
vk.com no
lenta.ru no
github.com no
hcaptcha.com no
api.hcaptcha.com no
newassets.hcaptcha.com noWhat this means in practice
- Wildberries and Yandex.Market are reachable over IPv6 — the cheap IPv6 plan fits them.
- Ozon, Avito, hh.ru and VK are IPv4-only. No IPv6 plan will work for them however large the pool.
- reCAPTCHA and Cloudflare Turnstile are reachable over IPv6; hCaptcha is not, on any of its working domains.
- GitHub, to many people's surprise, still publishes no AAAA.
Check the name, not the domain
An AAAA record is published for a specific name, not for a whole domain. The apex and www can differ, and an API subdomain can differ from the site because it lives on separate infrastructure. That is why the table above lists names individually: hCaptcha, for instance, was checked on three working names and none of them has AAAA.
The practical consequence: check the names your code actually contacts, API and asset hosts included. The situation where a site opens but requests to its API fail is usually different AAAA per name, not a proxy fault.
And how a missing AAAA looks from the inside: the request never reaches the HTTP stage, so you see no status code at all. Depending on the client it is a name-resolution error or a connection error — and in logs it reads as “the proxy is broken”, although the proxy was never even involved.
How to check your own targets
It is one command, and it belongs before payment rather than after. An empty answer means an IPv6 plan is useless for that target.
# Empty output = no AAAA record = the host is unreachable over IPv6
dig +short AAAA example.com
# Straight through a list of targets
for h in example.com example.org; do
printf '%-28s %s\n' "$h" "$(dig +short AAAA "$h" | head -1)"
done
# On Windows
nslookup -type=AAAA example.comWhy this table is not permanent
DNS is mutable state, not a fact with a fixed value. An operator can add AAAA on any given day, and then a “no” row becomes wrong. Record lifetimes on the checked domains are short — from tens of seconds to an hour — so the table describes a moment, not a rule.
The second caveat is the more honest one: the queries came from a single network location. Some of these domains serve geography-aware DNS, so a client in another region could in principle get a different answer. Two resolvers guard against one resolver's error, not against regional variation. Which is why the command above matters more than the table.
What to buy when targets are mixed
A mixed target list is the normal case, and it is not an either-or decision. For targets with AAAA take IPv6: it is cheaper at the same thread count. For targets without it you need IPv4 — rotating if the address should change, static if it should not. Both products live in one dashboard, and splitting jobs between them is done on your side.
IPv6 for what IPv6 can reach
Rotating IPv6 from 650 ₽ for 50 threads, IPv4 from 1375 ₽ for 100. Check your targets with the command above before ordering: it takes a minute and removes the main risk of the purchase.
View pricingProxies for this job
Check it with our tools
Read next
- IPv6 or IPv4 for scraping: what is cheaper and when it failsIPv6 costs less at the same thread count but hits one limitation on the target's side. How to check in a minute whether it will work.
- Proxyless or with a proxy: who actually needs the proxy when solving a captchaFor token captchas the solver usually does not need your address — Anti-Captcha's own docs say so. Task types across four services, the spelling trap, and where IP matching really is enforced.
- Chrome proxy errors: what each code means, and how −111 differs from −130ERR_TUNNEL_CONNECTION_FAILED and ERR_PROXY_CONNECTION_FAILED sound alike but describe different stages. A table checked against the source, and what Chrome actually does when a proxy fails.