SOCKS4 proxies forward TCP traffic from any network application while hiding your real IP address from the remote server. SOCKS4 does not support UDP or IPv6. Learn more about what SOCKS4 proxies are in our knowledge base, or buy premium access to get the list of all available servers.
| Address and type | |||||
|---|---|---|---|---|---|
South Korea Seoul | Medium | 4 sec. ago | |||
Brazil Pombos | Low | 4 sec. ago | |||
Netherlands Amsterdam | Low | 4 sec. ago | |||
United States Los Angeles | Medium | 7 sec. ago | |||
Morocco Casablanca | Low | 7 sec. ago | |||
Singapore Singapore | Medium | 8 sec. ago | |||
Indonesia Semarang | Medium | 10 sec. ago | |||
India Mumbai | Low | 10 sec. ago | |||
United States Delaware | Low | 10 sec. ago | |||
Russia Moscow | Medium | 11 sec. ago |
SOCKS4 is a transport-layer proxy protocol. It redirects TCP traffic from any application and does not expose the client IP to the target server. The protocol does not support UDP or authentication.
SOCKS4 only supports TCP connections and has no built-in authentication. SOCKS5 additionally supports UDP, IPv6, and login/password authorization, making it more flexible.
SOCKS4 proxies hide the IP in TCP applications, help bypass network blocks, work in proxy chains, and maintain a basic level of privacy.
Most modern applications support SOCKS4, but if the application requires UDP, IPv6, or authentication, SOCKS5 is necessary.
SOCKS4 proxies most commonly run on ports 1080 (SOCKS standard), 1081, and 4145. Port 1080 is the most widespread for all SOCKS proxy types.