HProxy · Free United States pool
Free United States proxy list 2026
Each US entry below stays listed for two days after our checker last heard from it. Most are ports on a few gateway servers, so check where one exits before you rely on it.
The table pages through the proxies that answer right now first, not the whole pool. Copy and Download take all 18,878 that match your filters.
You're viewing free US proxies. See the full list.
Browse the complete free proxy list: every country, protocol and anonymity grade, in one live view.
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.
United States proxies right now, by the numbers
The pool currently holds 500 United States proxies spread across 68 different networks. They respond in 2422ms at the median, quicker than the 3468ms median across the whole free pool. The busiest exits are Ashburn, North Bergen, Dallas. These figures come straight from the live pool and move every few minutes as proxies are re-verified.
By anonymity
Biggest hosting networks
About
The US list, sampled and tested
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 US proxies.
The list above holds every free proxy with a United States address that answered our checker recently. When an entry works, the site usually sees an American address, though often not the one you copied.
At 15:46 UTC on September 27, 2026, 17,519 of the 74,427 US entries in rotation were alive. That was 82.6 percent of every live entry in our free pool, far more than any other country. All 74,427 had been checked within the previous day, and 66,841 within the previous hour.
The count hides how narrow the list is: those 17,519 live entries sat on just 405 addresses. Of them, 15,803 sat on 37 addresses belonging to one hosting company. On average each of those addresses answers on over 400 ports, and each port is an entry.
Most of those ports do not send your traffic out from the address you copied. In our test, not one of 73 gateway entries that relayed a request exited through its listed address. At least 44 of them exited through home or mobile providers such as Comcast, Charter, Verizon and T-Mobile.
Live US entries pass more of their checks than the rest of the pool, yet they die sooner. Off the gateway servers, a typical live US entry passed 69.9 percent of its checks; elsewhere, 32.9. With the gateway ports counted, the US figure falls to 41.0 percent. The median US entry that died was gone after about 7 days; the rest lasted about 10. Those counts leave out busy addresses, Amazon's networks and one June evening when our checker failed.
Timed from our server in the United States, the median live US entry took 19.0 seconds to answer. Off the gateway servers it was 3.2 seconds, faster than the 6.7 elsewhere in the pool. Nearly all listed US entries sit on datacenter space, even when the exit behind is a home connection. Jobs that must keep a US address all day are what paid US proxies are for.
01
The United States against the rest of the free pool
Both columns of every row come from the same minute of our pool.
| Measured September 28, 2026 | United States | Rest of the pool |
|---|---|---|
| Live entries measured | 473 | 3,537 |
| Median success rate across its own checks | 69.9% | 32.9% |
| Passed ten checks at 90 percent | 40.0% | 4.8% |
| Median latency from our server in the United States | 3,220 ms | 6,653 ms |
| Answered in under one second | 28.1% | 4.1% |
| Median lifespan of entries that died | 161 hours | 240 hours |
| Died within a day | 28.2% | 24.3% |
| On datacenter address space | 57.1% | 18.6% |
The lifespans were read at 15:55 UTC on September 28, 2026, every other figure at 12:16. Both came a day after the counts above. A row skips any address that holds 20 or more of the entries it counts. In the US that removed 38 gateway addresses, which held 12,543 of the 13,016 live entries. Lifespans end at each entry's last answer, leaving out Amazon's networks and the June evening our checker failed.
US entries answer more of their checks while they live, but they do not live as long.
Counting the gateway addresses, 98.4 percent of live US entries sat on datacenter space. Only 3.6 percent of them passed ten checks at 90 percent, against 40.0 percent without.
02
A few servers behind thousands of entries
The US list looks wide on paper, but a few networks carry almost all of it. Each operator name below is the one the registry records for that network number.
| Operator, as the registry names it | Network | Live entries | Addresses |
|---|---|---|---|
| Secured Servers LLC | AS19437 | 13,361 | 13 |
| Secured Servers LLC | AS20454 | 2,442 | 24 |
| M247 Europe SRL | AS9009 | 1,261 | 9 |
| Performive LLC | AS46562 | 84 | 84 |
| Cox Communications Inc. | AS22773 | 70 | 70 |
| All live US entries | 88 networks | 17,519 | 405 |
Live US entries in our pool at 15:46 UTC on September 27, 2026. Operator names from ARIN and RIPE NCC registry records read the same day.
Cox is the one home provider near the top: its 70 entries sit on 70 separate addresses. Ashburn and Phoenix alone hold 15,815 live entries, and only three US cities hold 25 or more.
03
Where a free US proxy really exits
Our public list API returned 25,000 US entries at 01:18 UTC on September 28. We drew 1,000 of them at random: 600 from the 26 gateway addresses, and 400 from the rest. A gateway address here is one that carries 100 or more entries of the list.
From our server in the United States, we asked an echo service for each exit address. Then we opened Cloudflare and Google through it, with 30 seconds for each request.
| Tested at 01:18 UTC, September 28, 2026 | Gateway entries | Other entries |
|---|---|---|
| Sampled and tested | 600 | 400 |
| Did not accept a connection | 320 | 117 |
| Completed at least one request | 125 | 130 |
| Relayed our echo with a visible exit | 73 | 103 |
| Exited through the listed address | 0 | 58 |
| Exited in the United States | 58 | 91 |
| Opened Google | 50 | 56 |
| Failed a certificate check | 0 | 102 |
HProxy test from one server in the United States, with exit countries from the ip-api.com echo. The Google row counts entries through which www.google.com/generate_204 answered.
The 58 gateway exits inside the country came from 25 different states. Only 4 of them left from the state our list records for that entry. So a listed location shows where a gateway sits, not where your traffic leaves.
Nearly all 102 certificate failures had one of two causes; the first is the one to worry about. 36 SOCKS5 entries, mostly on Cox and Performive addresses, showed an expired certificate for Cloudflare or Google. Our direct check saw valid ones, so something on those paths replaced them. That is what interception of encrypted traffic looks like from outside the connection.
Another 65 came from entries on Amazon cloud addresses. None of the 97 we sampled there relayed our echo, and only one of them opened Google.
04
Who is behind a free home exit
A gateway that sends your traffic out through a home connection needs somebody's home connection. From a list, nobody can tell whether that person agreed to it.
The FBI has described how some residential proxy networks of this kind were built. The 911 S5 service ran on over 19 million compromised addresses in over 190 countries (FBI, May 2024).
Its free VPN apps came packaged within pirated games and software. In June 2025 the FBI warned about BADBOX 2.0, a botnet of infected home devices. Criminals sell access to those compromised home networks, or give it away for free.
We make no claim about any address on this list. A free exit on a home connection is an unknown, and it should never carry a login.
05
How to use a free US proxy
Copy the address, the port and the protocol of one row into your tool together. Browsers and scrapers work with HTTP and HTTPS entries; SOCKS5 entries also carry other programs' traffic.
Test the entry against a page that shows your address and location before real work. A gateway entry exits from an address that is not the one you copied, often in another state.
Keep several entries ready and switch when one stops, since no single address stays up for long. More than a quarter of the US entries that died had lasted less than a day.
Nothing you send through a free SOCKS5 entry gets encrypted by the entry itself. RFC 1928 leaves encryption to whatever method the two ends pick at the start. Free entries choose no authentication, so the proxy itself encrypts nothing.
Check each entry's anonymity grade as well, because a few entries give you away. A transparent entry passes your own address on to the site, for example in an X-Forwarded-For header. On September 27, 2026, 38 live US entries were graded transparent.
Questions
Frequently asked.
Yes, at no cost and with no signup. Many people share each entry, so test one right before you depend on it.
Because many entries are ports on a few gateway servers. On September 27, 2026, 15,803 of 17,519 live US entries sat on 37 addresses of Secured Servers.
US entries that answered and then died lived a median of about 7 days. The rest of our pool lived about 10 days. Addresses with 20 or more such entries, Amazon's networks and one June evening stay out of both medians.
Treat every entry as public: its operator sees any traffic you send without encryption. In our test, 36 SOCKS5 entries showed an expired certificate for Cloudflare or Google, a sign of interception. Never send a login or a payment through one.
Most do, but often not from the address you copy. Our test on September 28, 2026, placed 149 of 176 visible exits inside the United States. None of the 73 relaying gateway entries exited through its listed address.
Not reliably, because the list and the exit disagree. The state our list records is where the listed address sits, mostly Virginia or Arizona. In our test, only 4 of 58 US gateway exits left from the listed state.
Most are ports on gateway servers, which send your traffic on through a second connection. Timed from our server in the United States, half the live US entries took 19.0 seconds or more. Off those servers, the median was 3.2 seconds.
For steady work, HProxy sells US proxies you can target down to the city. Purchased traffic has no scheduled expiry date, and billing works without any subscription.
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.