HProxy · Free France pool
Free France proxy list 2026
Every row below is a proxy listed under France that answered our checker within two days. We sent traffic through all 341 on 28 September, and 77 of them relayed it.
FranceTransparentYou're viewing free French 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.
Free proxies by country
24 pages
France proxies right now, by the numbers
The pool currently holds 334 France proxies spread across 23 different networks. They respond in 6995ms at the median, much slower than the 3081ms median across the whole free pool. The busiest exits are Paris, Lauterbourg, Roubaix. These figures come straight from the live pool and move every few minutes as proxies are re-verified.
By anonymity
Biggest hosting networks
About
How the France list held up in our test
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 French proxies.
Set a row's address, port and protocol in your browser, and sites see the entry instead of you. Our test found 51 French exits among the 77 entries that relayed a request.
At 23:31 UTC on 27 September 2026, the France list held 347 entries, 105 of them live. That put France tenth among the countries in our pool by live entries. Of the rest, 73 sat on three Amazon addresses, and none had passed a check since 26 September.
Three networks carried most of the live entries: Contabo with 37, OVH with 30 and Scaleway with 21. Our location data places all 37 Contabo entries in Lauterbourg, in the Grand Est region. Paris came next with 27 live entries, and 15 had no city at all.
All 341 entries the list held at 00:26 UTC on 28 September went through our test. Requests left from our server in the United States, each with 30 seconds to finish. 87 never accepted a connection and 77 relayed our request. Of those 77, 47 left from the listed French address itself.
For French entries that answered and later stopped for good, the median lifetime was about 10 days. Elsewhere it was about the same, so a typical French entry lasted as long as the rest. Both counts leave out addresses with 20 or more such entries, which sets aside 1,558 French entries. Amazon's networks are skipped too, and so is the June evening our checker failed.
Our checker graded 25 of the 105 live entries transparent, so sites see your own address. For work that needs a French address to stay put, paid France proxies are the steadier choice.
01
The French slice next to the whole pool
France's column dates from 23:31 UTC on 27 September; busy addresses stay out of both.
| Measured 27 to 28 September 2026 | France | Rest of the pool |
|---|---|---|
| Live entries measured | 105 | 3,940 |
| Median success rate across its own checks | 52.1% | 34.2% |
| Passed ten checks at 90 percent | 12.4% | 8.8% |
| Median latency from our server in the United States | 9,532 ms | 6,372 ms |
| Answered in under one second | 11.4% | 6.9% |
| Median lifespan of entries that died | 241 hours | 235 hours |
| Died within a day | 27.5% | 24.6% |
| Lasted more than 30 days | 31.4% | 30.9% |
The French live side of the table is our 23:31 UTC read of 27 September. We read the rest column a day later, at 12:17 UTC, and every lifespan at 17:18. Lifespans count entries that answered and later died, on addresses with fewer than 20 of them. Live rows drop addresses with 20 or more live entries. Amazon's networks and the June evening our checker failed are left out of every lifespan.
Live French entries were steadier than the rest of the pool, though slower. One in eight passed ten checks at 90 percent, against about one in eleven elsewhere. Their lives were uneven, with more dying inside a day and more lasting past a month.
02
What each France row did in our test
Through each entry we fetched an address echo, then Cloudflare, then Google's connectivity check.
| Tested 28 September 2026 | On 3 Amazon addresses | On 168 other addresses |
|---|---|---|
| Rows on the list | 69 | 272 |
| Passed their latest check | 0 | 113 |
| Did not accept a connection | 0 | 87 |
| Completed at least one request | 0 | 103 |
| Relayed our echo | 0 | 77 |
| Came out in France | 0 | 51 |
| Left from the listed address in France | 0 | 47 |
| Opened Google | 0 | 58 |
| Failed a certificate check | 35 | 0 |
The test ran from our server in the United States, and ip-api.com located every exit address.
By protocol off Amazon, SOCKS5 rows relayed 15 of 40 and HTTP rows 44 of 163. HTTPS rows gave 16 of 64, and the five SOCKS4 rows, asked in plain SOCKS4, gave 2.
03
Three Amazon addresses in Paris
At 00:26 UTC, the three Amazon addresses carried 69 rows, all placed in Paris and all offering HTTPS. They last passed a check on 26 September, and our test found nothing behind them.
At 00:32 UTC we went back to 24 of them. Fifteen finished the encrypted handshake, and each showed a certificate made out to www.cloudflare.com. Their issuers carried names from Amazon and Go Daddy to Verifone and HashiCorp Vault. Seven named a public authority, and we tested six against that authority's own key. All six signatures failed; the seventh row stopped letting us through before we could test it.
A plain web request drew "Could not connect" from 20 of them, under 20 different server names. One gave its server name as Sonos, and another as HP Web Jetadmin.
We cannot see who runs these three addresses, yet they fit a honeypot better than a proxy. NIST's glossary defines that as a system designed to be attractive to potential crackers and intruders.
04
Where the working entries came out
Of the 77 entries that relayed our request, 26 exited outside France. Four left from their own listed address, which ip-api.com places in Germany, the UK or the Netherlands.
Our list also files 25 rows under France while naming a city abroad, 13 of them Köln. Four of those relayed our request, and three came out outside France.
The Tor Project's own check got through 40 working entries and found three on Tor. All three sit on OVH addresses. A site then sees the exit relay, the final relay in a Tor circuit, instead of the entry. None exited in France: their Tor relays sat in the Netherlands and Germany.
Cloudflare answered through 60 entries and tagged eight requests T1, its code for Tor traffic. Of the 40 requests it placed in France, it served 22 from Frankfurt and only 12 from Paris.
05
The Uptime column on the France list
For every tested row, we compared the result with the Uptime figure the list printed beside it. At 75 percent or more, 20 of 27 rows relayed; under 50 percent, only 36 of 263 did.
The 69 Amazon rows all showed less than 25 percent, and none relayed anything. On this list, a high Uptime was a fair first filter.
06
How to use a free French proxy
Sort by Uptime first: 20 of the 27 rows at 75 percent or more relayed our request.
Pass over rows on Amazon's network, and expand each row to check its city. Then open a page through the entry that reports your country: 26 of 77 working entries exited elsewhere.
Keep passwords and payments off every free entry, since its operator can read anything you send without HTTPS.
Questions
Frequently asked.
Yes: nothing to pay and no account to open, but everyone shares these rows, so test one first.
Many rows stop working between checks. In a test from our server in the United States, 87 of the 341 would not connect. The 69 Amazon rows relayed nothing at all.
On a typical live French entry, a request from our server in the United States took 9.5 seconds. Other live entries, busy addresses aside, came to a median of 6.4 seconds, so France was slower.
A few: 27 live entries carried Paris as their city on 27 September. Every Amazon row claims Paris too, and none of them relayed our request.
HProxy sells France proxies that target down to the city, paid as you go. Purchased traffic has no scheduled expiry date, and no subscription is needed to keep it.
Most of them: 51 of the 77 that carried our request on 28 September came out in France. The other 26 exited in 12 countries, most often Germany. We ran the test from our server in the United States.
Treat each one as a stranger's server. Its operator can read anything sent without HTTPS, and the 25 transparent live entries pass your address along.
A French entry that answered and later died lived a median of about 10 days, like the rest. Neither counts addresses with 20 or more dead entries, Amazon's networks or one June evening.
Cloudflare tagged eight of our requests as Tor traffic, and the Tor Project's own check confirmed three. All three exited outside France, so a site saw a Tor exit relay, not a French address.
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.