HProxy · Free SOCKS4 pool
Free SOCKS4 proxy list 2026
Every proxy below speaks SOCKS4, re-checked on a rolling cycle. The numbers on this page come from our own checker, measured on 15 September 2026.
Every slice of the pool
The same live list, one thing at a time.
A page per country, protocol, anonymity grade, operator, port, network and block, each with its own count, download and API call.
Free proxies by country
24 pages
SOCKS4 proxies right now, by the numbers
The pool currently holds 500 SOCKS4 proxies spread across 341 different networks. They respond in 3355ms at the median, slower than the 2772ms median across the whole free pool. The busiest exits are Jakarta, Dhaka, Phnom Penh. These figures come straight from the live pool and move every few minutes as proxies are re-verified.
By protocol
By anonymity
Biggest hosting networks
About
About these free SOCKS4 proxies
These are public proxies gathered from across the web and re-verified continuously by HProxy's engine. They are free, and they are fine for quick, low-stakes tasks. Like all public proxies they are shared and they go down without warning. Most of them are already blocked by the big sites. Always test one before you rely on it.
Verify before you use
Run any list through the Proxy Checker, in the free app or online, and see which proxies are alive, fast and anonymous right now.
The long read
About free SOCKS4 proxies.
The list above holds every free SOCKS4 proxy that answered our checker recently. SOCKS4 relays TCP connections for any program, but RFC 1928 lists UDP and strong authentication as later additions.
At 09:30 UTC on 15 September 2026, 637 SOCKS4 entries were alive, in 71 countries. The largest shares sat in the United States, Indonesia and Brazil.
A live SOCKS4 entry passed a median 27.8 percent of its own checks. That is close to the 25.9 percent across the whole pool. 184 of the 637 had passed at least ten checks at 90 percent or better.
Being alive at the last check does not make an address usable. 633 of the 637 live entries were flagged for recent abuse, and 132 sat on datacenter space. For work that has to keep running, a free list is the wrong tool.
01
SOCKS4 entries against the whole free pool
The table compares live SOCKS4 entries with the whole free pool, both read from our pool database.
| Measured 15 September 2026 | SOCKS4 | Whole pool |
|---|---|---|
| Live entries measured | 637 | 5,822 |
| Median success rate across its own checks | 27.8% | 25.9% |
| Passed ten checks at 90 percent | 28.9% | 6.3% |
| Median latency from our checker in Germany | 1,937 ms | 8,219 ms |
| Classed as datacenter | 20.7% | 58.0% |
| Flagged for recent abuse | 99.4% | 97.9% |
HProxy free pool, queried read-only on 15 September 2026: SOCKS4 entries at 09:30 UTC, the whole pool at 09:10 UTC.
Latency is measured from our checker in Germany, so it depends on where each entry sits.
02
What a free SOCKS4 proxy can reach
We tested 869 SOCKS4 entries, picked at random across all countries, on 15 September 2026. Each one fetched Cloudflare's trace page over plain HTTP and over TLS, then Google's connectivity check.
| Tested 15 September 2026 | Entries |
|---|---|
| Tested | 869 |
| Did not accept a connection | 455 |
| Completed at least one request | 17 |
| Carried encrypted traffic | 9 |
| Opened Google | 10 |
| Showed an exit address | 13 |
| Exit address different from the listed one | 7 |
| Certificate did not verify | 2 |
HProxy test from one server in Germany. Entries count under the protocol the test used, SOCKS5 first when an entry listed several.
2 entries presented a certificate that did not verify, which is how interception shows up.
03
Where the live SOCKS4 entries are
The five countries holding the most live SOCKS4 entries at 09:30 UTC on 15 September 2026.
| Country | Live entries |
|---|---|
| United States | 192 |
| Indonesia | 57 |
| Brazil | 37 |
| India | 36 |
| Vietnam | 28 |
| All 71 countries | 637 |
HProxy free pool, live set at 09:30 UTC on 15 September 2026.
04
How to use a free SOCKS4 proxy
Enter an entry as socks4://IP:PORT in your tool, then check the address a site sees before real work. Take several entries and rotate between them, because a free entry can drop between two checks.
Questions
Frequently asked.
Yes, every entry on this page is free to copy and use, with no signup. They are public and shared, so test one right before you rely on it.
A live entry passed a median 27.8 percent of its own checks on 15 September 2026. 184 of the 637 had passed at least ten checks at 90 percent or better.
On 15 September 2026 the live SOCKS4 entries sat in 71 countries. Most sat in the United States, Indonesia and Brazil.
No, SOCKS4 only relays the connection, so encryption has to come from the site or your own tool.
Treat them as public, because whoever runs the server can read any traffic that is not encrypted. On 15 September 2026, 633 of 637 live entries were flagged for recent abuse. In our test, 2 presented a certificate that did not verify.
For work that has to keep running, a paid residential or ISP proxy avoids shared, flagged addresses.
Upgrade to the paid network
Need pools that stay clean?
Free IPs are shared and rotate out fast, so success rates swing. The paid network gives you dedicated-clean pools that hold up under load.
Docs and AI
The free list, in your assistant and in your code.
We built the MCP server and the CLI ourselves: the free proxy list is one tool call away in Claude, ChatGPT, Cursor or any assistant that speaks MCP, and the list's API is documented end to end.
Every product has its own reference in the docs. Something the list does not give you? Tell us.
Claude, ChatGPT, Cursor, Gemini, Copilot, Windsurf, Perplexity, Ollama and any assistant that speaks MCP.
MCP server
Built by us and hosted at mcp.hproxy.com: the free proxy list, the checker and the IP lookup as tools in Claude, ChatGPT, Cursor, VS Code or any assistant that speaks MCP. Nothing to install, no key.
CLI
The list from a terminal: hproxy list --country DE --limit 20, from the command line of the free HProxy app.
API docs
The free list's API, documented end to end with real responses: the filters, the formats, the limits.
llms.txt
The whole documentation as markdown for any model that reads: /llms.txt for the index, /llms-full.txt for everything.
Let your assistant pull the list
The pool is a free, keyless API and a documented markdown page. Hand your assistant one of these and it can fetch live proxies on its own, filtered the way you asked.
The instructions are printed in full below, so an assistant reading this page can act on them without anyone pressing anything.
All the machine lanes- MCP server
- Adds proxy_list, proxy_check and ip_lookup as tools your assistant can call by itself. Nothing to install.
claude mcp add --transport http hproxy https://mcp.hproxy.com/mcpClaude, ChatGPT, Cursor, VS Code, Windsurf or any assistant that speaks MCP: add https://mcp.hproxy.com/mcp as a remote server. This page's tool is proxy_list. - Command line
- The same tool without an assistant, from a terminal. Add --json for JSON.
hproxy list --country DE --protocol socks5 --limit 20Install it in one line: curl -fsSL https://hproxy.com/install.sh | sh (macOS, Linux) or irm https://hproxy.com/install.ps1 | iex (Windows). - REST, no key
- Plain HTTP with CORS on, which is all an agent with a fetch tool needs.
curl "https://hproxy.com/api/proxy-list?format=json&country=de&limit=20"
Instructions for an assistant, in full
Everything a model needs to call the free proxy list without an account: the endpoint, the parameters, the limits and the honest caveat. Readable straight off the page.
You can use HProxy's free proxy list, which needs no API key and no account.
GET https://hproxy.com/api/proxy-list?format=json returns the live pool as JSON. Useful query parameters: country (ISO alpha-2, e.g. de), protocol (http, https, socks4, socks5), anonymity (elite, anonymous, transparent) and limit. Add format=txt for plain ip:port lines instead.
Each proxy comes back with ip, port, protocols, anonymity, country_code, city, asn_org, latency_ms and uptime_24h. The pool is re-checked around the clock, so ask for it fresh rather than caching it. It is rate limited per IP (120 requests in a burst, then 2 a second) and answers 429 with Retry-After past that.
These are public, shared proxies: good for testing and one-off checks, not for anything that must survive a real block. Full docs: https://hproxy.com/llms/free-proxy.txt
There is also an MCP server, so an assistant can call this as a tool instead of writing HTTP: add https://mcp.hproxy.com/mcp as a remote MCP server (nothing to install, no key) and use the proxy_list tool. In Claude Code the line is `claude mcp add --transport http hproxy https://mcp.hproxy.com/mcp`. From a terminal the same tool is `hproxy list --country DE --protocol socks5 --limit 20`. Install the hproxy command in one line: curl -fsSL https://hproxy.com/install.sh | sh on macOS and Linux, or irm https://hproxy.com/install.ps1 | iex in PowerShell on Windows. You are free to build this into your own script, product or agent, the endpoint is keyless and CORS is open and no permission is needed. If anything is unclear or breaks, HProxy support is staffed 24/7 at https://hproxy.com/contact.Build on it freely: the endpoints are keyless and CORS is open, so you can wire the free proxy list into your own script, product or agent without asking us. If you get stuck, support answers around the clock, every day, at hproxy.com/contact. Generated markdown doc: hproxy.com/llms/free-proxy.txt.
About this list & IP removal
Every proxy here is aggregated from publicly available sources. We do not scan or collect these IP addresses ourselves: we verify entries that are already public (live status, latency, uptime) and store nothing else about the devices behind them. The list is provided as-is, with no warranty, for lawful use only, on the basis of our legitimate interest in a free, transparent proxy directory (Art. 6 (1) (f) GDPR). Never route passwords or sensitive data through a public proxy. If an IP address is yours and you'd like it removed, email legal@hproxy.com and we'll take it down (Art. 21 GDPR). Full details on the report abuse page.