SOCKS5 carries arbitrary TCP and UDP traffic, supports username and password authentication, and can resolve DNS at the exit node. This guide covers how it works, where it fits, and how to buy and use authenticated access without a dashboard.
SOCKS5 operates at the session layer. Your client opens a connection to the proxy, names the destination, and the proxy forwards bytes. Unlike an HTTP proxy, it does not parse or rewrite HTTP headers, and it does not terminate TLS. That is why it works for anything that speaks TCP or UDP, from browsers to trading bots.
The protocol supports username and password authentication. Paid proxy networks use those credentials to scope access to a session, a country, or a traffic allowance. SOCKS5 does not encrypt the payload; use HTTPS or TLS inside the tunnel when the data needs encryption.
| SOCKS5 | HTTP proxy | VPN | |
|---|---|---|---|
| Traffic | TCP and UDP | HTTP and HTTPS | IP tunnel |
| Authentication | Username and password | HTTP auth | Varies by provider |
| DNS | Local, or at the exit with socks5h | Usually local | Inside the tunnel |
| Header rewriting | None | Can add or modify headers | None |
| Best for | Scrapers, bots, arbitrary TCP | Simple HTTP requests | Whole-device privacy |
| Browser support | Unauthenticated only in Chromium | Broad | Native |
The prefix changes where DNS resolution happens. With socks5://, your client resolves the hostname locally and sends the resulting IP to the proxy. With socks5h://, the proxy resolves the hostname at the exit node.
Use socks5h for scraping and trading. With plain socks5, your local resolver still sees every lookup, and the resolver location can contradict the connection origin. Detection systems look for that mismatch.
Chromium does not implement SOCKS5 username and password authentication. If you put an authenticated SOCKS5 URL into Chrome, Playwright, or Puppeteer, the browser will not send the credentials. Run a local HTTP-to-SOCKS5 bridge that holds the upstream credentials, then point the browser at the local HTTP proxy. The Playwright proxy guide covers the bridge and the per-context rotation pattern.
Use a sticky session for anything authenticated: a trading bot, a logged-in scraper, a checkout flow. Choose rotation for unauthenticated collection where each request can come from a new IP. Changing the IP between a price fetch and an order submission looks like account takeover. The rotating proxy guide covers the mechanics.
Country is a session parameter. Open a session for the country the target expects; do not encode the country into the SOCKS5 username.
ProxyBase sells access across 45 countries by the gigabyte. Pricing is per GB, KYC is not required, and credentials are provisioned through the API, CLI, or MCP server. Payment is in crypto.
| Network | Catalog range | Use it for |
|---|---|---|
| Residential | $2-$4 / GB | Sites with bot management; the default for scraping |
| Mobile | $3.30-$6.70 / GB | Endpoints that reject residential ranges |
| ISP | $1.30-$2.70 / GB | Speed with moderate trust |
| Datacenter | $0.70-$1.30 / GB | Public APIs and low-protection pages |
Ranges as of November 2026. Prices vary by country and supply. The markets page shows the live catalog.
Open a country-matched session first, then use the returned session id and your token in the SOCKS5 URL. The v2 buyer gateway is api.proxybase.xyz:1082.
Python with requests:
curl:
Both examples use socks5h (curl calls it --socks5-hostname). If the exit country is wrong, close the session and open a new one before sending production traffic.
A SOCKS5 connection refused usually means the wrong port or bad credentials. A timeout points to a session that is down or out of bandwidth. HTTP 407 is an HTTP proxy error, not SOCKS5. The proxy error guide has the full checklist.
No. SOCKS5 moves bytes between your client and the exit node; it does not encrypt them. Use HTTPS or TLS for the payload. The proxy changes the network origin, not the transport security.
SOCKS5 handles arbitrary TCP and UDP traffic and long-lived connections without rewriting headers. HTTP proxies are useful when you need HTTP-level caching or header control. Most paid scraping setups use SOCKS5 with application-level routing.
The h means the proxy resolves the hostname at the exit node. With plain socks5, your client resolves the hostname locally and sends the IP to the proxy. Use socks5h so DNS resolution and connection origin stay consistent.
Chromium does not send SOCKS5 username and password credentials. Run a local HTTP-to-SOCKS5 bridge that holds the upstream credentials, then point Chrome or Playwright at the bridge. The Playwright proxy guide covers the setup.
ProxyBase catalog ranges are $0.70-$1.30/GB for datacenter, $1.30-$2.70/GB for ISP, $2-$4/GB for residential, and $3.30-$6.70/GB for mobile. Prices vary by country and supply.
Yes. Open a rotating session for unauthenticated collection, or a sticky session for authenticated flows such as trading bots and logged-in scrapers. Rotating an authenticated session mid-flow looks like account takeover.
No. ProxyBase is wallet-based and KYC-free. You pay per GB in crypto and receive credentials through the API, CLI, or MCP server.
Using a proxy is legal in most jurisdictions. What matters is what you do with it and the target site's terms. Use it for legitimate access, respect rate limits and contracts, and do not use it for fraud or to evade lawful restrictions.
Residential, mobile, ISP, and datacenter exits by the GB. No KYC, crypto accepted, credentials through the API.