Does This Domain Support IPv6?
Enter a domain to look up its AAAA DNS records in real time. Confirm IPv6 reachability before you point an IPv6 proxy at it — no sign-up, no cached snapshots.
An IPv6 checker is a tool that queries a domain's AAAA DNS records to confirm whether the host is reachable over IPv6. The DCPROXY checker runs the lookup against authoritative resolvers, returning live AAAA addresses or a clean negative result.
Tool spec
What this tool does
A small, focused DNS utility for one job: confirming a target domain's IPv6 reachability before you route traffic through an IPv6 proxy.
- Input: a domain or hostname (apex like example.com or a subdomain like api.example.com).
- Lookup: AAAA DNS records queried against authoritative resolvers in real time, with no caching between checks.
- Positive result: one or more AAAA addresses returned — the host is published in DNS as accepting IPv6 connections.
- Negative result: zero AAAA records — the host is IPv4-only at the DNS layer, and IPv6 clients will not route to it by name.
- Speed: live DNS lookup on every request — results reflect the current state of the zone, not a stale snapshot.
- Scope: this tool checks the target domain you enter. To check your own connection's IPv6 (your dual-stack, your proxy egress), use the IP Checker.
Reading the result
How to read your result
AAAA records present
One or more AAAA addresses came back. The target is published in DNS as IPv6-reachable, and an IPv6 proxy can route to it by hostname. This is the standard result for sites on modern hosting and CDN setups (Cloudflare, Cloudfront, GitHub Pages, most Google properties). For pre-flight planning, this target works with our IPv6 proxy plans.
Datacenter IPv6 plansNo AAAA records
The zone publishes only A records, so the host is IPv4-only at the DNS layer. An IPv6 proxy cannot reach it by name — DNS will return zero IPv6 addresses, and a strict IPv6 client will fail to connect. For IPv4-only targets, you need an IPv4 SKU. ISP Static IPv4 covers single-IP needs today, and IPv4 Rotating is in our roadmap.
Talk to support about IPv4Mixed (CDN-fronted)
The apex looks fine — AAAA returned — but the actual workload runs across many hostnames behind a CDN like Cloudfront or Cloudflare. Different edge endpoints, asset domains, and origin pulls may or may not have AAAA. The fix is to pre-check each hostname your pipeline actually hits, not just the apex, and monitor for drift over time.
Datacenter IPv6 with monitoringReal-world cases
Common test cases
Three patterns cover most of what you will see in practice. CDN-fronted apex domains usually look fine but hide downstream complexity, search engines accept IPv6 but treat it harshly, and standard dual-stack sites are the easy case. Pre-checking saves you wasted requests on the first two.
| Domain pattern | Expected result | What to do |
|---|---|---|
| *.cloudfront.net | Yes (host depending) | Use Datacenter IPv6 and verify each target hostname with this tool. |
| Google SERP / google.com search | Yes, but IPv6 is banned fast | Use IPv4 — see the IPv6 vs IPv4 trust-level dimension. |
| Standard dual-stack site (e.g. example.com) | Yes | Any DCPROXY IPv6 plan works. |
Why it matters
Why IPv6 support matters for proxy users
When you route through IPv6 proxies, the destination must support IPv6 or the connection fails silently — DNS returns no IPv6 address and a strict IPv6 client gives up. For a one-off curl that's a non-issue. For a pipeline running against hundreds or thousands of targets, pre-checking IPv6 reachability before deployment saves wasted requests, false positives, and debug sessions chasing connection errors that are really DNS truths.
IPv6 adoption is uneven. Cloud providers, modern CDNs, and major platforms have dual-stacked their infrastructure; smaller hosts, legacy stacks, and certain regions still publish only A records. The split is not random, and the fix is not to wait — it is to sort your target list before you start, then assign IPv6 proxies where they actually route.
For protocol structure, rotation modes, and how IPv6 proxy pools are architected, read the full IPv6 proxy guide.
Pick your IPv6 plan
Best fit: Datacenter IPv6
20 × /29 datacenter subnets across 195 countries, per-request rotation, SOCKS5 and HTTP(S), unlimited bandwidth — from $10/month. Default pick for scraping, research, and geo-distributed automation against IPv6-reachable targets. On our own ASNs since 2022.
Or pivot to:
Related tool
Check your own IP
You've checked the target. Now check yourself: confirm your own public IPv4 and IPv6, verify dual-stack, or confirm a proxy is actually carrying your traffic. The IP Checker forces a protocol per endpoint so you can see exactly what your network or proxy is doing.
Open IP CheckerFAQ
Common Questions
Straight answers on AAAA records, IPv6 reachability, and which DCPROXY plan to pick once you know the result.
An AAAA record is the DNS record type that maps a domain name to a 128-bit IPv6 address — like 2606:2800:220:1:248:1893:25c8:1946. It is the IPv6 counterpart of the A record, which maps the same name to a 32-bit IPv4 address. A domain can publish both A and AAAA records simultaneously, in which case it is reachable over both protocols. That setup is called dual-stack and is now the default on most modern hosting and CDN platforms.
Ready to ship IPv6 traffic?
Once you've confirmed your targets accept IPv6, route through 20 × /29 datacenter subnets across 195 countries — own ASNs, per-request rotation, unlimited bandwidth.