HProxy · Free United Kingdom pool
Free United Kingdom proxy list 2026
Our checker revisits every UK entry below, and one that stays silent for two days drops off. Most entries failed our deeper test, so check one yourself before you rely on it.
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 Kingdom proxies right now, by the numbers
The pool currently holds 147 United Kingdom proxies spread across 37 different networks. They respond in 1802ms at the median, much quicker than the 4188ms median across the whole free pool. The busiest exits are City of London, Slough, London. These figures come straight from the live pool and move every few minutes as proxies are re-verified.
By anonymity
Biggest hosting networks
About
What the UK list did in our tests
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 UK proxies.
The list above holds every free UK proxy that answered our checker within the last two days. Copy an address and a port into your browser or tool. When the entry works, sites you open most often see a UK address.
On September 27, 2026, at 17:02 UTC, 14 of the 147 listed entries had passed their latest check. Of the 18,689 live entries in our whole pool at 17:01 UTC, only 14 were in the UK. Most UK entries never work: 11,172 of the 11,689 we retired off busy addresses never answered once.
At 01:17 UTC on September 28, three Amazon cloud addresses carried 60 of the 129 rows. Each held 8 to 29 of them, one per port, all marked HTTPS. We tested every entry, and none of the 60 carried a request to the site we asked for.
Asked to open Cloudflare, 35 of them presented a certificate our server could not verify. Every one we examined bore Cloudflare's name, but none was Cloudflare's real certificate. A proxy that just relays traffic leaves the site's own certificate untouched. One that shows its own can read everything you send, if you accept the browser warning.
Only a few of the other 69 entries worked; they sat on 59 addresses in 39 networks. In our test, 17 of them completed a request and 14 relayed our echo. Only 9 of those left from the address we listed, inside the UK.
Live UK entries were quick: 2.4 seconds at the median, measured from our server in the United States. UK entries that worked for a while and then went dead lasted about 6 days at the median. That median skips busy addresses, Amazon's networks and the June evening our checker failed. For a UK address that has to keep working, paid UK proxies are built for the job.
01
The UK against the rest of the free pool
The 14 live UK entries of 17:01 UTC stand against the rest of the pool, busy addresses aside.
| Measured September 27 to 28, 2026 | United Kingdom | Rest of the pool |
|---|---|---|
| Live entries measured | 14 | 3,992 |
| Median success rate across its own checks | 66.2% | 34.4% |
| Passed ten checks at 90 percent | 21.4% | 8.9% |
| Median latency from our server in the United States | 2,410 ms | 6,447 ms |
| Answered in under one second | 28.6% | 6.9% |
| Median lifespan of entries that died | 136 hours | 237 hours |
| Died within a day | 26.6% | 24.7% |
| Retired entries that never answered once | 95.6% | 88.4% |
| On datacenter address space | 64.3% | 23.0% |
We read the UK live figures at 17:01 UTC on September. 27 The rest of the table comes from 12:16 UTC the next day, the lifespans from 17:17. Each row drops busy addresses, meaning 20 or more of the entries that row measures. No lifespan counts Amazon's networks, or entries marked dead on the failed evening of June. 14
With only 14 live entries, a single server moves every share in this table. Our server sits in the United States, and the UK entries were fast even across the Atlantic.
02
Three Amazon addresses behind nearly half the list
When we read our public list API at 01:17 UTC on September 28, it held 129 UK entries. We tested each of them through itself, asking an echo service for the exit. Cloudflare and Google came next, each opened through the entry with 30 seconds to answer.
| Tested at 01:17 UTC, September 28, 2026 | On 3 Amazon addresses | On 59 other addresses |
|---|---|---|
| Entries on the list | 60 | 69 |
| Passed their latest check | 0 | 25 |
| Did not accept a connection | 0 | 27 |
| Completed at least one request | 0 | 17 |
| Relayed our echo with a visible exit | 0 | 14 |
| Exited in the UK from the listed address | 0 | 9 |
| Opened Google | 0 | 11 |
| Failed a certificate check | 35 | 0 |
All requests came from one HProxy server in the United States; exit countries are ip-api.com's. Google here is www.google.com/generate_204, the connectivity check we fetched through every entry.
Each Amazon row stays listed since it passed some of our routine checks during the past two days. In our test, not one of them relayed a request to any site we asked for.
A certificate probe at 01:18 UTC reached 28 of them, and every one finished the encrypted handshake. Each showed a certificate made out to www.cloudflare.com that our server could not verify. Their issuer names ranged from Let's Encrypt and Microsoft Azure to Tuya Smart Device. We checked nine against the real authority's own certificate, and all nine failed.
All 28 also answered a request for a plain web page, using 24 different server names. One port called itself IBM_HTTP_Server and another cisco-IOS, yet every reply said: Could not connect.
We do not know who runs the three Amazon servers. They acted more like a honeypot than like a proxy. NIST's glossary calls a honeypot a system designed to attract intruders.
03
Where a free UK proxy really exits
Nine of the 14 relaying entries exited from the listed address, inside the UK. None left from another UK address.
The other 5 exited abroad: three in Helsinki, one in Frankfurt and one in Istanbul. All five left from the very address our list places in the UK, so the databases disagree.
Seven of Cloudflare's answers through the working entries came from London. The other 6 came from data centers in five other cities, among them Frankfurt and Düsseldorf. A UK row is a database's view of an address, so check the exit yourself.
04
A UK address brings UK rules
A UK exit makes you look like a UK visitor, and UK rules come with that. Under the Online Safety Act 2023, sites that publish pornographic content must check their users' ages.
That duty has applied since January 17, 2025, according to the UK government. The Act also reaches services abroad that have many UK users or target the UK. So a free UK exit can bring an age check with it.
05
How to use a free UK proxy
Set up the proxy with all three parts of a row: address, port and protocol. The Network column matters too, since the Amazon rows carried no traffic at all in our test.
Before real work, check your address and its country on a page opened through the entry. About two in three relaying UK entries left from the listed address inside the UK.
If your browser warns that a connection is not private, drop that proxy and try another.
A free SOCKS5 entry does not encrypt your traffic by itself. RFC 1928 lets client and server agree on a protecting method, and free entries choose no authentication instead.
Keep a few entries in rotation instead of trusting any single address to stay up. One in four UK entries that died was gone within 18 hours.
Questions
Frequently asked.
Yes, all of them: copying and using an entry costs nothing, and you need no account. Other people use the same entries, so test one right before any real task.
Almost half the rows sit on addresses that relay nothing. Not one of the 60 rows on the three Amazon addresses carried traffic on September 28, 2026.
Our server in the United States waited a median 2.4 seconds for a live UK entry to answer. The rest of our pool, busy addresses aside, took a median 6.4 seconds.
Only a few: on September 27, 2026, 3 of the 14 live UK entries carried a London location. Three more sat in Slough, all three on a single cloud server.
Most do, though not all. Tested from our server in the United States, 9 of 14 relaying entries used the listed UK address. Finland, Germany and Turkey took the other five, on September 28, 2026.
Treat them as public, since whoever runs one can read what you send without encryption. In our test, 35 entries on Amazon addresses presented a certificate our server could not verify. Keep every login and payment off them.
Half of the UK entries that answered and later died were gone within about 6 days. A quarter of them were gone within 22 hours. Entries elsewhere in our pool lasted about 10 days. Both sides ignore Amazon's networks, one June evening and any address with 20 or more such entries.
For work that must keep running, HProxy offers UK residential, static ISP, mobile and datacenter proxies. Residential plans can aim at a single UK city, and purchased traffic has no scheduled expiry date.
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.