HProxy · Free Germany pool
Free Germany proxy list 2026
The German entries below stay listed while our checker keeps hearing from them, for up to two days. Many entries failed our deeper test, so check where one exits before you rely on it.
GermanyEliteYou're viewing free German 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
Germany proxies right now, by the numbers
The pool currently holds 362 Germany proxies spread across 61 different networks. They respond in 2762ms at the median, slower than the 2105ms median across the whole free pool. The busiest exits are Frankfurt am Main, Nuremberg, Falkenstein. 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 German list under our own 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 German proxies.
Above this text is Germany's free list: entries that answered our checker in the past 48 hours. Copy an address and a port, and sites you open see an address other than yours. In our test, 57 of the 90 entries that relayed showed a German one.
When we read the list at 17:31 UTC on September 27, 2026, 79 of 399 entries were live. Germany had 79 of the 17,125 live entries in our whole pool at that minute. Most German entries never work at all: of the 9,763 retired off busy addresses, 8,410 never answered.
A quarter of the list sat on 4 Amazon cloud addresses in Frankfurt, all marked HTTPS. Our test on September 28 found 91 such entries among 357, and none carried a request anywhere. For Cloudflare, 34 of them produced a certificate that our server could not verify.
The other 266 entries sat on 199 addresses across 54 networks. In our test, 90 relayed our echo, and 50 left from the listed address inside Germany. Another 33 exited abroad, in 13 countries from Turkey to the Philippines.
By the Tor Project's own check, three entries handed our request to the Tor network. One live entry that did exit in Germany swapped in its own certificate for Cloudflare. Its issuer carried the name of SslBump, the Squid feature that decrypts HTTPS traffic in the middle.
Measured from our server in the United States, live German entries answered in a median 5.6 seconds. German entries that died lived a median of about 3 days, against about 10 for the rest. Those two medians ignore busy addresses, so no gateway dominates. Amazon's networks stay out too, and so does the evening in June when our checker failed. If a job needs a German address it can count on, paid German proxies are built for that.
01
Germany against the rest of the free pool
Busy addresses are left out of both columns below, and the German column dates from 17:31 UTC.
| Measured September 27 to 28, 2026 | Germany | Rest of the pool |
|---|---|---|
| Live entries measured | 79 | 3,930 |
| Median success rate across its own checks | 68.2% | 33.9% |
| Passed ten checks at 90 percent | 17.7% | 8.7% |
| Median latency from our server in the United States | 5,625 ms | 6,444 ms |
| Answered in under one second | 16.5% | 6.7% |
| Median lifespan of entries that died | 81 hours | 245 hours |
| Died within a day | 32.6% | 24.3% |
| Retired entries that never answered once | 86.1% | 88.7% |
| On datacenter address space | 70.9% | 22.1% |
Germany's live column comes from our 17:31 UTC reading of September. 27 The rest of the pool and both retired shares come from 12:16 UTC on September. 28 Addresses carrying 20 or more of a row's entries are dropped from that row. Every lifespan was read at 17:18 UTC, without Amazon's networks. Lifespans also exclude the June evening when our checker recorded about 128,000 entries dead at once.
Counting 42 busy German addresses, whose entries mostly answered once, the retired share falls to 73.5 percent.
Hetzner alone held 27 of the 79 live entries, on 14 addresses. By city, Frankfurt held 34 of the live entries, Falkenstein 18 and Nuremberg 12.
02
Four Amazon addresses behind a quarter of the list
Our test read 357 German entries from the public list API at 01:17 UTC on September. 28 Each one was tested through itself. An echo service reported the exit, and Cloudflare and Google had to open, with 30 seconds each.
| Tested at 01:17 UTC, September 28, 2026 | On 4 Amazon addresses | On 199 other addresses |
|---|---|---|
| Entries on the list | 91 | 266 |
| Passed their latest check | 0 | 115 |
| Did not accept a connection | 38 | 85 |
| Completed at least one request | 0 | 113 |
| Relayed our echo with a visible exit | 0 | 90 |
| Exited in Germany from the listed address | 0 | 50 |
| Opened Google | 0 | 72 |
| Failed a certificate check | 34 | 3 |
Our tests went out from a single machine of ours in the United States. Exit countries are the ip-api.com echo's, and Google means its connectivity check at www.google.com/generate_204, fetched through each entry.
The Amazon entries sit on the list because they passed some of our routine checks within two days. At 01:23 UTC we probed 20 of them, and five finished the encrypted handshake. Each carried a certificate made out to www.cloudflare.com. Their issuers were named IEC61850-Server, DeltaV and SIMATIC WinCC, and our server trusted none.
Asked for a plain page, all 20 answered under 19 different server names, each saying: Could not connect. We cannot tell who runs these four servers, but they behave more like a honeypot than a proxy. NIST defines a honeypot as a system designed to be attractive to intruders.
03
Where a free German proxy really exits
Of the 90 entries that relayed our echo, 50 left from the listed address inside Germany. Seven more left from other German addresses, and the other 33 exited in 13 other countries.
For nine entries our list places in Frankfurt, the echo placed the same address in Istanbul. Fifteen entries on Hetzner addresses passed our request on to other networks, 13 of them abroad.
Three of the 90 sent our request into the Tor network, by the Tor Project's own check. A site then sees the address of a Tor exit relay, and those addresses are public by design.
Asked through the working entries, Cloudflare answered 50 from Frankfurt and Düsseldorf and 4 from Berlin. It answered the other 22 from 19 cities abroad, as far away as Sydney and Vancouver.
04
Two free German proxies that read encrypted traffic
One live entry on a Hetzner address relayed our echo from its listed address in Germany. Asked to open Cloudflare, it showed its own certificate for the site instead of Cloudflare's.
Its issuer named SslBump, which the Squid project describes as decryption and encryption in the middle. The Squid project also warns that decrypting HTTPS tunnels without consent may be illegal in your jurisdiction.
A live Alibaba entry did the same, with a Cloudflare certificate valid for just two hours. The issuer borrowed a GlobalSign name, and GlobalSign's real key for that name refused it.
05
How to use a free German proxy
Note a row's address, port and protocol before you set it in your browser or tool. Skip the rows on Amazon addresses, since none of them carried traffic in our test.
Open a what-is-my-IP page through the entry and read the country before you do anything that matters. Just over half of the German entries that relayed our echo left from the listed address in Germany.
Check each row's anonymity grade too: 18 of the 79 live German entries were graded transparent. Such an entry hands the site your real address, for example in a header named X-Forwarded-For.
If your browser warns that a connection is not private, stop and choose another entry. Through a free SOCKS5 entry, your data travels exactly as you send it. The SOCKS5 standard, RFC 1928, only adds protection when the chosen method provides it. Free entries pick the no-authentication method, and that one provides none.
Rotate between several entries instead of trusting any single address to stay up. One German entry in four that died was gone within 12 hours.
Questions
Frequently asked.
Yes, they cost nothing and need no account. Other people use the same entries, so try one right before you need it.
A quarter of them are not working proxies. On September 28, 2026, four Amazon addresses carried 91 of the 357 entries and relayed nothing.
From our server in the United States, live German entries needed 5.6 seconds at the median. The rest of the pool, busy addresses aside, took 6.4 seconds by the same measure.
Frankfurt, yes: on September 27, 2026, 34 of the 79 live German entries sat there. Berlin had none among the live entries at that minute.
Most do, but not all. On September 28, 2026, 57 of 90 relaying entries exited in Germany, 50 from the listed address. The other 33 exited in 13 other countries.
Not for secrets: an entry's operator can see anything you send without encryption. In our test, two live German entries swapped in their own certificates for Cloudflare. Keep logins and card payments away from free proxies.
Not long: a German entry that answered and then died lasted about 3 days at the median. A third died within a day, against a quarter for the rest of our pool. Neither figure counts busy addresses, Amazon's networks or the June evening our checker failed.
For work that has to keep running, HProxy sells German residential, ISP, mobile and datacenter proxies. You can pick a German city on residential plans, 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.