Protocol · SOCKS5 on all four networks
Every HodlProxy product speaks SOCKS5 as well as HTTP(S): the same account, the same credentials and the same targeting parameters, on port 9001 of the rotating gateways and port 8001 of every dedicated address. Use it for tools that are not HTTP clients, for apps that only accept a SOCKS proxy, or whenever the exit should resolve hostnames instead of your machine.
01 — Which SOCKS5 proxy
The protocol does not decide how trusted an exit is; the IP behind it does. Pick the network for the target, then connect to it over SOCKS5 with the credentials you already have.
Rotating household IPs over SOCKS5 at res.hodlproxy.com:9001, with country, state, city and ASN targeting in the username and sticky sessions from 1 minute to 24 hours.
Static residential SOCKS5 at ip:8001: one address for the whole term with unlimited traffic, the natural fit for logins, accounts and long-lived sessions.
Dedicated datacenter SOCKS5 at ip:8001: the lowest latency and the lowest price per IP, for targets that accept datacenter ranges.
4G/5G carrier IPs over SOCKS5 at mob.hodlproxy.com:9001, or on a dedicated device at ip:8001, for the targets that score every other kind of address.
02 — SOCKS5 or HTTP
Both carry HTTPS end to end and both are elite here. The choice depends on what your client speaks and who should resolve hostnames.
| SOCKS5 | HTTP(S) proxy | |
|---|---|---|
| Works at | Transport level: relays any TCP connection | Application level: plain HTTP requests and CONNECT tunnels |
| Carries | HTTP, HTTPS, WebSocket, SSH, database or custom TCP protocols | HTTP and HTTPS; other TCP protocols only through CONNECT |
| DNS | Remote when the client sends the hostname (socks5h), local otherwise | Always remote: the hostname travels in the request |
| Client support | Browsers, anti-detect tools, Telegram, cURL, Python, Node.js, Go | Every HTTP library, browser and scraping framework |
| Encryption | None of its own: TLS between client and target does the work | None of its own for the hop to the proxy; HTTPS stays end to end |
| HodlProxy port | 9001 (gateways) · 8001 (dedicated) | 9000 (gateways) · 8000 (dedicated) |
socks5h://.03 — Connect
Replace USER and PASS with the credentials from your dashboard. Add -cc-de or any other targeting parameter to the username to choose the exit.
# Rotating residential exit in Germany; the hostname is resolved at the exit (socks5h)
curl -x socks5h://USER-cc-de:PASS@res.hodlproxy.com:9001 https://api.ipify.org
# Same thing on a dedicated ISP or datacenter address
curl -x socks5h://USER:PASS@203.0.113.10:8001 https://api.ipify.org# pip install requests[socks]
import requests
proxy = "socks5h://USER-cc-us-sid-a1b2-ttl-10m:PASS@res.hodlproxy.com:9001"
r = requests.get("https://api.ipify.org", proxies={"http": proxy, "https": proxy}, timeout=30)
print(r.text) # the same US exit for 10 minutes// npm install axios socks-proxy-agent
import axios from "axios";
import { SocksProxyAgent } from "socks-proxy-agent";
const agent = new SocksProxyAgent("socks5h://USER-cc-gb:PASS@mob.hodlproxy.com:9001");
const { data } = await axios.get("https://api.ipify.org", { httpAgent: agent, httpsAgent: agent });
console.log(data); // a UK mobile carrier IPTelegram (mobile): Settings → Data and Storage → Proxy → Add proxy → SOCKS5
Telegram Desktop: Settings → Advanced → Connection type → Use custom proxy
Server res.hodlproxy.com (or your dedicated IP)
Port 9001 (or 8001 on a dedicated IP)
Username USER-cc-nl-sid-tg1-ttl-24h
Password PASS
Firefox: Settings → Network settings → Manual proxy → SOCKS v5, and tick
"Proxy DNS when using SOCKS v5". Firefox has no field for SOCKS5
credentials: whitelist your IP in the dashboard instead.A long sticky session (-sid-...-ttl-24h) suits apps that keep one connection open, such as messengers; rotation on every connection suits crawlers. Every parameter is listed in targeting & sessions.
04 — Where it helps
Everything below runs over TCP, which is all a SOCKS5 proxy on HodlProxy carries.
SSH, Git over SSH, database clients, custom TCP services and desktop software that offer a SOCKS setting and nothing else.
Most profiles accept SOCKS5 with credentials; pair one sticky residential, ISP or mobile exit with each profile.
Telegram and similar apps accept a SOCKS5 proxy natively; a 24-hour sticky session keeps the connection stable.
With socks5h the destination name is resolved in the exit's network: no lookups from your own resolver, and local answers.
Headless browsers, bots and AI agents that take one proxy URL: switch protocols without touching targeting.
No proxy headers are added and TLS is never terminated, so the target sees an ordinary client on the exit address.
05 — Questions
Yes. Residential and mobile gateways accept SOCKS5 on port 9001; every dedicated ISP, datacenter and mobile address accepts it on port 8001. Credentials, targeting parameters and billing are the same as over HTTP(S).
No. HodlProxy relays TCP only: UDP ASSOCIATE and BIND are not available, so QUIC, HTTP/3 and UDP-based games or calls fall back to TCP or bypass the proxy.
With socks5:// the client resolves the hostname itself and sends an IP address; with socks5h:// it sends the hostname and the exit resolves it. Use socks5h to keep DNS lookups out of your own network and to get the answers a local user would get.
Not in any way you would measure on web traffic. Both add one hop; speed depends on the exit network, the distance and the target. Choose the protocol for compatibility, the network for trust and price.
SOCKS5 itself does not encrypt. HTTPS, SSH and other TLS-based protocols stay encrypted end to end between your client and the destination, and HodlProxy never terminates TLS.
Yes. Add your server's IPv4 address to the whitelist in the dashboard and connect without credentials; targeting is then set from the dashboard instead of the username.
No. Public free lists are mostly misconfigured or compromised machines that log traffic. A paid exit costs from $0.70 per IP per month or $2.45 per GB, starting from a $20 top-up.
In cryptocurrency (BTC, ETH, USDT, USDC, LTC, XMR, SOL, TRX, DOGE and more) into a prepaid USD wallet from $20. No card, no identity documents; residential and mobile traffic never expires.
Ready when you are
Create an account, top up $20 in crypto and paste the line above into your tool. Traffic you buy never expires.