在in 英国 🇬🇧中的免费代理
3 免费 in 英国 代理(SOCKS5、HTTP、HTTPS、SOCKS4),具有延迟、正常运行时间和匿名性,持续检查。
showing 1–60 of 62 (working first, then history)
Rows marked “not working” are history: they answered a check before, but not the latest one. They are kept for reference and are not counted.
| 1080 | SOCKS5 | 🇬🇧Rugby | Elite | – | 65 ms | 99% | ||
| 3128 | HTTP | 🇬🇧St Louis | Transparent | – | 104 ms | 99% | ||
| 3128 | HTTPS | 🇬🇧London | Transparent | ✓ | 18 ms | 77% | ||
| 10086 | HTTPS | 🇬🇧Amsterdam | Elite | ✓ | 1408 ms | 97% | not working last alive | |
| 10008 | HTTPS | 🇬🇧Amsterdam | Elite | ✓ | 892 ms | 96% | not working last alive | |
| 10101 | HTTPS | 🇬🇧Amsterdam | Elite | ✓ | 2379 ms | 96% | not working last alive | |
| 1080 | SOCKS5 | 🇬🇧London | Elite | – | 283 ms | 94% | not working last alive | |
| 1080 | SOCKS4 | 🇬🇧London | Elite | – | 14 ms | 84% | not working last alive | |
| 8888 | SOCKS4 | 🇬🇧London | Elite | – | 88 ms | 84% | not working last alive | |
| 1080 | SOCKS4 | 🇬🇧Bromley | Elite | – | 5325 ms | 60% | not working last alive | |
| 1080 | SOCKS5 | 🇬🇧City of London | Elite | – | 12 ms | 55% | not working last alive | |
| 3128 | HTTPS | 🇬🇧Bexley | Transparent | ✓ | 21 ms | 52% | not working last alive | |
| 1090 | SOCKS4 | 🇬🇧City of London | Elite | – | 15 ms | 52% | not working last alive | |
| 1080 | SOCKS5 | 🇬🇧London | Elite | – | 41 ms | 52% | not working last alive | |
| 需要每 5 分钟不会掉线的代理吗? 获取带有您自己专用IP的私有SOCKS5/HTTP,99.9%的正常运行时间和无日志记录。 查看 s4m 代理 → | ||||||||
| 8080 | HTTPS | 🇬🇧Birmingham | Elite | ✓ | 22 ms | 51% | not working last alive | |
| 8080 | HTTPS | 🇬🇧London | Transparent | ✓ | 14 ms | 51% | not working last alive | |
| 1080 | SOCKS5 | 🇬🇧London | Elite | – | 4 ms | 50% | not working last alive | |
| 3128 | HTTPS | 🇬🇧Portsmouth | Transparent | ✓ | 18 ms | 50% | not working last alive | |
| 3128 | HTTPS | 🇬🇧City of London | Transparent | ✓ | 18 ms | 50% | not working last alive | |
| 8080 | HTTP | 🇬🇧Reyhanlı | Transparent | – | 76 ms | 50% | not working last alive | |
| 3128 | HTTP | 🇬🇧London | Elite | – | 18 ms | 50% | not working last alive | |
| 8080 | HTTPS | 🇬🇧Birmingham | Elite | ✓ | 60 ms | 50% | not working last alive | |
| 8080 | HTTPS | 🇬🇧Slough | Transparent | ✓ | 21 ms | 50% | not working last alive | |
| 3128 | HTTPS | 🇬🇧Erith | Elite | ✓ | 21 ms | 50% | not working last alive | |
| 8118 | HTTPS | 🇬🇧Purfleet-on-Thames | Elite | ✓ | 74 ms | 50% | not working last alive | |
| 5002 | HTTP | 🇬🇧Reading | Elite | – | 18 ms | 50% | not working last alive | |
| 9050 | SOCKS5 | 🇬🇧Loughborough | Elite | – | 33 ms | 50% | not working last alive | |
| 80 | HTTP | 🇬🇧City of London | Elite | – | 16 ms | 49% | not working last alive | |
| 3128 | HTTPS | 🇬🇧City of London | Elite | ✓ | 19 ms | 49% | not working last alive | |
| 8080 | HTTP | 🇬🇧London | Transparent | – | 183 ms | 49% | not working last alive | |
| 9050 | SOCKS5 | 🇬🇧Stretford | Elite | – | 22 ms | 49% | not working last alive | |
| 8989 | SOCKS4 | 🇬🇧Worcester | Elite | – | 18 ms | 49% | not working last alive | |
| 9150 | SOCKS5 | 🇬🇧Hinckley | Elite | – | 62 ms | 49% | not working last alive | |
| 1080 | SOCKS5 | 🇬🇧Islington | Elite | – | 47 ms | 47% | not working last alive | |
| 80 | HTTP | 🇬🇧Amsterdam | Elite | – | 66 ms | 44% | not working last alive | |
| 8080 | HTTPS | 🇬🇧Birmingham | Elite | ✓ | 231 ms | 42% | not working last alive | |
| 8080 | HTTPS | 🇬🇧London | Transparent | ✓ | 13 ms | 42% | not working last alive | |
| 1080 | SOCKS4 | 🇬🇧Coventry | Elite | – | 285 ms | 36% | not working last alive | |
| 19180 | HTTPS | 🇬🇧London | Elite | ✓ | 437 ms | 36% | not working last alive | |
| 8080 | HTTPS | 🇬🇧Reyhanlı | Transparent | ✓ | 7017 ms | 34% | not working last alive | |
| 1080 | SOCKS5 | 🇬🇧Bromley | Elite | – | 48 ms | 33% | not working last alive | |
| 1080 | SOCKS5 | 🇬🇧Maisach | Elite | – | 4147 ms | 32% | not working last alive | |
| 19100 | SOCKS4 | 🇬🇧London | Elite | – | 15 ms | 32% | not working last alive | |
| 19180 | HTTP | 🇬🇧London | Elite | – | 1197 ms | 32% | not working last alive | |
| 3128 | HTTP | 🇬🇧Frankfurt am Main | Transparent | – | 3 ms | 29% | not working last alive | |
| 999 | HTTP | 🇬🇧Santo Domingo Este | Transparent | – | 3472 ms | 28% | not working last alive | |
| 8080 | HTTP | 🇬🇧Aleppo | Transparent | – | 5359 ms | 22% | not working last alive | |
| 999 | HTTP | 🇬🇧Santo Domingo Este | Transparent | – | 3068 ms | 21% | not working last alive | |
| 6969 | HTTPS | 🇬🇧Singapore | Transparent | ✓ | 3294 ms | 21% | not working last alive | |
| 8080 | HTTPS | 🇬🇧Antakya | Transparent | ✓ | 5270 ms | 20% | not working last alive | |
| 5443 | HTTP | 🇬🇧Maidenhead | Elite | – | 2463 ms | 20% | not working last alive | |
| 8080 | HTTPS | 🇬🇧London | Transparent | ✓ | 14 ms | 20% | not working last alive | |
| 8111 | HTTP | 🇬🇧London | Anonymous | – | 34 ms | 19% | not working last alive | |
| 8080 | HTTP | 🇬🇧Mexborough | Anonymous | – | 6376 ms | 18% | not working last alive | |
| 8080 | HTTPS | 🇬🇧Istanbul | Transparent | ✓ | 1436 ms | 17% | not working last alive | |
| 4145 | SOCKS5 | 🇬🇧London | Elite | – | 191 ms | 14% | not working last alive | |
| 8080 | HTTP | 🇬🇧Mexborough | Anonymous | – | 7081 ms | 13% | not working last alive | |
| 3128 | HTTPS | 🇬🇧Moscow | Elite | ✓ | 42 ms | 12% | not working last alive | |
| 19100 | SOCKS5 | 🇬🇧London | Elite | – | 4898 ms | 11% | not working last alive | |
| 999 | HTTP | 🇬🇧Santo Domingo Este | Transparent | – | 8529 ms | 10% | not working last alive | |
这些是公共的、未经验证的第三方代理——请自担风险,切勿通过它们发送敏感流量。有关可靠的私人代理,请参见 s4m Proxy.
一目了然
此快照列出了3个实时代理,平均正常运行时间为91%,典型响应时间约为62毫秒。 按协议:SOCKS5 (1), HTTP (1), HTTPS (1)。 按匿名级别:精英 (1), 透明 (2)。 最常用的端口是3128, 1080。 Every entry is re-validated around the clock — press ⟳ on any row to confirm it responds right now, then copy the IP:port into your client.
This page lists free public proxies located in in 英国, gathered from open sources and re-checked around the clock for latency, uptime and anonymity level. Pick an elite row for the least IP leakage, copy the IP:port, and point your browser, scraper or tool at it — or hit ⟳ to verify a proxy live before you use it.
免费代理是共享和不稳定的——适合快速测试,但请将其视为一次性使用,绝不要通过它们传输敏感流量。当您需要实际保持在线的端点时,我们的私人 SOCKS5/HTTP 代理和WireGuard VPN是经过认证的,快速且无日志,提供可选的专用 IP。不确定选择哪个?请参见VPN 与代理。
免费代理 — 常见问题
这个免费代理列表检查的频率是多少?
持续进行。我们的验证器每几分钟通过每个代理连接到回声端点,并丢弃失败的代理,因此速度、正常运行时间和“检查”时间反映了最近的现实——而不是过时的数据。
免费公共代理安全吗?
将它们视为一次性使用。它们由未知的第三方运营,可能会很慢、记录您的流量,或随时消失。切勿通过它们发送密码或敏感数据。对于任何真实的需求,请使用经过认证的私人代理或VPN。
我如何使用此列表中的代理?
Copy its IP:port, set it in your browser or tool (for example curl -x http://IP:PORT https://api.ipify.org), and confirm the returned IP is the proxy's, not yours. Pick an “elite” entry to minimise IP leakage, and press ⟳ to check it's alive first.
人们通过搜索找到此页面
- 英国
- 工作代理英国
- SOCKS5 和 HTTP 代理
- 精英代理列表
- 免费代理 英国
- 如何检查代理匿名性
- 免费代理
- 代理列表
- 匿名代理
- 免费代理列表
- 精英代理
- socks5代理 用于抓取
- 可用的代理
- http 代理设置
- 公共代理 解释
- socks5 代理 的工作原理
此页面回答的真实搜索短语 — 链接的短语打开详细覆盖它们的页面。