India: free HTTP proxies 🇮🇳
India HTTP: 23 public proxies marked working in this snapshot. The table also includes check history; recheck before use.
showing 1–60 of 101 (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.
| 83 | HTTP | 🇮🇳Dwarka | Transparent | – | 157 ms | 100% | ||
| 9292 | HTTP | 🇮🇳Navi Mumbai | Elite | – | 130 ms | 100% | ||
| 84 | HTTP | 🇮🇳Hyderabad | Transparent | – | 149 ms | 100% | ||
| 80 | HTTP | 🇮🇳Hyderabad | Elite | – | 144 ms | 99% | ||
| 8080 | HTTP | 🇮🇳Tirupur | Transparent | – | 155 ms | 99% | ||
| 8080 | HTTP | 🇮🇳New Delhi | Transparent | – | 201 ms | 99% | ||
| 8080 | HTTP | 🇮🇳Jūnāgadh | Elite | – | 158 ms | 98% | ||
| 80 | HTTP | 🇮🇳New Delhi | Transparent | – | 195 ms | 98% | ||
| 80 | HTTP | 🇮🇳Varanasi | Transparent | – | 189 ms | 97% | ||
| 5555 | HTTP | 🇮🇳New Delhi | Transparent | – | 173 ms | 96% | ||
| 83 | HTTP | 🇮🇳Hyderabad | Transparent | – | 174 ms | 93% | ||
| 80 | HTTP | 🇮🇳Ghaziabad | Transparent | – | 180 ms | 90% | ||
| 8080 | HTTP | 🇮🇳New Delhi | Transparent | – | 240 ms | 87% | ||
| 80 | HTTP | 🇮🇳Hubballi | Transparent | – | 156 ms | 75% | ||
| Private connection options Compare authenticated SOCKS5/HTTP and optional dedicated IP plans. Check the service terms; availability can vary. See s4m Proxy → | ||||||||
| 8080 | HTTP | 🇮🇳Surat | Transparent | – | 1289 ms | 54% | ||
| 8080 | HTTP | 🇮🇳Chennai | Transparent | – | 4300 ms | 42% | ||
| 80 | HTTP | 🇮🇳Ghaziabad | Transparent | – | 2394 ms | 36% | ||
| 80 | HTTP | 🇮🇳Aurangabad | Transparent | – | 2241 ms | 19% | ||
| 83 | HTTP | 🇮🇳New Delhi | Transparent | – | 8701 ms | 18% | ||
| 80 | HTTP | 🇮🇳New Delhi | Transparent | – | 5714 ms | 16% | ||
| 83 | HTTP | 🇮🇳Vijayapura | Transparent | – | 3196 ms | 15% | ||
| 8080 | HTTP | 🇮🇳Noida | Elite | – | 940 ms | 14% | ||
| 8080 | HTTP | 🇮🇳New Delhi | Transparent | – | 8128 ms | 11% | ||
| 3080 | HTTP | 🇮🇳Mumbai | Elite | – | 135 ms | 49% | not working last alive | |
| 8080 | HTTP | 🇮🇳New Delhi | Transparent | – | 161 ms | 49% | not working last alive | |
| 8080 | HTTP | 🇮🇳Ismāilābād | Transparent | – | 159 ms | 48% | not working last alive | |
| 53281 | HTTP | 🇮🇳Rasapūdipalem | Elite | – | 143 ms | 48% | not working last alive | |
| 3128 | HTTP | 🇮🇳Mumbai | Elite | – | 129 ms | 43% | not working last alive | |
| 8080 | HTTP | 🇮🇳Debra | Transparent | – | 185 ms | 42% | not working last alive | |
| 8080 | HTTP | 🇮🇳Chennai | Transparent | – | 2337 ms | 39% | not working last alive | |
| 8080 | HTTP | 🇮🇳Indore | Transparent | – | 171 ms | 37% | not working last alive | |
| 8080 | HTTP | 🇮🇳Mharal Bk | Transparent | – | 4954 ms | 36% | not working last alive | |
| 3128 | HTTP | 🇮🇳Mumbai | Transparent | – | 8779 ms | 36% | not working last alive | |
| 8080 | HTTP | 🇮🇳Bengaluru | Transparent | – | 1615 ms | 35% | not working last alive | |
| 3128 | HTTP | 🇮🇳Kochi | Transparent | – | 2074 ms | 34% | not working last alive | |
| 80 | HTTP | 🇮🇳New Delhi | Elite | – | 188 ms | 33% | not working last alive | |
| 8080 | HTTP | 🇮🇳Phalodi | Transparent | – | 5234 ms | 30% | not working last alive | |
| 48976 | HTTP | 🇮🇳Anand | Elite | – | 6470 ms | 27% | not working last alive | |
| 82 | HTTP | 🇮🇳Hyderabad | Transparent | – | 143 ms | 26% | not working last alive | |
| 53281 | HTTP | 🇮🇳Gudivāda | Elite | – | 143 ms | 26% | not working last alive | |
| 3129 | HTTP | 🇮🇳Howrah | Transparent | – | 8897 ms | 25% | not working last alive | |
| 80 | HTTP | 🇮🇳Mumbai | Transparent | – | 3389 ms | 24% | not working last alive | |
| 83 | HTTP | 🇮🇳New Delhi | Transparent | – | 147 ms | 22% | not working last alive | |
| 8080 | HTTP | 🇮🇳Mumbai | Elite | – | 924 ms | 22% | not working last alive | |
| 8080 | HTTP | 🇮🇳Gopālasamudram | Transparent | – | 194 ms | 20% | not working last alive | |
| 53281 | HTTP | 🇮🇳Rasapūdipalem | Elite | – | 147 ms | 19% | not working last alive | |
| 1111 | HTTP | 🇮🇳Mumbai | Transparent | – | 1996 ms | 19% | not working last alive | |
| 8080 | HTTP | 🇮🇳Gurugram | Transparent | – | 5613 ms | 19% | not working last alive | |
| 32650 | HTTP | 🇮🇳Jaipur | Transparent | – | 240 ms | 19% | not working last alive | |
| 8080 | HTTP | 🇮🇳Noida | Elite | – | 1175 ms | 18% | not working last alive | |
| 8080 | HTTP | 🇮🇳Mumbai | Elite | – | 727 ms | 18% | not working last alive | |
| 8080 | HTTP | 🇮🇳Mumbai | Elite | – | 757 ms | 18% | not working last alive | |
| 8080 | HTTP | 🇮🇳Bengaluru | Elite | – | 853 ms | 18% | not working last alive | |
| 8080 | HTTP | 🇮🇳Galsi | Transparent | – | 1203 ms | 17% | not working last alive | |
| 32650 | HTTP | 🇮🇳Jaipur | Transparent | – | 187 ms | 17% | not working last alive | |
| 83 | HTTP | 🇮🇳Hyderabad | Transparent | – | 2913 ms | 16% | not working last alive | |
| 58080 | HTTP | 🇮🇳Mumbai | Transparent | – | 1335 ms | 16% | not working last alive | |
| 83 | HTTP | 🇮🇳Hyderabad | Transparent | – | 5558 ms | 15% | not working last alive | |
| 8080 | HTTP | 🇮🇳Sivakasi | Transparent | – | 2847 ms | 15% | not working last alive | |
| 8080 | HTTP | 🇮🇳Shāhābād | Anonymous | – | 4556 ms | 15% | 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 23 entries marked working. Mean recorded check success across these entries is 67%; mean recorded response time, where available, is 1708 ms. By protocol: HTTP (23). By anonymity level: Elite (4), Transparent (19). The most common ports are 80, 8080, 83. Measurements come from recorded checks, not a promise of availability. Use ⟳ to recheck before use.
This slice groups public proxy records for India / 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
- proxy server HTTP
- anonymous proxies HTTP
- SOCKS5 & HTTP proxies
- HTTP proxy list
- working proxies
- buy dedicated ip
- elite proxies without registration
- dedicated ip
- what is a SOCKS5 proxy
- working proxies for windows
- proxy list
- fresh anonymous proxies
- free proxy list
- download public proxies
Real search phrases this page answers — the linked ones open the page that covers them in depth.