| # | Proxy (IP:Port) | Protocol | HTTPS | Country | Anonymity | Latency | Uptime (7d) | Last checked |
|---|---|---|---|---|---|---|---|---|
| 1 | 103.51.223.133:8080 | http | — | India / Siliguri | elite | 880 ms | 100% | 39m ago |
| 2 | 139.59.1.14:8080 | http | — | India / Bengaluru | elite | 601 ms | 100% | 1h ago |
| 3 | 152.67.191.232:6800 | http | ✓ TLS | India / Hyderabad | elite | 8992 ms | 85.12% | 1h ago |
| 4 | 144.24.111.128:1088 | socks5 | ✓ TLS | India / Mumbai | elite | 1502 ms | 98.85% | 1h ago |
| 5 | 45.117.29.137:10888 | socks4 | ✓ TLS | India / Bengaluru | elite | 2269 ms | 60.19% | 5m ago |
| 6 | 103.41.97.225:83 | http | ✓ TLS | India / Ongole | elite | 6710 ms | 44.33% | 2m ago |
| 7 | 150.129.109.14:5678 | socks4 | ✓ TLS | India / Kolkata | elite | 3363 ms | 48.76% | 30m ago |
| 8 | 103.177.235.207:83 | http | ✓ TLS | India / Manipal | elite | 8500 ms | 41.24% | 18h ago |
| 9 | 103.48.68.30:83 | http | ✓ TLS | India / Hyderabad | elite | 7290 ms | 20.69% | 2h ago |
| 10 | 103.157.224.1:5678 | socks4 | ✓ TLS | India / Mumbai | elite | 1085 ms | 13.64% | 7m ago |
| 11 | 103.112.212.57:84 | http | ✓ TLS | India / Ilkal | elite | 9448 ms | 5.88% | 8h ago |
| 12 | 103.48.68.126:83 | http | ✓ TLS | India / Hyderabad | elite | 9350 ms | 43.06% | 6h ago |
| 13 | 103.125.154.1:8080 | http | ✓ TLS | India / Tirupur | elite | 11154 ms | 17.5% | 16h ago |
| 14 | 103.26.110.125:84 | http | ✓ TLS | India / Sivakasi | elite | 3831 ms | 25% | 4h ago |
| 15 | 150.129.170.73:5678 | socks4 | — | India / Nadiād | elite | 1834 ms | 28.92% | 23h ago |
| 16 | 103.217.213.124:32650 | http | ✓ TLS | India / Guntur | elite | 2286 ms | 37.5% | 18h ago |
| 17 | 163.53.204.178:9813 | socks5 | ✓ TLS | India / Āttukkāranpatti | elite | 3588 ms | 44.07% | 33m ago |
| 18 | 203.112.134.74:5678 | socks4 | ✓ TLS | India / Mumbai | elite | 993 ms | 18.18% | 5h ago |
| 19 | 27.116.41.156:8470 | http | ✓ TLS | India / Rourkela | elite | 3729 ms | 11.11% | 18h ago |
| 20 | 103.137.218.113:83 | http | ✓ TLS | India / Bhagalpur | elite | 7290 ms | 29.79% | 25m ago |
| 21 | 103.139.242.117:83 | http | ✓ TLS | India / Pune | elite | 4053 ms | 8.7% | 15h ago |
| 22 | 144.48.49.217:8080 | http | ✓ TLS | India / Kanchipuram | elite | 3152 ms | 43.75% | 2h ago |
| 23 | 103.161.31.249:83 | http | ✓ TLS | India / Hyderabad | elite | 7534 ms | 22.5% | 4h ago |
| 24 | 103.48.68.242:83 | http | ✓ TLS | India / Hyderabad | elite | 5605 ms | 9.68% | 6h ago |
| 25 | 103.48.68.28:83 | http | ✓ TLS | India / Hyderabad | elite | 3539 ms | 16.67% | 55m ago |
| 26 | 103.48.68.106:83 | http | ✓ TLS | India / Hyderabad | elite | 8334 ms | 27.14% | 16h ago |
| 27 | 103.48.71.34:83 | http | ✓ TLS | India / Hyderabad | elite | 4762 ms | 15.38% | 4h ago |
| 28 | 103.48.69.70:83 | http | ✓ TLS | India / Hyderabad | elite | 9680 ms | 18.92% | 10m ago |
| 29 | 103.49.166.193:83 | http | ✓ TLS | India / Pune | elite | 8099 ms | 25.64% | 31m ago |
| 30 | 202.62.75.38:83 | http | ✓ TLS | India / Hyderabad | elite | 7357 ms | 44.44% | 19m ago |
| 31 | 103.112.212.57:82 | http | ✓ TLS | India / Ilkal | elite | 8037 ms | 15% | 3h ago |
| 32 | 27.121.101.221:5678 | socks4 | ✓ TLS | India / Nadiād | elite | 1902 ms | 28.16% | 1h ago |
| 33 | 103.163.244.106:1080 | socks5 | ✓ TLS | India / Panipat | elite | 6419 ms | 38.04% | 2h ago |
| 34 | 103.48.68.82:83 | http | ✓ TLS | India / Hyderabad | elite | 7770 ms | 20.83% | 8m ago |
| 35 | 45.116.114.37:5678 | socks4 | ✓ TLS | India / Salem | elite | 9954 ms | 44.12% | 5h ago |
| 36 | 139.59.59.122:8118 | http | ✓ TLS | India / Bengaluru | elite | 1247 ms | 19.57% | 11h ago |
| 37 | 45.64.11.105:8080 | http | ✓ TLS | India / Noida | elite | 9290 ms | 8.7% | 16h ago |
| 38 | 103.137.85.29:83 | http | ✓ TLS | India / Jaipur | elite | 8902 ms | 27.27% | 19h ago |
| 39 | 103.48.71.70:83 | http | ✓ TLS | India / Hyderabad | elite | 6192 ms | 20.34% | 59m ago |
| 40 | 103.169.53.145:8080 | http | ✓ TLS | India / Aizawl | elite | 8077 ms | 28.57% | 2h ago |
| 41 | 111.125.242.34:1111 | http | ✓ TLS | India / Mumbai | elite | 9799 ms | 11.54% | 22h ago |
| 42 | 183.87.160.62:82 | http | ✓ TLS | India / Mumbai | elite | 5816 ms | 10.34% | 1h ago |
| 43 | 103.224.48.38:31433 | socks4 | ✓ TLS | India / Sonauli | elite | 4177 ms | 40.51% | 1h ago |
| 44 | 119.235.50.246:4153 | socks4 | — | India / Hyderabad | elite | 8040 ms | 33.73% | 4h ago |
| 45 | 45.127.56.194:83 | http | ✓ TLS | India / Hyderabad | elite | 1393 ms | 26.39% | 20h ago |
| 46 | 103.149.194.11:32650 | http | ✓ TLS | India / Bānkoli | elite | 8676 ms | 35.83% | 23m ago |
| 47 | 115.247.115.38:8080 | http | ✓ TLS | India / Indore | elite | 9203 ms | 26.32% | 2h ago |
| 48 | 103.48.70.105:84 | http | ✓ TLS | India / Hyderabad | elite | 5218 ms | 25.71% | 5h ago |
| 49 | 103.137.84.17:83 | http | ✓ TLS | India / Jaipur | elite | 4068 ms | 14.81% | 11h ago |
| 50 | 103.48.183.113:4145 | socks4 | ✓ TLS | India / Chennai | elite | 2323 ms | 58.94% | 6m ago |
A quick automated human-verification check runs before more proxies load. We don't offer bulk download or an API — this list is for manual use.
Browse proxies by country
Use public proxies with caution. These are open, third-party servers we did not set up. A working proxy can still log your traffic, inject content, or expose your real IP through DNS, WebRTC, or application headers.
Never send passwords, financial data, or other sensitive traffic through an untrusted proxy. Verify a proxy with our Proxy Tester before relying on it, and only use proxies where you are authorized to do so.
ℹ️ About India Proxy List
What is this free proxy list?
This page publishes a live list of public HTTP, HTTPS, SOCKS4, and SOCKS5 proxy servers drawn from our continuously monitored proxy database. Every proxy is re-tested on a short interval by a distributed worker fleet, so the status, latency, anonymity level, and geographic location reflect recent checks rather than a stale dump. Only proxies that are currently alive are listed, and credentialed/private proxies are never published.
The first 50 results load instantly. To reveal the rest (up to 200) a lightweight, invisible human-verification check runs first — this keeps the list useful for people while discouraging automated bulk scraping. There is intentionally no bulk download or public API.
HTTP vs HTTPS vs SOCKS proxies
- HTTP — forwards plain HTTP requests; best for simple web traffic and scraping non-TLS endpoints.
- HTTPS — supports the
CONNECTmethod to tunnel TLS, so it can carry encryptedhttps://traffic. - SOCKS4 — a lower-level TCP tunnel; no authentication of the proxied protocol and no UDP/IPv6.
- SOCKS5 — the most flexible: TCP and UDP, IPv6, and optional auth. Defined in RFC 1928. HTTP semantics are defined in RFC 9110 and the standardized forwarding header in RFC 7239.
The HTTPS column (✓ TLS) marks proxies we verified can tunnel encrypted https:// traffic — confirmed either by a live TLS probe or by the proxy reaching our HTTPS test endpoint. This is independent of the proxy's own scheme: an HTTP-listed proxy can still be HTTPS-capable via CONNECT. Use the HTTPS filter to show only TLS-capable proxies.
Anonymity levels & safety ratings
| Level | Reveals your IP? | Privacy rating | Use |
|---|---|---|---|
| Elite | No — and hides that a proxy is used | Strongest | Best choice for anonymity |
| Anonymous | No, but reveals a proxy is in use | Medium | OK for general use |
| Transparent | Yes — forwards your real IP | None | Caching/testing only, not privacy |
How "reliability" and uptime are measured
The default sort ranks proxies by recent success streak. The Uptime (7d) column is the share of our last week of checks that succeeded for that proxy. Latency is the most recent measured round-trip time. Because public proxies are volatile, a proxy that is up now may be down within hours — re-verify before depending on it.