| # | Proxy (IP:Port) | Protocol | HTTPS | Country | Anonymity | Latency | Uptime (7d) | Last checked |
|---|---|---|---|---|---|---|---|---|
| 1 | 116.202.108.111:3128 | http | — | Germany / Falkenstein | elite | 148 ms | 88.66% | 1h ago |
| 2 | 80.74.54.148:3128 | http | — | Germany / Tönisvorst | elite | 247 ms | 88.07% | 6m ago |
| 3 | 141.98.153.86:80 | http | — | Germany / Karlsruhe | elite | 545 ms | 98.85% | 1h ago |
| 4 | 128.140.113.110:3128 | http | ✓ TLS | Germany / Falkenstein | elite | 2801 ms | 33.33% | 27m ago |
| 5 | 128.140.113.110:8080 | http | ✓ TLS | Germany / Falkenstein | elite | 3119 ms | 31.02% | 28m ago |
| 6 | 78.39.253.49:8080 | http | ✓ TLS | Germany / Frankfurt am Main | elite | 7690 ms | 27.85% | 41m ago |
| 7 | 176.126.70.111:16379 | socks5 | ✓ TLS | Germany / Brandenburg an der Havel | elite | 10883 ms | 29.17% | 3h ago |
| 8 | 56.68.116.64:12719 | http | ✓ TLS | Germany / Brandenburg an der Havel | elite | 3003 ms | 48.99% | 19m ago |
| 9 | 89.168.67.102:3128 | http | — | Germany / Frankfurt am Main | transparent | 8468 ms | 20% | 51m ago |
| 10 | 167.86.79.35:1080 | socks5 | ✓ TLS | Germany / Karlsruhe | elite | 1610 ms | 45.95% | 45m ago |
| 11 | 85.214.107.177:80 | http | — | Germany / Berlin | elite | 8194 ms | 65.84% | 20m ago |
| 12 | 157.230.28.51:1973 | http | ✓ TLS | Germany / Frankfurt am Main | elite | 9373 ms | 16.67% | 21h ago |
| 13 | 193.158.12.140:4153 | socks4 | — | Germany / Berlin | elite | 299 ms | 32.38% | 5h ago |
| 14 | 85.9.87.26:8080 | http | ✓ TLS | Germany / Frankfurt am Main | elite | 9306 ms | 26.09% | 33m ago |
| 15 | 91.26.188.170:8080 | http | ✓ TLS | Germany / Cochem | elite | 2113 ms | 24% | 53m ago |
| 16 | 79.76.121.87:3128 | http | ✓ TLS | Germany / Frankfurt am Main | elite | 241 ms | 6.25% | 1h ago |
| 17 | 93.115.18.235:8118 | http | ✓ TLS | Germany / Brandenburg an der Havel | elite | 6625 ms | 9.52% | 1h ago |
| 18 | 34.124.190.108:8080 | socks5 | — | Germany / Brandenburg an der Havel | elite | 10530 ms | 33.9% | 16h ago |
| 19 | 128.140.113.110:8081 | http | ✓ TLS | Germany / Falkenstein | elite | 2497 ms | 29.38% | 22h ago |
| 20 | 46.203.233.116:3128 | http | ✓ TLS | Germany / Frankfurt am Main | elite | 7069 ms | 15.38% | 32m ago |
| 21 | 13.126.183.60:47712 | http | ✓ TLS | Germany / Haßfurt | elite | 4975 ms | 32.77% | 20m ago |
| 22 | 79.127.30.250:8080 | http | ✓ TLS | Germany / Frankfurt am Main | elite | 6021 ms | 39.04% | 1h ago |
Browse proxies by country
Use public proxies with caution. These are open, third-party servers we did not set up. A working proxy can still log your traffic, inject content, or expose your real IP through DNS, WebRTC, or application headers.
Never send passwords, financial data, or other sensitive traffic through an untrusted proxy. Verify a proxy with our Proxy Tester before relying on it, and only use proxies where you are authorized to do so.
ℹ️ About Germany Proxy List
What is this free proxy list?
This page publishes a live list of public HTTP, HTTPS, SOCKS4, and SOCKS5 proxy servers drawn from our continuously monitored proxy database. Every proxy is re-tested on a short interval by a distributed worker fleet, so the status, latency, anonymity level, and geographic location reflect recent checks rather than a stale dump. Only proxies that are currently alive are listed, and credentialed/private proxies are never published.
The first 50 results load instantly. To reveal the rest (up to 200) a lightweight, invisible human-verification check runs first — this keeps the list useful for people while discouraging automated bulk scraping. There is intentionally no bulk download or public API.
HTTP vs HTTPS vs SOCKS proxies
- HTTP — forwards plain HTTP requests; best for simple web traffic and scraping non-TLS endpoints.
- HTTPS — supports the
CONNECTmethod to tunnel TLS, so it can carry encryptedhttps://traffic. - SOCKS4 — a lower-level TCP tunnel; no authentication of the proxied protocol and no UDP/IPv6.
- SOCKS5 — the most flexible: TCP and UDP, IPv6, and optional auth. Defined in RFC 1928. HTTP semantics are defined in RFC 9110 and the standardized forwarding header in RFC 7239.
The HTTPS column (✓ TLS) marks proxies we verified can tunnel encrypted https:// traffic — confirmed either by a live TLS probe or by the proxy reaching our HTTPS test endpoint. This is independent of the proxy's own scheme: an HTTP-listed proxy can still be HTTPS-capable via CONNECT. Use the HTTPS filter to show only TLS-capable proxies.
Anonymity levels & safety ratings
| Level | Reveals your IP? | Privacy rating | Use |
|---|---|---|---|
| Elite | No — and hides that a proxy is used | Strongest | Best choice for anonymity |
| Anonymous | No, but reveals a proxy is in use | Medium | OK for general use |
| Transparent | Yes — forwards your real IP | None | Caching/testing only, not privacy |
How "reliability" and uptime are measured
The default sort ranks proxies by recent success streak. The Uptime (7d) column is the share of our last week of checks that succeeded for that proxy. Latency is the most recent measured round-trip time. Because public proxies are volatile, a proxy that is up now may be down within hours — re-verify before depending on it.