Skip to contentGermany: free HTTP proxies 🇩🇪
Germany HTTP: 13 public proxies marked working in this snapshot. The table also includes check history; recheck before use.
showing 1–60 of 84 (working first, then history)
Rows marked “not working” are excluded from the working count. History retains recorded entries; a last-response time is shown when known.
| 8118 | HTTP | 🇩🇪Nuremberg | Elite | – | 14 ms | 100% | ||
| 8118 | HTTP | 🇩🇪Nuremberg | Elite | – | 13 ms | 100% | ||
| 8080 | HTTP | 🇩🇪Saarbrücken | Transparent | – | 6 ms | 100% | ||
| 80 | HTTP | 🇩🇪Karlsruhe | Elite | – | 49 ms | 100% | ||
| 3128 | HTTP | 🇩🇪Sonsbeck | Anonymous | – | 11 ms | 100% | ||
| 10002 | HTTP | 🇩🇪Limburg an der Lahn | Elite | – | 7 ms | 100% | ||
| 80 | HTTP | 🇩🇪Frankfurt Am Main | Elite | – | 10 ms | 100% | ||
| 8118 | HTTP | 🇩🇪Frankfurt am Main | Elite | – | 3 ms | 99% | ||
| 8080 | HTTP | 🇩🇪Berlin | Transparent | – | 23 ms | 93% | ||
| 8080 | HTTP | 🇩🇪Frankfurt am Main | Elite | – | 3 ms | 90% | ||
| 2222 | HTTP | 🇩🇪Falkenstein | Elite | – | 8 ms | 65% | ||
| 3128 | HTTP | 🇩🇪Frankfurt am Main | Transparent | – | 12 ms | 42% | ||
| 3128 | HTTP | 🇩🇪Frankfurt am Main | Transparent | – | 5964 ms | 23% | ||
| 3128 | HTTP | 🇩🇪Falkenstein | Elite | – | 11 ms | 50% | not working last alive | |
| Private connection options Compare authenticated SOCKS5/HTTP and optional dedicated IP plans. Check the service terms; availability can vary. See s4m Proxy → | ||||||||
| 3128 | HTTP | 🇩🇪Waldbrunn | Anonymous | – | 7 ms | 50% | not working last alive | |
| 8080 | HTTP | 🇩🇪Spremberg | Transparent | – | 17 ms | 50% | not working last alive | |
| 80 | HTTP | 🇩🇪Frankfurt am Main | Elite | – | 7 ms | 49% | not working last alive | |
| 1080 | HTTP | 🇩🇪Frankfurt Am Main | Elite | – | 13 ms | 49% | not working last alive | |
| 9999 | HTTP | 🇩🇪Nuremberg | Elite | – | 10 ms | 49% | not working last alive | |
| 80 | HTTP | 🇩🇪Falkenstein | Elite | – | 11 ms | 49% | not working last alive | |
| 8888 | HTTP | 🇩🇪Falkenstein | Anonymous | – | 15 ms | 49% | not working last alive | |
| 80 | HTTP | 🇩🇪Karlsruhe | Elite | – | 85 ms | 49% | not working last alive | |
| 3128 | HTTP | 🇩🇪Frankfurt am Main | Transparent | – | 8 ms | 49% | not working last alive | |
| 8118 | HTTP | 🇩🇪Berlin | Elite | – | 33 ms | 49% | not working last alive | |
| 10007 | HTTP | 🇩🇪Limburg an der Lahn | Elite | – | 7 ms | 48% | not working last alive | |
| 8118 | HTTP | 🇩🇪Frankfurt am Main | Elite | – | 3 ms | 48% | not working last alive | |
| 1082 | HTTP | 🇩🇪Frankfurt am Main | Elite | – | 14 ms | 47% | not working last alive | |
| 8118 | HTTP | 🇩🇪Falkenstein | Elite | – | 11 ms | 47% | not working last alive | |
| 8899 | HTTP | 🇩🇪Frankfurt am Main | Elite | – | 6 ms | 46% | not working last alive | |
| 8118 | HTTP | 🇩🇪Frankfurt am Main | Elite | – | 7 ms | 46% | not working last alive | |
| 8080 | HTTP | 🇩🇪Berlin | Transparent | – | 22 ms | 46% | not working last alive | |
| 8080 | HTTP | 🇩🇪Saarbrücken | Transparent | – | 6 ms | 46% | not working last alive | |
| 10015 | HTTP | 🇩🇪Limburg an der Lahn | Elite | – | 7 ms | 45% | not working last alive | |
| 3128 | HTTP | 🇩🇪Frankfurt am Main | Elite | – | 4 ms | 45% | not working last alive | |
| 3128 | HTTP | 🇩🇪Düsseldorf | Transparent | – | 7358 ms | 45% | not working last alive | |
| 8888 | HTTP | 🇩🇪Berlin | Elite | – | 22 ms | 43% | not working last alive | |
| 80 | HTTP | 🇩🇪Berlin | Elite | – | 16 ms | 41% | not working last alive | |
| 3128 | HTTP | 🇩🇪Frankfurt am Main | Transparent | – | 5481 ms | 41% | not working last alive | |
| 10001 | HTTP | 🇩🇪Limburg an der Lahn | Elite | – | 7 ms | 41% | not working last alive | |
| 8080 | HTTP | 🇩🇪Saarbrücken | Transparent | – | 6 ms | 38% | not working last alive | |
| 80 | HTTP | 🇩🇪Nuremberg | Elite | – | 6 ms | 37% | not working last alive | |
| 8118 | HTTP | 🇩🇪Berlin | Elite | – | 12 ms | 36% | not working last alive | |
| 8118 | HTTP | 🇩🇪Frankfurt am Main | Elite | – | 7 ms | 36% | not working last alive | |
| 8080 | HTTP | 🇩🇪Cochem | Transparent | – | 952 ms | 35% | not working last alive | |
| 3128 | HTTP | 🇩🇪Uslar | Elite | – | 10 ms | 35% | not working last alive | |
| 3128 | HTTP | 🇩🇪Frankfurt am Main | Transparent | – | 3 ms | 35% | not working last alive | |
| 3128 | HTTP | 🇩🇪Frankfurt am Main | Elite | – | 3353 ms | 34% | not working last alive | |
| 8080 | HTTP | 🇩🇪Frankfurt am Main | Elite | – | 9 ms | 34% | not working last alive | |
| 10010 | HTTP | 🇩🇪Limburg an der Lahn | Elite | – | 8284 ms | 29% | not working last alive | |
| 3128 | HTTP | 🇩🇪Frankfurt am Main | Elite | – | 8073 ms | 27% | not working last alive | |
| 443 | HTTP | 🇩🇪Frankfurt am Main | Transparent | – | 8247 ms | 24% | not working last alive | |
| 8080 | HTTP | 🇩🇪Olbernhau | Transparent | – | 18 ms | 24% | not working last alive | |
| 3128 | HTTP | 🇩🇪Nuremberg | Elite | – | 170 ms | 23% | not working last alive | |
| 8080 | HTTP | 🇩🇪Brieselang | Transparent | – | 23 ms | 23% | not working last alive | |
| 3128 | HTTP | 🇩🇪Frankfurt am Main | Transparent | – | 5904 ms | 23% | not working last alive | |
| 3128 | HTTP | 🇩🇪Falkenstein | Elite | – | 331 ms | 22% | not working last alive | |
| 10009 | HTTP | 🇩🇪Limburg an der Lahn | Elite | – | 7315 ms | 20% | not working last alive | |
| 10008 | HTTP | 🇩🇪Limburg an der Lahn | Elite | – | 200 ms | 16% | not working last alive | |
| 8118 | HTTP | 🇩🇪Frankfurt am Main | Elite | – | 225 ms | 16% | not working last alive | |
| 3128 | HTTP | 🇩🇪Berlin | Transparent | – | 7539 ms | 15% | not working last alive | |
These are public, unverified third-party proxies — use at your own risk and never send sensitive traffic through them. For reliable, private proxies see s4m Proxy.
At a glance
This page has 13 entries marked working. Mean recorded check success across these entries is 85%; mean recorded response time, where available, is 471 ms. By protocol: HTTP (13). By anonymity level: Elite (8), Anonymous (1), Transparent (4). The most common ports are 8118, 3128, 8080. Measurements come from recorded checks, not a promise of availability. Use ⟳ to recheck before use.
This slice groups public proxy records for Germany / HTTP. Use the recorded status and timestamps to interpret the table, then recheck before use. Availability and anonymity labels do not certify operator trust or privacy.
For authenticated access, compare private SOCKS5/HTTP, WireGuard VPN and optional dedicated IP plans. Read VPN vs proxy, the privacy policy and service terms. Availability can vary; public proxies remain unverified.
Free proxies — FAQ
How often is this free proxy list checked?
Scheduled checks record reachability and response time. The working mark follows the catalogue's retry policy and can differ from the latest attempt. Failed entries may remain as history. Use the shown timestamps and recheck; a fixed interval or continued availability is not guaranteed.
Are free public proxies safe to use?
Public proxy operators are unverified third parties. Do not send credentials or sensitive traffic through them. An elite label does not certify privacy, encryption or logging policy. A private proxy or VPN also requires a separate assessment of the provider.
How do I use a proxy from this list?
Choose the matching protocol and configure the shown IP:port in your client. For HTTP, curl -x http://IP:PORT https://api.ipify.org checks that request's exit IP. Recheck first; this does not test DNS, WebRTC or provider logging.
Private connection options
Compare authenticated SOCKS5/HTTP and optional dedicated IP plans. Check the service terms; availability can vary.
People found this page by searching for
- HTTP
- HTTP proxies online
- proxy server HTTP
- free proxies HTTP
- HTTP ip address
- SOCKS5 & HTTP proxies
- what is socks5 proxies
- download http proxies
- free proxy list
- socks5 proxies
- is anonymous proxies safe
- socks5 proxies without registration
- fresh free proxies
- public proxies list txt
- what is a SOCKS5 proxy
- http proxies
- how to configure dedicated ip
Real search phrases this page answers — the linked ones open the page that covers them in depth.