在in 印度 🇮🇳中的免费代理
20 免费 in 印度 代理(SOCKS5、HTTP、HTTPS、SOCKS4),具有延迟、正常运行时间和匿名性,持续检查。
showing 1–60 of 175 (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.
| 9100 | SOCKS5 | 🇮🇳Mumbai | Elite | – | 138 ms | 100% | ||
| 83 | HTTP | 🇮🇳Hyderabad | Transparent | – | 154 ms | 100% | ||
| 8080 | HTTPS | 🇮🇳Kalyān | Transparent | ✓ | 147 ms | 100% | ||
| 1080 | SOCKS4 | 🇮🇳Mumbai | Elite | – | 136 ms | 99% | ||
| 8888 | SOCKS5 | 🇮🇳Bengaluru | Elite | – | 136 ms | 99% | ||
| 4145 | SOCKS4 | 🇮🇳Mumbai | Elite | – | 128 ms | 98% | ||
| 8080 | HTTPS | 🇮🇳Phalodi | Transparent | ✓ | 187 ms | 98% | ||
| 1088 | SOCKS5 | 🇮🇳Mumbai | Elite | – | 920 ms | 98% | ||
| 9813 | SOCKS5 | 🇮🇳Kattumannarkoil | Elite | – | 178 ms | 93% | ||
| 8888 | HTTPS | 🇮🇳Bengaluru | Elite | ✓ | 138 ms | 91% | ||
| 1080 | SOCKS5 | 🇮🇳Surat | Elite | – | 8753 ms | 51% | ||
| 8080 | HTTPS | 🇮🇳Mumbai | Elite | ✓ | 826 ms | 45% | ||
| 9053 | SOCKS4 | 🇮🇳Panvel | Elite | – | 6073 ms | 34% | ||
| 3128 | HTTPS | 🇮🇳Kochi | Transparent | ✓ | 5106 ms | 32% | ||
| 需要每 5 分钟不会掉线的代理吗? 获取带有您自己专用IP的私有SOCKS5/HTTP,99.9%的正常运行时间和无日志记录。 查看 s4m 代理 → | ||||||||
| 3128 | HTTP | 🇮🇳Kochi | Transparent | – | 5031 ms | 32% | ||
| 8080 | HTTP | 🇮🇳Galsi | Transparent | – | 8881 ms | 17% | ||
| 6667 | SOCKS5 | 🇮🇳Ankleshwar | Elite | – | 1707 ms | 15% | ||
| 8080 | HTTPS | 🇮🇳Tirunelveli | Transparent | ✓ | 6845 ms | 14% | ||
| 48976 | HTTPS | 🇮🇳Vadodara | Elite | ✓ | 7275 ms | 12% | ||
| 83 | HTTPS | 🇮🇳Hyderabad | Transparent | ✓ | 7450 ms | 5% | ||
| 1080 | SOCKS4 | 🇮🇳Noida | Elite | – | 153 ms | 84% | not working last alive | |
| 4145 | SOCKS4 | 🇮🇳Mumbai | Elite | – | 123 ms | 84% | not working last alive | |
| 1080 | SOCKS4 | 🇮🇳Vikramgad | Elite | – | 130 ms | 80% | not working last alive | |
| 4153 | SOCKS4 | 🇮🇳Hyderabad | Elite | – | 177 ms | 58% | not working last alive | |
| 1080 | SOCKS5 | 🇮🇳Mumbai | Elite | – | 132 ms | 57% | not working last alive | |
| 1080 | SOCKS4 | 🇮🇳Gurugram | Elite | – | 200 ms | 51% | not working last alive | |
| 8080 | HTTP | 🇮🇳Āsandh | Transparent | – | 161 ms | 51% | not working last alive | |
| 1080 | SOCKS5 | 🇮🇳Mumbai | Elite | – | 129 ms | 50% | not working last alive | |
| 8080 | HTTP | 🇮🇳New Delhi | Transparent | – | 162 ms | 50% | not working last alive | |
| 8888 | SOCKS5 | 🇮🇳Bengaluru | Elite | – | 134 ms | 50% | not working last alive | |
| 8080 | HTTPS | 🇮🇳Chennai | Transparent | ✓ | 150 ms | 50% | not working last alive | |
| 58080 | HTTP | 🇮🇳Mumbai | Transparent | – | 124 ms | 49% | not working last alive | |
| 1080 | SOCKS5 | 🇮🇳Mumbai | Elite | – | 130 ms | 49% | not working last alive | |
| 51951 | SOCKS4 | 🇮🇳Mumbai | Elite | – | 122 ms | 49% | not working last alive | |
| 80 | HTTPS | 🇮🇳Navi Mumbai | Transparent | ✓ | 141 ms | 49% | not working last alive | |
| 83 | HTTP | 🇮🇳Jaipur | Transparent | – | 169 ms | 49% | not working last alive | |
| 3080 | HTTP | 🇮🇳Mumbai | Elite | – | 137 ms | 49% | not working last alive | |
| 80 | HTTP | 🇮🇳Hyderabad | Elite | – | 149 ms | 49% | not working last alive | |
| 53281 | HTTP | 🇮🇳Hyderabad | Elite | – | 147 ms | 49% | not working last alive | |
| 8888 | HTTPS | 🇮🇳Bengaluru | Anonymous | ✓ | 157 ms | 49% | not working last alive | |
| 3128 | HTTPS | 🇮🇳Bengaluru | Transparent | ✓ | 141 ms | 49% | not working last alive | |
| 4153 | SOCKS4 | 🇮🇳Hyderabad | Elite | – | 158 ms | 49% | not working last alive | |
| 1080 | SOCKS4 | 🇮🇳Kadaparai | Elite | – | 180 ms | 48% | not working last alive | |
| 5555 | HTTP | 🇮🇳New Delhi | Transparent | – | 209 ms | 47% | not working last alive | |
| 8443 | HTTPS | 🇮🇳Bengaluru | Elite | ✓ | 122 ms | 47% | not working last alive | |
| 8080 | HTTPS | 🇮🇳Mumbai | Transparent | ✓ | 129 ms | 47% | not working last alive | |
| 8080 | HTTPS | 🇮🇳Mumbai | Transparent | ✓ | 165 ms | 47% | not working last alive | |
| 8080 | HTTPS | 🇮🇳Jaipur | Elite | ✓ | 2424 ms | 47% | not working last alive | |
| 80 | HTTPS | 🇮🇳New Delhi | Transparent | ✓ | 177 ms | 46% | not working last alive | |
| 80 | HTTP | 🇮🇳New Delhi | Elite | – | 167 ms | 45% | not working last alive | |
| 3128 | HTTP | 🇮🇳Mumbai | Transparent | – | 116 ms | 44% | not working last alive | |
| 1080 | SOCKS5 | 🇮🇳Kota | Elite | – | 189 ms | 42% | not working last alive | |
| 8080 | HTTP | 🇮🇳Shāhābād | Anonymous | – | 7992 ms | 41% | not working last alive | |
| 1080 | SOCKS5 | 🇮🇳Bengaluru | Elite | – | 1096 ms | 40% | not working last alive | |
| 8080 | HTTP | 🇮🇳Chennai | Transparent | – | 8624 ms | 40% | not working last alive | |
| 8080 | HTTP | 🇮🇳Debra | Transparent | – | 6518 ms | 40% | not working last alive | |
| 8080 | HTTPS | 🇮🇳Gurugram | Transparent | ✓ | 5271 ms | 39% | not working last alive | |
| 8080 | HTTP | 🇮🇳Kalyān | Transparent | – | 4195 ms | 37% | not working last alive | |
| 84 | HTTP | 🇮🇳Dhaka | Anonymous | – | 968 ms | 37% | not working last alive | |
| 8080 | HTTP | 🇮🇳Kurnool | Transparent | – | 8199 ms | 36% | not working last alive | |
这些是公共的、未经验证的第三方代理——请自担风险,切勿通过它们发送敏感流量。有关可靠的私人代理,请参见 s4m Proxy.
一目了然
此快照列出了20个实时代理,平均正常运行时间为61%,典型响应时间约为3010毫秒。 按协议:SOCKS5 (6), HTTP (3), HTTPS (8), SOCKS4 (3)。 按匿名级别:精英 (12), 透明 (8)。 最常用的端口是8080, 8888, 83。 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 代理
- 匿名代理是安全的吗
- 可用的代理
- 精英代理列表
- 如何检查代理匿名性
- 专用 IP 适合初学者
- 免费代理
- 免费代理列表
- http 代理
- 购买 专用 IP
此页面回答的真实搜索短语 — 链接的短语打开详细覆盖它们的页面。