Skip to contentFrance: free HTTP proxies 🇫🇷
France HTTP: 13 public proxies marked working in this snapshot. The table also includes check history; recheck before use.
showing 1–60 of 70 (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.
| 3128 | HTTP | 🇫🇷Gravelines | Transparent | – | 11 ms | 100% | ||
| 80 | HTTP | 🇫🇷Roubaix | Elite | – | 14 ms | 100% | ||
| 80 | HTTP | 🇫🇷Roubaix | Elite | – | 11 ms | 100% | ||
| 80 | HTTP | 🇫🇷Paris | Elite | – | 7 ms | 100% | ||
| 8888 | HTTP | 🇫🇷Lauterbourg | Elite | – | 6 ms | 99% | ||
| 3128 | HTTP | 🇫🇷Gravelines | Transparent | – | 11 ms | 99% | ||
| 80 | HTTP | 🇫🇷Paris | Elite | – | 36 ms | 98% | ||
| 8156 | HTTP | 🇫🇷Paris | Anonymous | – | 9 ms | 96% | ||
| 8080 | HTTP | 🇫🇷Lauterbourg | Elite | – | 40 ms | 94% | ||
| 8080 | HTTP | 🇫🇷Paris | Transparent | – | 76 ms | 84% | ||
| 8888 | HTTP | 🇫🇷Lauterbourg | Elite | – | 725 ms | 43% | ||
| 3128 | HTTP | 🇫🇷Paris | Transparent | – | 6807 ms | 36% | ||
| 8080 | HTTP | 🇫🇷Marseille | Transparent | – | 1087 ms | 17% | ||
| 3128 | HTTP | 🇫🇷Lauterbourg | Transparent | – | 10 ms | 49% | 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 → | ||||||||
| 80 | HTTP | 🇫🇷Paris | Anonymous | – | 9 ms | 49% | not working last alive | |
| 80 | HTTP | 🇫🇷Paris | Elite | – | 9 ms | 49% | not working last alive | |
| 8911 | HTTP | 🇫🇷Roubaix | Elite | – | 15 ms | 49% | not working last alive | |
| 8388 | HTTP | 🇫🇷Lauterbourg | Elite | – | 6 ms | 48% | not working last alive | |
| 9090 | HTTP | 🇫🇷Lauterbourg | Elite | – | 12 ms | 48% | not working last alive | |
| 8080 | HTTP | 🇫🇷Paris | Transparent | – | 4948 ms | 48% | not working last alive | |
| 80 | HTTP | 🇫🇷Strasbourg | Elite | – | 7 ms | 48% | not working last alive | |
| 8118 | HTTP | 🇫🇷Saint-Etienne | Elite | – | 15 ms | 47% | not working last alive | |
| 80 | HTTP | 🇫🇷Paris | Elite | – | 9 ms | 47% | not working last alive | |
| 10111 | HTTP | 🇫🇷Roubaix | Transparent | – | 29 ms | 46% | not working last alive | |
| 5432 | HTTP | 🇫🇷Paris | Elite | – | 99 ms | 45% | not working last alive | |
| 8080 | HTTP | 🇫🇷Paris | Transparent | – | 61 ms | 44% | not working last alive | |
| 8118 | HTTP | 🇫🇷Lauterbourg | Elite | – | 245 ms | 44% | not working last alive | |
| 80 | HTTP | 🇫🇷Lauterbourg | Elite | – | 5 ms | 43% | not working last alive | |
| 8118 | HTTP | 🇫🇷Lyon | Elite | – | 15 ms | 43% | not working last alive | |
| 8080 | HTTP | 🇫🇷Paris | Transparent | – | 1486 ms | 42% | not working last alive | |
| 3128 | HTTP | 🇫🇷Paris | Transparent | – | 6 ms | 42% | not working last alive | |
| 3128 | HTTP | 🇫🇷Gravelines | Transparent | – | 8292 ms | 41% | not working last alive | |
| 80 | HTTP | 🇫🇷Lauterbourg | Elite | – | 7 ms | 40% | not working last alive | |
| 3128 | HTTP | 🇫🇷Lauterbourg | Transparent | – | 8720 ms | 39% | not working last alive | |
| 3128 | HTTP | 🇫🇷Lauterbourg | Transparent | – | 8839 ms | 35% | not working last alive | |
| 6001 | HTTP | 🇫🇷Lauterbourg | Elite | – | 224 ms | 35% | not working last alive | |
| 90 | HTTP | 🇫🇷Roubaix | Elite | – | 15 ms | 34% | not working last alive | |
| 3128 | HTTP | 🇫🇷Lauterbourg | Elite | – | 790 ms | 33% | not working last alive | |
| 3128 | HTTP | 🇫🇷Lauterbourg | Elite | – | 1771 ms | 32% | not working last alive | |
| 3128 | HTTP | 🇫🇷Paris | Transparent | – | 18 ms | 31% | not working last alive | |
| 3128 | HTTP | 🇫🇷Roubaix | Transparent | – | 8806 ms | 31% | not working last alive | |
| 3128 | HTTP | 🇫🇷Paris | Anonymous | – | 8661 ms | 26% | not working last alive | |
| 80 | HTTP | 🇫🇷Roubaix | Elite | – | 15 ms | 24% | not working last alive | |
| 5005 | HTTP | 🇫🇷Lauterbourg | Elite | – | 7487 ms | 22% | not working last alive | |
| 3128 | HTTP | 🇫🇷Lauterbourg | Elite | – | 8417 ms | 21% | not working last alive | |
| 48080 | HTTP | 🇫🇷Strasbourg | Elite | – | 7264 ms | 21% | not working last alive | |
| 3128 | HTTP | 🇫🇷Paris | Elite | – | 9 ms | 19% | not working last alive | |
| 40001 | HTTP | 🇫🇷Lauterbourg | Elite | – | 4437 ms | 17% | not working last alive | |
| 40002 | HTTP | 🇫🇷Lauterbourg | Elite | – | 8487 ms | 17% | not working last alive | |
| 30005 | HTTP | 🇫🇷Roubaix | Elite | – | 8464 ms | 17% | not working last alive | |
| 80 | HTTP | 🇫🇷Lauterbourg | Elite | – | 1190 ms | 15% | not working last alive | |
| 3128 | HTTP | 🇫🇷Lauterbourg | Transparent | – | 7881 ms | 14% | not working last alive | |
| 3128 | HTTP | 🇫🇷Lauterbourg | Transparent | – | 8842 ms | 13% | not working last alive | |
| 3128 | HTTP | 🇫🇷Lauterbourg | Transparent | – | 7514 ms | 13% | not working last alive | |
| 3128 | HTTP | 🇫🇷Lauterbourg | Transparent | – | 4074 ms | 12% | not working last alive | |
| 3128 | HTTP | 🇫🇷Lauterbourg | Transparent | – | 5817 ms | 11% | not working last alive | |
| 3128 | HTTP | 🇫🇷Lauterbourg | Elite | – | 3073 ms | 10% | not working last alive | |
| 80 | HTTP | 🇫🇷Roubaix | Elite | – | 109 ms | 9% | not working last alive | |
| 3128 | HTTP | 🇫🇷Ermenonville | Transparent | – | 8876 ms | 9% | not working last alive | |
| 3128 | HTTP | 🇫🇷Paris | Transparent | – | 7096 ms | 9% | 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 82%; mean recorded response time, where available, is 680 ms. By protocol: HTTP (13). By anonymity level: Elite (7), Anonymous (1), Transparent (5). The most common ports are 80, 8080, 3128. Measurements come from recorded checks, not a promise of availability. Use ⟳ to recheck before use.
This slice groups public proxy records for France / 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 proxy list
- free HTTP proxy
- free proxies HTTP
- HTTP proxies online
- proxy list
- socks5 proxies
- SOCKS5 & HTTP proxies
- dedicated ip
- what is a SOCKS5 proxy
- free proxy list
- elite proxies
- socks5 proxy
- working elite proxies
- elite proxies tutorial
Real search phrases this page answers — the linked ones open the page that covers them in depth.