Specs
| Attribute | Value |
|---|---|
| Address family | IPv6 only |
| Locations | EU, US |
| Protocols | HTTP, HTTPS, SOCKS5, UDP |
| Authentication | Username : password |
| Threads | Unlimited |
| Uplink | 10 Gbps |
| Billing | Per day, unlimited bandwidth |
Endpoints
| Region | Host | Port |
|---|---|---|
| United States | dcp-us.proxies.fo | 10808 |
| Europe | dcp-eu.proxies.fo | 10808 |
Checking your egress
Useapi6.ipify.org — it’s IPv6-only, so a successful response confirms you egressed over IPv6. api.ipify.org is IPv4-only and will fail or return an error for IPv6 plans.
Rotating (default)
No modifiers = fresh IPv6 per request:Sticky sessions
Same modifiers as IPv4 —session-<id> plus optional duration-<seconds>:
IPv6 target compatibility
Before committing a workload, confirm the target supports IPv6:Code examples
Unlimited-thread workload
IPv6 has no thread cap — scale concurrency as high as your client can handle.SOCKS5 & UDP
Common issues
'No route to host' on a target
'No route to host' on a target
The target site doesn’t have an AAAA record — it’s IPv4-only. Either switch to the IPv4 product or pick a different target.
Library can't resolve IPv6
Library can't resolve IPv6
Some older HTTP libraries default to IPv4 lookup. Upgrade the client or configure it to prefer IPv6. Python’s
requests works correctly with modern urllib3 (1.25+).Getting IPv4 back from a test endpoint
Getting IPv4 back from a test endpoint
Use
api6.ipify.org instead of api.ipify.org. The IPv4 endpoint will either reject the connection or return an error for IPv6 plans.