What Is an IPv6 Proxy and How Does It Work?

How an IPv6 proxy works

Your client opens a connection to the proxy endpoint — a hostname, a port, and your credentials. The proxy accepts the request, attaches an IPv6 address from its pool as the source, and forwards the traffic to the destination. The destination server sees only the proxy's IPv6 address: the source IP header, the reverse DNS, the ASN it belongs to. Your real IP never appears on the wire outside the first leg.

What the proxy picks from the pool, and how often, is controlled by rotation mode. Per-request rotation draws a new IPv6 address for every outgoing HTTP request — useful when each request should look independent (scraping, pricing checks, SERP collection). Timer rotation holds the same address for a configured window, from 1 second up to 24 hours — useful when the target needs session continuity (logins, cart flows). DCPROXY supports both on every IPv6 plan, switched from the dashboard at app.dcproxy.com.

IPv6 address structure and subnet pools

Two things make IPv6 a different animal from IPv4 once you're proxying at scale: the size of a single address and the size of a single subnet. Both come from the same source — IPv6 is 128-bit instead of 32-bit. The practical consequences are worth a closer look.

Address structure

An IPv6 address is a 128-bit number, written as eight groups of four hex digits separated by colons — 2001:0db8:85a3:0000:0000:8a2e:0370:7334. Leading zeros collapse, and one run of all-zero groups compresses to :: — so the same address can read 2001:db8:85a3::8a2e:370:7334. That's a cosmetic shorthand; the underlying bits don't change.

The number after the slash is the prefix length — how many high bits are fixed. /64 is the conventional network prefix on a single network segment. Proxy allocations usually live at shorter prefixes (/29, /32, /48), which expose many more variable bits and therefore many more addresses to rotate through.

Subnet pools

A single /29 IPv6 subnet contains 2^99 addresses — enough to rotate per request for practical eternity. A /32 subnet contains 2^96; still far beyond anything IPv4 can offer. Those numbers aren't marketing theater — they're the arithmetic of prefix length, and the same math anyone else computes from the same IPv6 standard.

What actually differentiates pools in the real world is ASN diversity. A pool spanning multiple /29 allocations across different ASNs forces a target site to analyze and block many independent ranges, not one prefix. DCPROXY allocates 20 × /29 subnets across 195 countries for its Datacenter IPv6 plan, 2 × /29 on Windstream's ASN for ISP, and 8 × /32 across 8 ASNs for SimpleDC.

Rotation — per-request vs timer

Rotating IPv6 proxies can rotate per request or on a timer between 1 second and 24 hours. Both modes use the same pool; the only difference is how often the proxy picks a fresh address.

Per-request rotation is the default on Datacenter IPv6. Every outgoing HTTP request gets a new IPv6 address drawn from the subnet pool. The destination server sees no correlation between requests — no repeated source IP, no repeated fingerprint on the network layer. This is the right mode for scraping, data collection, and any workload where independence between requests is the point.

Timer rotation holds the same address for a window you configure — 1 second to 24 hours. It's the right mode when the target expects session continuity: auth cookies tied to a source IP, multi-step checkouts, account farming where switching mid-session would break state. You can change rotation mode per sub-user from the dashboard and apply it without regenerating credentials.

Protocols — SOCKS5 and HTTP(S)

DCPROXY endpoints accept both SOCKS5 and HTTP(S) on the same credential. SOCKS5 operates at the transport layer: it forwards raw TCP (and UDP) without touching payloads, so it handles any protocol your client speaks — HTTPS, FTP, SMTP, custom binary. HTTP(S) operates at the application layer and is understood natively by every HTTP library, browser, and automation framework — requests, Scrapy, Playwright, Puppeteer, Selenium, curl.

The endpoint auto-detects which protocol your client speaks, so you don't need separate credentials or ports per mode. Use HTTP(S) when your stack is HTTP-only and you want the simplest setup; use SOCKS5 when you need non-HTTP traffic through the same proxy or want lower per-request overhead. Authentication is user/password on both, over TLS where supported.

Types of IPv6 proxy (Datacenter, ISP, multi-ASN)

The proxy market groups IPv6 into a few rough buckets, and the labels matter because target sites often treat them differently. The two primary axes are ASN type (who the addresses are registered to) and subnet topology (how many allocations, how many networks).

Datacenter IPv6 means addresses registered to a hosting ASN — a cloud provider, a colocation operator, a hosting company. They're fast, cheap, and easy to scale, but some sites classify hosting ASNs as higher risk and apply stricter filters. ISP IPv6 means addresses registered to a residential ASN — a home internet provider. The traffic looks like home broadband, which is treated more leniently by detection systems. Multi-ASN IPv6 spreads addresses across several allocations from different operators; no one ASN carries the whole pool, so a subnet block on one ASN doesn't take the whole plan down.

DCPROXY offers one product in each bucket. Datacenter IPv6 runs on its own hosting ASN with 20 × /29 subnets across 195 countries. ISP uses Windstream's ASN (Windstream is a real residential ISP operator in New York) for 2 × /29 subnets with home-IP trust. SimpleDC takes the multi-ASN approach: 8 × /32 subnets across 8 different ASNs — and it's the only DCPROXY plan that permits reCAPTCHA interaction. All three run on the same dashboard, same credentials, same rotation controls.

Or pivot to:

IPv6 vs IPv4 — which to pick

Short answer: IPv6 for cost and pool size, IPv4 for compatibility. IPv6 gives you billions of unique addresses per subnet at a fraction of the per-address cost, which is why rotating-proxy pricing has converged on IPv6. IPv4 still matters when the target site only accepts IPv4 connections, or when a dedicated IPv4 address carries the trust signal you need (SMTP sending, some payment flows). Most scraping, research, and automation jobs work on IPv6 today — but check target compatibility before committing.

How to choose your IPv6 plan

DCPROXY operates on its own ASNs, without reselling, since 2022. The three IPv6 lines target different jobs: precise country selection, home-IP trust, or multi-ASN diversity with reCAPTCHA support. Pick the branch that matches your target site's behaviour, then size the plan from there.

• 1

  You need specific-country GEO (195 countries, 200+ locations) → Datacenter IPv6 — 20 × /29 subnets, per-request rotation, unlimited bandwidth, from $10/mo

• 2

  You need home-IP trust for sites that filter hosting ASNs → ISP Windstream IPv6 — 2 × /29 subnets on Windstream's ASN, NY exit, from $17/mo

• 3

  You need reCAPTCHA interaction or the lowest entry price → SimpleDC IPv6 — 8 × /32 subnets across 8 ASNs, random DE/US/UK/AU exits, from $6/mo