Updated

Germany: free HTTPS proxies 🇩🇪

Germany HTTPS: 3 public proxies marked working in this snapshot. The table also includes check history; recheck before use.

showing 1–60 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.

3128HTTPS🇩🇪Frankfurt am MainTransparent✓5126 ms47%
3128HTTPS🇩🇪WaldbrunnAnonymous✓6243 ms42%
8080HTTPS🇩🇪SaarbrückenTransparent✓685 ms5%
11111HTTPS🇩🇪Frankfurt am MainElite✓10 ms97%not working last alive
3129HTTPS🇩🇪NurembergElite✓480 ms56%not working last alive
8080HTTPS🇩🇪MünsterElite✓11 ms52%not working last alive
3128HTTPS🇩🇪Frankfurt am MainElite✓7 ms51%not working last alive
3128HTTPS🇩🇪Frankfurt am MainElite✓7 ms50%not working last alive
3128HTTPS🇩🇪Frankfurt am MainTransparent✓8 ms50%not working last alive
3128HTTPS🇩🇪Frankfurt am MainTransparent✓3 ms50%not working last alive
8088HTTPS🇩🇪FalkensteinElite✓11 ms50%not working last alive
3128HTTPS🇩🇪NurembergTransparent✓13 ms50%not working last alive
3128HTTPS🇩🇪FalkensteinElite✓11 ms50%not working last alive
8080HTTPS🇩🇪Frankfurt am MainElite✓4 ms50%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 →
3128HTTPS🇩🇪Frankfurt Am MainTransparent✓11 ms50%not working last alive
8080HTTPS🇩🇪Frankfurt am MainTransparent✓10 ms49%not working last alive
59061HTTPS🇩🇪Frankfurt am MainElite✓25 ms49%not working last alive
3128HTTPS🇩🇪Frankfurt am MainElite✓10 ms49%not working last alive
8881HTTPS🇩🇪Frankfurt am MainElite✓7 ms49%not working last alive
8888HTTPS🇩🇪FalkensteinElite✓12 ms49%not working last alive
3128HTTPS🇩🇪NurembergTransparent✓10 ms49%not working last alive
3128HTTPS🇩🇪Frankfurt am MainTransparent✓8 ms49%not working last alive
3133HTTPS🇩🇪DüsseldorfTransparent✓6 ms49%not working last alive
3129HTTPS🇩🇪FalkensteinElite✓11 ms49%not working last alive
8080HTTPS🇩🇪FalkensteinElite✓11 ms49%not working last alive
8118HTTPS🇩🇪DortmundElite✓20 ms49%not working last alive
3128HTTPS🇩🇪NurembergElite✓15 ms49%not working last alive
3128HTTPS🇩🇪Frankfurt am MainTransparent✓4 ms49%not working last alive
18080HTTPS🇩🇪NurembergElite✓8 ms49%not working last alive
1080HTTPS🇩🇪Frankfurt am MainElite✓7 ms49%not working last alive
6444HTTPS🇩🇪FalkensteinElite✓14 ms49%not working last alive
3128HTTPS🇩🇪FalkensteinElite✓15 ms49%not working last alive
8086HTTPS🇩🇪Frankfurt am MainElite✓3 ms49%not working last alive
8888HTTPS🇩🇪BerlinTransparent✓17 ms49%not working last alive
3128HTTPS🇩🇪Frankfurt am MainElite✓4 ms49%not working last alive
3128HTTPS🇩🇪NurembergElite✓10 ms49%not working last alive
1080HTTPS🇩🇪Frankfurt am MainElite✓4 ms49%not working last alive
3128HTTPS🇩🇪NurembergElite✓16 ms49%not working last alive
9080HTTPS🇩🇪NurembergElite✓14 ms49%not working last alive
3128HTTPS🇩🇪Frankfurt am MainTransparent✓7 ms48%not working last alive
1080HTTPS🇩🇪Frankfurt am MainElite✓15 ms48%not working last alive
8888HTTPS🇩🇪Frankfurt am MainElite✓17 ms48%not working last alive
3128HTTPS🇩🇪Frankfurt am MainElite✓12 ms48%not working last alive
3128HTTPS🇩🇪Frankfurt am MainTransparent✓3 ms48%not working last alive
3128HTTPS🇩🇪Frankfurt am MainTransparent✓12 ms48%not working last alive
3128HTTPS🇩🇪Frankfurt am MainElite✓4 ms48%not working last alive
8881HTTPS🇩🇪FalkensteinElite✓15 ms48%not working last alive
3128HTTPS🇩🇪Frankfurt am MainTransparent✓7303 ms48%not working last alive
2222HTTPS🇩🇪FalkensteinElite✓14 ms48%not working last alive
6666HTTPS🇩🇪Frankfurt am MainAnonymous✓7 ms47%not working last alive
3128HTTPS🇩🇪Frankfurt am MainTransparent✓3 ms47%not working last alive
3128HTTPS🇩🇪Limburg an der LahnTransparent✓7 ms47%not working last alive
3128HTTPS🇩🇪BerlinTransparent✓17 ms46%not working last alive
3128HTTPS🇩🇪Frankfurt am MainTransparent✓3 ms46%not working last alive
8080HTTPS🇩🇪SaarbrückenElite✓13 ms46%not working last alive
3128HTTPS🇩🇪DüsseldorfElite✓10 ms45%not working last alive
3128HTTPS🇩🇪Frankfurt am MainTransparent✓3 ms45%not working last alive
8080HTTPS🇩🇪Frankfurt am MainTransparent✓3 ms45%not working last alive
8080HTTPS🇩🇪Frankfurt am MainTransparent✓6 ms44%not working last alive
3128HTTPS🇩🇪Frankfurt am MainTransparent✓4 ms44%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.

At a glance

This page has 3 entries marked working. Mean recorded check success across these entries is 31%; mean recorded response time, where available, is 4018 ms. By protocol: HTTPS (3). By anonymity level: Anonymous (1), Transparent (2). The most common ports are 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 / HTTPS. 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.

FAQ

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.

Download Verified List ($1.99) →Explore s4m Proxy →

People found this page by searching for

Real search phrases this page answers — the linked ones open the page that covers them in depth.