Skip to contentUpdated
Germany: free HTTPS proxies 🇩🇪
Germany HTTPS: 3 public proxies marked working in this snapshot. The table also includes check history; recheck before use.
showing 61–120 of 139 (working first, then history)
3Entries marked working
31%Mean check success
5126 msMedian recorded latency
0%Elite-labelled share
Rows marked “not working” are excluded from the working count. History retains recorded entries; a last-response time is shown when known.
| 8080 | HTTPS | 🇩🇪Frankfurt am Main | Elite | ✓ | 4 ms | 43% | not working last alive | |
| 2222 | HTTPS | 🇩🇪Falkenstein | Elite | ✓ | 15 ms | 42% | not working last alive | |
| 3128 | HTTPS | 🇩🇪Frankfurt am Main | Transparent | ✓ | 3 ms | 42% | not working last alive | |
| 3128 | HTTPS | 🇩🇪Frankfurt am Main | Transparent | ✓ | 4 ms | 42% | not working last alive | |
| 8081 | HTTPS | 🇩🇪Nuremberg | Elite | ✓ | 1875 ms | 42% | not working last alive | |
| 443 | HTTPS | 🇩🇪Frankfurt am Main | Transparent | ✓ | 5 ms | 41% | not working last alive | |
| 443 | HTTPS | 🇩🇪Frankfurt am Main | Elite | ✓ | 13 ms | 40% | not working last alive | |
| 3128 | HTTPS | 🇩🇪Frankfurt am Main | Elite | ✓ | 3 ms | 40% | not working last alive | |
| 8080 | HTTPS | 🇩🇪Frankfurt am Main | Transparent | ✓ | 9 ms | 40% | not working last alive | |
| 8080 | HTTPS | 🇩🇪Cochem | Transparent | ✓ | 11 ms | 39% | not working last alive | |
| 1010 | HTTPS | 🇩🇪Frankfurt am Main | Elite | ✓ | 13 ms | 39% | not working last alive | |
| 3128 | HTTPS | 🇩🇪Frankfurt am Main | Elite | ✓ | 9 ms | 38% | not working last alive | |
| 3128 | HTTPS | 🇩🇪Frankfurt am Main | Transparent | ✓ | 8 ms | 38% | not working last alive | |
| 8080 | HTTPS | 🇩🇪Halle | Transparent | ✓ | 31 ms | 38% | 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 | HTTPS | 🇩🇪Frankfurt am Main | Transparent | ✓ | 7 ms | 37% | not working last alive | |
| 3128 | HTTPS | 🇩🇪Saarbrücken | Transparent | ✓ | 6428 ms | 37% | not working last alive | |
| 443 | HTTPS | 🇩🇪Germering | Elite | ✓ | 7 ms | 37% | not working last alive | |
| 3128 | HTTPS | 🇩🇪Frankfurt am Main | Transparent | ✓ | 14 ms | 36% | not working last alive | |
| 3128 | HTTPS | 🇩🇪Frankfurt am Main | Transparent | ✓ | 77 ms | 36% | not working last alive | |
| 8080 | HTTPS | 🇩🇪Halle | Transparent | ✓ | 21 ms | 35% | not working last alive | |
| 3128 | HTTPS | 🇩🇪Frankfurt am Main | Transparent | ✓ | 9 ms | 34% | not working last alive | |
| 3128 | HTTPS | 🇩🇪Frankfurt am Main | Elite | ✓ | 3 ms | 33% | not working last alive | |
| 3128 | HTTPS | 🇩🇪Frankfurt am Main | Transparent | ✓ | 5 ms | 32% | not working last alive | |
| 3128 | HTTPS | 🇩🇪Düsseldorf | Transparent | ✓ | 9 ms | 31% | not working last alive | |
| 3128 | HTTPS | 🇩🇪Limburg an der Lahn | Elite | ✓ | 5849 ms | 29% | not working last alive | |
| 8080 | HTTPS | 🇩🇪Frankfurt am Main | Transparent | ✓ | 8 ms | 28% | not working last alive | |
| 3128 | HTTPS | 🇩🇪Frankfurt am Main | Transparent | ✓ | 6 ms | 28% | not working last alive | |
| 8118 | HTTPS | 🇩🇪Frankfurt am Main | Elite | ✓ | 426 ms | 27% | not working last alive | |
| 3128 | HTTPS | 🇩🇪Frankfurt am Main | Elite | ✓ | 7363 ms | 26% | not working last alive | |
| 8118 | HTTPS | 🇩🇪Frankfurt am Main | Elite | ✓ | 6366 ms | 25% | not working last alive | |
| 3128 | HTTPS | 🇩🇪Frankfurt am Main | Elite | ✓ | 6049 ms | 24% | not working last alive | |
| 80 | HTTPS | 🇩🇪Berlin | Elite | ✓ | 7253 ms | 24% | not working last alive | |
| 80 | HTTPS | 🇩🇪Berlin | Elite | ✓ | 17 ms | 24% | not working last alive | |
| 8118 | HTTPS | 🇩🇪Nuremberg | Elite | ✓ | 540 ms | 23% | not working last alive | |
| 8080 | HTTPS | 🇩🇪Frankfurt am Main | Elite | ✓ | 8757 ms | 23% | not working last alive | |
| 80 | HTTPS | 🇩🇪Nuremberg | Elite | ✓ | 16 ms | 23% | not working last alive | |
| 2080 | HTTPS | 🇩🇪Frankfurt am Main | Elite | ✓ | 9 ms | 22% | not working last alive | |
| 3128 | HTTPS | 🇩🇪Nortorf | Elite | ✓ | 18 ms | 21% | not working last alive | |
| 8080 | HTTPS | 🇩🇪Saarbrücken | Transparent | ✓ | 4166 ms | 21% | not working last alive | |
| 3128 | HTTPS | 🇩🇪Falkenstein | Elite | ✓ | 185 ms | 21% | not working last alive | |
| 3128 | HTTPS | 🇩🇪Falkenstein | Transparent | ✓ | 9 ms | 20% | not working last alive | |
| 8080 | HTTPS | 🇩🇪Frankfurt am Main | Transparent | ✓ | 7 ms | 18% | not working last alive | |
| 3128 | HTTPS | 🇩🇪Meshkīn Dasht | Transparent | ✓ | 87 ms | 18% | not working last alive | |
| 8118 | HTTPS | 🇩🇪Frankfurt am Main | Elite | ✓ | 208 ms | 18% | not working last alive | |
| 10012 | HTTPS | 🇩🇪Limburg an der Lahn | Elite | ✓ | 7 ms | 17% | not working last alive | |
| 8888 | HTTPS | 🇩🇪Nuremberg | Elite | ✓ | 356 ms | 17% | not working last alive | |
| 3128 | HTTPS | 🇩🇪Frankfurt am Main | Transparent | ✓ | 8545 ms | 16% | not working last alive | |
| 3128 | HTTPS | 🇩🇪Frankfurt am Main | Transparent | ✓ | 4 ms | 16% | not working last alive | |
| 11000 | HTTPS | 🇩🇪Falkenstein | Elite | ✓ | 11 ms | 15% | not working last alive | |
| 10011 | HTTPS | 🇩🇪Limburg an der Lahn | Elite | ✓ | 7928 ms | 14% | not working last alive | |
| 3128 | HTTPS | 🇩🇪Frankfurt am Main | Transparent | ✓ | 3 ms | 14% | not working last alive | |
| 10808 | HTTPS | 🇩🇪Düsseldorf | Elite | ✓ | 6772 ms | 14% | not working last alive | |
| 8888 | HTTPS | 🇩🇪Lauterbourg | Transparent | ✓ | 8824 ms | 13% | not working last alive | |
| 8080 | HTTPS | 🇩🇪Nuremberg | Elite | ✓ | 2389 ms | 13% | not working last alive | |
| 8080 | HTTPS | 🇩🇪Frankfurt am Main | Transparent | ✓ | 7168 ms | 10% | not working last alive | |
| 8080 | HTTPS | 🇩🇪Saarbrücken | Transparent | ✓ | 2439 ms | 9% | not working last alive | |
| 8080 | HTTPS | 🇩🇪Halle | Transparent | ✓ | 34 ms | 9% | not working last alive | |
| 443 | HTTPS | 🇩🇪Essen | Transparent | ✓ | 1239 ms | 9% | not working last alive | |
| 8888 | HTTPS | 🇩🇪Frankfurt am Main | Elite | ✓ | 238 ms | 9% | not working last alive | |
| 3128 | HTTPS | 🇩🇪Falkenstein | Transparent | ✓ | 5892 ms | 8% | not working last alive | |
Public proxy reminder
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.
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
- HTTPS
- SOCKS5 & HTTP proxies
- HTTPS proxies online
- free HTTPS proxy
- HTTPS ip address
- anonymous proxies
- free proxy list
- socks5 proxy with crypto payment
- dedicated ip for windows
- what is a SOCKS5 proxy
Real search phrases this page answers — the linked ones open the page that covers them in depth.