SOCKS stands for SOCKet Secure. SOCKS is an internet protocol for exchanging data packets between a client and a server through a third device – a proxy. The two current versions are 4 and 5.
The definitive quality of SOCKS is that it is designed to route multiple types of traffic across a wide range of ports.
Most other proxies act on the application level (service, single port). They can route only the type of traffic specific to that service (i.e., HTTP, email, etc.) SOCKS protocols belong at the Sessions layer 5 of the OSI model: by definition, session layers can include several protocols, applications, or services. It makes them a more versatile routing solution than most web proxies typically set up at the services layer (one proxy – one specific service.)
SOCKS-enabled proxy servers can be used to:
There are only two versions of the SOCKS protocol: SOCKS4 and SOCKS5 (technically, also 4a).
The SOCKS5 protocol was originally a security protocol simplifying firewall and authentication implementation. It has existed since 1996 and is outlined in RFC 1928.
The main differences between SOCKs5 and SOCKS4 are:
The SOCKS proxy is an intermediate node or relay that filters and directs the traffic further. Once configured, the SOCKS proxy handles all the back and forward between you (the client) and the server transparently.
If the client is exchanging TCP data, SOCKS forwards the data over the established TCP connection. If the client is exchanging UDP data, the TCP connection might have to be used to establish the initial connection for communication (handshake) because the UDP protocol itself is not suitable for it. After that, TCP is only used for the proxy’s success replies and the client’s instructions on where to send the UDP packets. A separate UDP relay is used to move UDP traffic.
HTTP proxies are protocol (application) layer proxies: they can only work with HTTP/HTTP(s) traffic. You need to establish a separate connection for each protocol you want to exchange through proxy: for example, emails would have to be set up separately. This means a better connection speed over each one but also a significantly more complicated configuration when you need more than one protocol.
SOCKS5 proxies can work with many traffic types: HTTP, HTTP(s), FTP, POP3, and SMTP. So SOCKS can be used for P2P (peer-to-peer) file transfers, email exchange, and more. You just need to make sure your proxy service provider has all the ports you need open, otherwise the proxies would not be any different from HTTPs.
SOCKS5 UDP protocol allows for establishing a fast enough connection for Real-Time Streaming Protocol, Voice over IP, and more. It means you might succeed with video streaming and online gaming as long as the proxy server remains the same.
When a proxy rewrites data headers, it takes extra time and might lead to errors or misrouting. SOCKS5 proxy servers do not rewrite data packet headers; hence the performance improves. This also means that some of your personal information is still exposed to any surveillance program that uses deep analysis and not just looks at the last source’s IP address. If anonymity is important, SOCKS should be used with another protocol on top of it (i.e. Tor network).
As long as you have permissions, access the gateway node of the network with SSH protocol. You can now use a single proxy instead of several application-specific ones.
SOCKS protocols are well-documented, and all the information is easily accessible:
How to set up a SOCKS5 SOAX proxy manually on Windows 10:
How to set up a SOCKS5 SOAX proxy manually on macOS:
A SOCKS proxy is a versatile and fast proxy of layer 5 of the OSI model, useful for multiple types of traffic. SOCKS5 proxy is an excellent improvement to version 4. In your SOAX Dashboard, you can easily access and configure a SOCKS5 residential proxy network for your own needs.