SOCKS proxies work at a low network level, so almost any network application can run through them. They do not pass the client IP address to the remote server and support chaining, which further increases anonymity. You can learn what SOCKS proxies are in our knowledge base, or buy premium access to get the list of all available servers.
| Address and type | |||||
|---|---|---|---|---|---|
India Noida | Low | 1 sec. ago | |||
France Strasbourg | Low | 1 sec. ago | |||
Lithuania Kaunas | Low | 1 sec. ago | |||
United States Los Angeles | Low | 2 sec. ago | |||
Vietnam Ho Chi Minh City | Low | 2 sec. ago | |||
Russia Moscow | Low | 2 sec. ago | |||
United States Atlanta | Low | 3 sec. ago | |||
India Noida | Low | 3 sec. ago | |||
United States Jacksonville | Low | 3 sec. ago | |||
Algeria Bordj el Kiffan | Medium | 3 sec. ago |
This page combines SOCKS4 and SOCKS5 in one list. Useful when you need a single SOCKS address pool without splitting by protocol version. You can then move to the SOCKS4 or SOCKS5 pages for a more precise choice.
The combined list is convenient when the protocol is not yet decided: it works for parsing, automation, and desktop applications. Choose SOCKS4 for TCP-only tasks without authentication. Choose SOCKS5 when you need UDP, IPv6, or login and password.
SOCKS proxies most often run on ports 1080, 1081, 4145, and 9050. The exact port depends on server configuration and protocol implementation, so it is best to check response time and last verification time in the table before using them.
SOCKS4 works over TCP only and does not support authentication. SOCKS5 adds UDP, IPv6, and login/password, making it suitable for gaming, VoIP, and tasks requiring authorization. When the protocol does not matter, SOCKS5 covers all SOCKS4 use cases.
Yes, most browsers and applications support SOCKS4 and SOCKS5 in their proxy settings. Specify the address, port, and protocol type. SOCKS5 also allows you to set a login and password for authentication.