Skip to main content
Both address families live behind the same hostname and port. Your request is served over IPv4 or IPv6 based on what the target site supports and how your client resolves DNS.

​
How it works

When you route a request through dcp-us.proxies.fo:10808 or dcp-eu.proxies.fo:10808:
  1. The proxy receives your CONNECT or HTTP request with the target hostname
  2. The network resolves the target’s DNS record (A for IPv4, AAAA for IPv6)
  3. If the target has an AAAA record, the connection may egress over IPv6
  4. If the target is IPv4-only, the connection egresses over IPv4
This means you don’t pick the address family explicitly — the target does.

​
Checking what you got

# Most "what's my IP" services are dual-stack. Hit the IPv6-only one to confirm:
curl -x "http://USER:PASSWORD@dcp-eu.proxies.fo:10808" https://api6.ipify.org
curl -x "http://USER:PASSWORD@dcp-eu.proxies.fo:10808" https://api.ipify.org
  • api.ipify.org is IPv4-only — the response will always be an IPv4 address
  • api6.ipify.org is IPv6-only — if your connection succeeds, you egressed over IPv6

​
Forcing IPv4

Most HTTP clients default to IPv4 when both families are available. If you want to guarantee IPv4: 
# --ipv4 forces A-record resolution only
curl --ipv4 -x "http://USER:PASSWORD@dcp-eu.proxies.fo:10808" \
  https://api.ipify.org

​
Forcing IPv6

# --ipv6 forces AAAA-record resolution only
curl --ipv6 -x "http://USER:PASSWORD@dcp-eu.proxies.fo:10808" \
  https://api6.ipify.org

​
When to prefer IPv6

  • The target supports IPv6 (check with dig AAAA <domain> +short)
  • You need high concurrency — IPv6 pools are effectively unlimited
  • Cost per request matters

​
When to prefer IPv4

  • The target is IPv4-only (no AAAA record)
  • You’re using tooling that doesn’t cleanly support IPv6
  • Compatibility with legacy systems is a concern