SOCKS-Proxy
Embed This Widget
Add the script tag and a data attribute to embed this widget.
Embed via iframe for maximum compatibility.
<iframe src="https://ipfyi.com/iframe/glossary/socks/" width="420" height="400" frameborder="0" style="border:0;border-radius:10px;max-width:100%" loading="lazy"></iframe>Paste this URL in WordPress, Medium, or any oEmbed-compatible platform.
https://ipfyi.com/glossary/socks/Add a dynamic SVG badge to your README or docs.
[](https://ipfyi.com/glossary/socks/)Use the native HTML custom element.
Definition
Ein universelles Proxy-Protokoll (SOCKS4/SOCKS5), das beliebigen TCP- (und optional UDP-) Datenverkehr über einen Proxy-Server weiterleitet. Im Gegensatz zu HTTP-Proxys arbeitet SOCKS auf einer niedrigeren Ebene und ist protokollunabhängig.
SOCKS Protocol Versions
SOCKS4 supports only TCP connections and requires a fixed destination IP. SOCKS4a extended this to support hostname resolution by the proxy server. SOCKS5, the current standard (RFC 1928), adds UDP support, authentication (username/password or GSSAPI), and IPv6. SOCKS5 is by far the most widely deployed version in practice.
Unlike HTTP proxies, which understand HTTP semantics and may modify headers, SOCKS operates at the transport layer. It establishes a TCP or UDP relay without inspecting or modifying application-layer data. This makes SOCKS suitable for any protocol: web browsing, SSH, database connections, or any other TCP-based application.
How SOCKS5 Works
A client opens a TCP connection to the SOCKS5 Proxy ServerAn intermediary server that forwards requests between a client and destination server. Forward proxies anonymize client traffic; reverse proxies sit in front of servers for load balancing, caching, and security. server. After an authentication handshake, the client sends a CONNECT command with the destination address and port. The proxy resolves the hostname if needed and opens a TCP connection to the destination. From that point, all data flows transparently through the proxy in both directions without further protocol involvement.
Common Use Cases
SSH includes built-in SOCKS5 proxy functionality: ssh -D 1080 user@remotehost creates a local SOCKS5 listener. All traffic routed through port 1080 tunnels through the SSH connection. This is commonly used to access resources on private networks or to route browser traffic through a trusted server when on untrusted public Wi-Fi.
TorThe Onion Router. An anonymity network that routes traffic through multiple encrypted relays (typically three) worldwide, making it extremely difficult to trace the origin of a connection. The basis of .onion hidden services. uses SOCKS5 as its client interface — applications connect to the Tor client's local SOCKS5 listener (default port 9050) to route traffic through the anonymization network. Use IP Lookup to confirm your apparent IP address when routing through a SOCKS proxy.