Ports and protocols
HTTP, HTTPS and SOCKS5 endpoints for every product.
| Product | Host | HTTP | HTTPS | SOCKS5 |
|---|---|---|---|---|
| Residential | res.wproxy.io | 8000 | 8443 | 1080 |
| Datacenter | dc.wproxy.io | 8000 | 8443 | 1080 |
| Mobile | mob.wproxy.io | 8000 | 8443 | 1080 |
| ISP | isp.wproxy.io | 8000 | 8443 | 1080 |
| Dedicated | ded.wproxy.io | 8000 | 8443 | 1080 |
All three protocols carry the same traffic across the same exits and bill identically. The choice is about your client, not about capability.
Which to use
- HTTP on 8000 — the default. Works everywhere, tunnels HTTPS through CONNECT.
- HTTPS on 8443 — encrypts the hop between you and the gateway. Worth it on untrusted networks; unnecessary from a datacenter you control.
- SOCKS5 on 1080 — protocol-agnostic. Use it for anything that is not HTTP, and for clients whose CONNECT handling is unreliable.
SOCKS5 examples
curl --socks5-hostname res.wproxy.io:1080 \
-U "wp-acc4821-country-us:s3cr3t-pass" \
https://ipinfo.io/jsonResolve DNS remotely
Use socks5h:// rather than socks5:// (and --socks5-hostname rather than --socks5). The h means hostnames are resolved by the exit rather than by your machine, which is both faster and less likely to leak the fact that a proxy is in play.
IPv6
The gateways are dual-stack. Exit addresses are IPv4 by default because most targets still treat IPv6 residential traffic as unusual; append -ipv6 to request an IPv6 exit where the pool supports it.
Something inaccurate?Tell support