HProxy · Free India pool
Free India proxy list 2026
Public proxies our checker places in India, with uptime, speed and network for every row. Nearly every relay in our two tests exited in India.
Every slice of the pool
The same live list, one thing at a time.
A page per country, protocol, anonymity grade, operator, port, network and block, each with its own count, download and API call.
Free proxies by country
24 pages
India proxies right now, by the numbers
The pool currently holds 500 India proxies spread across 103 different networks. They respond in 2959ms at the median, quicker than the 3451ms median across the whole free pool. The busiest exits are Hyderabad, Mumbai, Bengaluru. These figures come straight from the live pool and move every few minutes as proxies are re-verified.
By anonymity
About
What our tests show about the Indian list
These are public proxies gathered from across the web and re-verified continuously by HProxy's engine. They are free, and they are fine for quick, low-stakes tasks. Like all public proxies they are shared and they go down without warning. Most of them are already blocked by the big sites. Always test one before you rely on it.
Verify before you use
Run any list through the Proxy Checker, in the free app or online, and see which proxies are alive, fast and anonymous right now.
The long read
About free Indian proxies.
These rows are free proxies our checker placed in India and heard from in the last two days. When one works, the exit is almost always in India.
The 15:25 UTC pool query on 27 September 2026 found 853 Indian entries in rotation, 120 alive. Our checker had tested 484 of the 853 in the half hour before. Open a row and it shows when our checker last reached it.
At 00:38 UTC on 28 September, we tested all 146 entries live at that minute. Our server in the United States sent a plain web request through each, and 79 took no connection. 29 relayed the request: 28 came out in India, 20 from the listed address, and one in Germany.
Most live Indian entries sit on Indian internet providers rather than cloud servers. On 27 September our list flagged 21 of the 120 as datacenter. That is near the share on ordinary addresses elsewhere. The other 99 are spread over 63 networks, mostly Indian internet providers. Swibi Airnet in Tamil Nadu and Juweriyah Networks in Mumbai hold 5 each.
Indian entries are less steady than the rest, and more of them stop early. On 28 September at 14:31 UTC, the middle live Indian entry had passed 25.0 percent of its checks. The pool's other ordinary addresses reached 34.4. At 17:17 UTC, entries that had worked and then stopped showed a median of 7.1 days, against 9.8. Addresses with 20 or more such entries sit outside both lifespans, and so do Amazon's networks.
A free proxy adds no protection of its own to what you send through it. RFC 1928, the SOCKS5 standard, leaves encryption to whichever method the two sides agree on. A free SOCKS5 entry picks the method with no authentication, and that method encrypts nothing. For steady work from an Indian address, paid India proxies are the better fit.
01
India against the rest of the free pool
Our 14:31 UTC query on 28 September put 123 live Indian entries against 4,145 elsewhere.
| Measured 28 September 2026 | India | Rest of the pool |
|---|---|---|
| Live entries measured | 123 | 4,145 |
| Median success rate across its own checks | 25.0% | 34.4% |
| Passed ten checks at 90 percent | 4.1% | 8.8% |
| Median latency from our server in the United States | 6,240 ms | 6,360 ms |
| Flagged as datacenter by our list | 18.7% | 20.8% |
No Indian address held 20 live entries, and the rest column skips every address that did.
Against ordinary addresses elsewhere, Indian entries match on speed and datacenter share but pass fewer checks. The latency line is measured from the United States, so yours will differ.
02
How long an Indian free proxy lasts
Most free entries never work at all, and India is no exception. Just 682 of the 5,529 Indian entries our engine retired from ordinary addresses ever answered a check. The other 4,847, 87.7 percent, never did, about the pool's 88.6.
With busy addresses counted, 3,764 answered at least once, and 3,128 of them sat on 114 Amazon addresses. Some addresses carry many ports, and each port counts as its own entry. A lifespan counts only addresses with fewer than 20 such entries, in India and the rest alike. In India, that left out 3,081 entries on 26 addresses.
Amazon entries, which relayed nothing in our test, are left out too, as is one June evening. The 530 counted did not last as long as the rest of the pool. We count from the day we first saw an entry until it stopped answering.
| Measured 28 September 2026 | India | Rest of the pool |
|---|---|---|
| Worked, then stopped | 3,764 | 294,139 |
| Left out: on addresses with 20 or more | 3,081 | 258,571 |
| Left out: the evening of 14 June | 108 | 9,084 |
| Left out: other entries on Amazon's networks | 45 | 1,021 |
| Counted | 530 | 25,463 |
| Median lifespan of those counted | 7.1 days | 9.8 days |
| Of those counted, stopped within a day | 27.5% | 24.6% |
| Of those counted, lasted more than thirty days | 32.6% | 30.9% |
Read at 17:17 UTC on 28 September, without addresses holding 20 or more entries that worked and stopped. It also leaves out Amazon's networks, and 14 June after 19:00 UTC. That evening a checker fault marked about 128,000 entries dead.
India loses more entries early: a quarter stopped within 21 hours, against 25 hours for the rest. The long end is about the same, as the last row shows.
03
What an Indian free proxy can reach
We asked every live entry for a plain web page that echoes the address it sees. We also asked each one to open Google over an encrypted connection.
| Measured 28 September 2026 | Entries |
|---|---|
| Tested | 146 |
| Did not accept a connection | 79 |
| Relayed the plain web request | 29 |
| Of those, exiting in India | 28 |
| Of those, leaving from the listed address | 20 |
| Opened Google over an encrypted connection | 18 |
| Certificate did not verify | 0 |
Our live test ran at 00:38 UTC on 28 September 2026, through one server in the United States. Exit countries from ip-api.com's geolocation.
The plain request took a median 3,058 ms through the 29 entries that relayed it. None of the 146 live entries presented a certificate that failed to verify. The busy Amazon entries described below were not alive at 00:38 UTC, so this test left them out.
The one exit abroad was a SOCKS5 entry on a Mumbai server, which came out in Germany.
04
About a quarter of the list is not a proxy
The table shows every entry that answered our checker in the last 48 hours. At 00:39 UTC on 28 September 2026, that was 694 entries.
173 of them sat on just 6 Amazon addresses in Hyderabad and Mumbai, 23 to 32 ports each. They were the same six addresses we found on 27 September, which then carried 234 entries. We tested every entry on the list from our server in the United States. None of the 173 relayed a request. 79 answered a request for www.cloudflare.com with a certificate that did not verify.
A closer look at 18 of them on 27 September found every certificate made out to www.cloudflare.com. They named issuers such as Amazon, an FTP server and one called localhost CA. Cloudflare's real certificate, which we read directly, comes from Google Trust Services. One named Let's Encrypt, and the real Let's Encrypt key had not signed it.
Asked for a plain page, they answered "Could not connect" under 14 different server names. That is how a decoy behaves, not a proxy. Skip these entries, and never send anything through an entry whose certificate does not verify.
| Measured 28 September 2026 | On 6 busy Amazon addresses | Every other entry |
|---|---|---|
| Entries | 173 | 521 |
| Relayed a plain web request | 0 | 79 |
| Of those, exiting in India | 0 | 78 |
| Certificate did not verify | 79 | 1 |
| Opened Google over an encrypted connection | 0 | 59 |
Each of the 694 entries went through our test at 00:39 UTC on 28 September 2026. Requests left our server in the United States. Certificates were examined on 27 September at 17:42 and 17:44 UTC.
The one list relay outside India left from its own address, which ip-api.com places in Tokyo.
Of the 43 list entries that relayed on 27 September, 17 still relayed seven hours later.
05
Where the live Indian entries sit
On 27 September, DigitalOcean held the most live Indian entries, 12, all on datacenter space. Next came two Indian providers, Swibi Airnet and Juweriyah Networks, with 5 each. Microsoft and CtrlS followed with 4 each, and no other network held more than 3.
By city, Bengaluru and Mumbai held 17 live entries each, Hyderabad 7, and Chennai and Pune 4 each. 31 of the 120 had no city on record, and a city is only a database estimate.
06
How to use a free Indian proxy
Before you set up your tool, write down the row's address, port and protocol. On 27 September, 65 live entries spoke HTTP, 29 HTTPS, 34 SOCKS4 and 4 SOCKS5.
Try the SOCKS rows first. In our live test, 19 of 47 SOCKS entries relayed, against 10 of 99 HTTP and HTTPS entries.
Give an entry a minute in our proxy checker before real work. The checker connects through it and shows status, speed, anonymity, country and network.
Keep several entries in reserve, since no single free address can be trusted to stay up. Free entries take no username or password, so anyone can use the same address at once.
Questions
Frequently asked.
Nearly always, when they work: on 28 September 2026, 29 of 146 live entries relayed a plain request. We sent it from our server in the United States, and 28 came out in India. That is by ip-api.com's geolocation, and 20 left from the listed address.
No: WhatsApp's proxy setting expects a plain relay to WhatsApp's own servers, like the proxy software WhatsApp publishes. WhatsApp says it does not support any intermediary that is an HTTP proxy. So an HTTP or SOCKS address from this list will not connect there.
No, free entries take no login, so strangers can use the same address at the same time. Paid proxies come with a username and password of their own.
A median 7.1 days, counted from our first sighting to the entry's last answer. The rest of our pool comes to 9.8 days on that count. Both medians leave out Amazon's networks, a faulty June evening and addresses with 20 or more. On ordinary addresses, 87.7 percent of the Indian entries set aside never answered, so most never work. Our engine's records, read on 28 September 2026, supply all three.
Not for anything private: a free SOCKS5 entry uses the method with no authentication, which adds no encryption. Whoever runs the server can read anything you send without HTTPS. On 28 September, 80 entries on the list presented certificates that did not verify. Use one for tests, and never for a login.
About as quick as other free entries, and slow for real work. On 28 September live Indian entries took a median 6,240 ms, and ordinary addresses elsewhere 6,360 ms. Both were measured from our server in the United States, so your times will differ. At that reading, no live Indian entry came back within half a second.
Upgrade to the paid network
Need pools that stay clean?
Free IPs are shared and rotate out fast, so success rates swing. The paid network gives you dedicated-clean pools that hold up under load.
Docs and AI
The free list, in your assistant and in your code.
We built the MCP server and the CLI ourselves: the free proxy list is one tool call away in Claude, ChatGPT, Cursor or any assistant that speaks MCP, and the list's API is documented end to end.
Every product has its own reference in the docs. Something the list does not give you? Tell us.
Claude, ChatGPT, Cursor, Gemini, Copilot, Windsurf, Perplexity, Ollama and any assistant that speaks MCP.
MCP server
Built by us and hosted at mcp.hproxy.com: the free proxy list, the checker and the IP lookup as tools in Claude, ChatGPT, Cursor, VS Code or any assistant that speaks MCP. Nothing to install, no key.
CLI
The list from a terminal: hproxy list --country DE --limit 20, from the command line of the free HProxy app.
API docs
The free list's API, documented end to end with real responses: the filters, the formats, the limits.
llms.txt
The whole documentation as markdown for any model that reads: /llms.txt for the index, /llms-full.txt for everything.
Let your assistant pull the list
The pool is a free, keyless API and a documented markdown page. Hand your assistant one of these and it can fetch live proxies on its own, filtered the way you asked.
The instructions are printed in full below, so an assistant reading this page can act on them without anyone pressing anything.
All the machine lanes- MCP server
- Adds proxy_list, proxy_check and ip_lookup as tools your assistant can call by itself. Nothing to install.
claude mcp add --transport http hproxy https://mcp.hproxy.com/mcpClaude, ChatGPT, Cursor, VS Code, Windsurf or any assistant that speaks MCP: add https://mcp.hproxy.com/mcp as a remote server. This page's tool is proxy_list. - Command line
- The same tool without an assistant, from the free HProxy app's command line. Add --json for JSON.
hproxy list --country DE --protocol socks5 --limit 20Comes with the free HProxy app: hproxy.com/proxy-checker - REST, no key
- Plain HTTP with CORS on, which is all an agent with a fetch tool needs.
curl "https://hproxy.com/api/proxy-list?format=json&country=de&limit=20"
Instructions for an assistant, in full
Everything a model needs to call the free proxy list without an account: the endpoint, the parameters, the limits and the honest caveat. Readable straight off the page.
You can use HProxy's free proxy list, which needs no API key and no account.
GET https://hproxy.com/api/proxy-list?format=json returns the live pool as JSON. Useful query parameters: country (ISO alpha-2, e.g. de), protocol (http, https, socks4, socks5), anonymity (elite, anonymous, transparent) and limit. Add format=txt for plain ip:port lines instead.
Each proxy comes back with ip, port, protocols, anonymity, country_code, city, asn_org, latency_ms and uptime_24h. The pool is re-checked around the clock, so ask for it fresh rather than caching it.
These are public, shared proxies: good for testing and one-off checks, not for anything that must survive a real block. Full docs: https://hproxy.com/llms/free-proxy.txt
There is also an MCP server, so an assistant can call this as a tool instead of writing HTTP: add https://mcp.hproxy.com/mcp as a remote MCP server (nothing to install, no key) and use the proxy_list tool. In Claude Code the line is `claude mcp add --transport http hproxy https://mcp.hproxy.com/mcp`. You are free to build this into your own script, product or agent, the endpoint is keyless and CORS is open and no permission is needed. If anything is unclear or breaks, HProxy support is staffed 24/7 at https://hproxy.com/contact.Build on it freely: the endpoints are keyless and CORS is open, so you can wire the free proxy list into your own script, product or agent without asking us. If you get stuck, support answers around the clock, every day, at hproxy.com/contact. Generated markdown doc: hproxy.com/llms/free-proxy.txt.
About this list & IP removal
Every proxy here is aggregated from publicly available sources. We do not scan or collect these IP addresses ourselves: we verify entries that are already public (live status, latency, uptime) and store nothing else about the devices behind them. The list is provided as-is, with no warranty, for lawful use only, on the basis of our legitimate interest in a free, transparent proxy directory (Art. 6 (1) (f) GDPR). Never route passwords or sensitive data through a public proxy. If an IP address is yours and you'd like it removed, email legal@hproxy.com and we'll take it down (Art. 21 GDPR). Full details on the report abuse page.