SOCKS5 Proxy
IntermediateA protocol-agnostic proxy standard that forwards any TCP or UDP traffic — not just web requests — with optional authentication and no payload rewriting.
In depth
SOCKS5 is the fifth version of the SOCKS protocol, the lingua franca for general-purpose proxying. Where an HTTP proxy understands and may rewrite web requests, SOCKS5 is deliberately dumb: it simply relays bytes between you and the destination, which makes it work for any application — browsers, scrapers, torrent clients, game launchers, mail clients, custom TCP tools.
How it differs from an HTTP proxy
| SOCKS5 | HTTP proxy | |
|---|---|---|
| Traffic types | Any TCP/UDP | HTTP(S) only |
| Reads your traffic | No — blind relay | Can inspect/modify headers |
| DNS resolution | Can resolve remotely (hides lookups) | Varies |
| Authentication | Username/password built in | Basic auth headers |
Key properties
- UDP and IPv6 support: added in version 5 — relevant for streaming, gaming and modern stacks.
- Remote DNS: the proxy resolves hostnames, so your local resolver never sees what you visit.
- No encryption: SOCKS5 itself is plaintext. Privacy comes from the application layer (HTTPS) or by tunneling SOCKS5 over SSH/TLS — this is the biggest misconception about it.
When to choose it
Pick SOCKS5 when the tool you are proxying is not a browser, when you need UDP, or when you want the proxy to stay out of your protocol entirely. Most premium proxy providers expose every plan over both HTTP and SOCKS5 endpoints.
Examples
- A custom Python scraper tunnels raw TCP through SOCKS5 because its target speaks a non-HTTP protocol.
- A privacy-minded user chains a torrent client through a SOCKS5 endpoint so peers see the proxy IP.
- A pentester forwards tooling through SSH dynamic port forwarding — which is simply a local SOCKS5 proxy.
Common use cases
FAQs
Marginally — SOCKS5 never injects or rewrites headers (a badly configured HTTP proxy can leak X-Forwarded-For), and remote DNS keeps lookups off your machine. But neither protocol encrypts anything by itself.
No. SOCKS5 is a relay, not a tunnel. Your HTTPS traffic stays encrypted end-to-end as usual, but plain protocols remain readable to anyone on the path, including the proxy operator.
A VPN encrypts and routes your whole device and is better for privacy. SOCKS5 is per-application, faster (no encryption overhead), and ideal when you need one tool — not the entire system — to exit from a different IP.