Using SOCKS5

SOCKS5 is on port 1080 with exactly the same username and password as HTTP:

curl -x socks5h://YOUR_KEY:[email protected]:1080 https://api.ipify.org

Use socks5h:// rather than socks5://. The h sends the hostname through the proxy instead of looking it up on your own machine, so the DNS request does not leave from your IP.

Both ports use the same account, balance and tiers. Pick by what your client supports.

What SOCKS5 cannot do here

No UDP. Only TCP connections are relayed, so UDP-based protocols will not work through it.
No state, city, ZIP or ASN targeting. Those are set with HTTP headers, and SOCKS5 has nowhere to put them. Country targeting in the password works on both.

Destination ports

As on HTTP, the proxy connects to the common web and mail-client ports: 80, 443, 8080, 8443, 22, 465, 587, 993, 995 and 5060. A request to any other port is refused with a message saying so. If you need a different port, ask us — a server may suit the job better than a proxy.

Proxies: your first requestFind your credentials, copy a cURL or Python example, and check the response.Proxy connection format and tiersWhat goes in the username and password, and what each tier is for.Sticky sessionsKeep the same IP across requests, for logins and multi-step flows.

Still stuck? Open a ticket — tell us what was missing and the article gets fixed.

← Docs / Proxies

Using SOCKS5

SOCKS5 is on port 1080 with exactly the same username and password as HTTP:

curl -x socks5h://YOUR_KEY:[email protected]:1080 https://api.ipify.org

Use socks5h:// rather than socks5://. The h sends the hostname through the proxy instead of looking it up on your own machine, so the DNS request does not leave from your IP.

Both ports use the same account, balance and tiers. Pick by what your client supports.

What SOCKS5 cannot do here

No UDP. Only TCP connections are relayed, so UDP-based protocols will not work through it.
No state, city, ZIP or ASN targeting. Those are set with HTTP headers, and SOCKS5 has nowhere to put them. Country targeting in the password works on both.

Destination ports

Still stuck? Open a ticket — tell us what was missing and the article gets fixed.

Using SOCKS5

What SOCKS5 cannot do here

Destination ports

Related

Using SOCKS5

What SOCKS5 cannot do here

Destination ports

Related