India: free HTTPS proxies 🇮🇳
India HTTPS: 5 public proxies marked working in this snapshot. The table also includes check history; recheck before use.
showing 1–60 of 100 (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.
| 80 | HTTPS | 🇮🇳Hubballi | Transparent | ✓ | 4228 ms | 83% | ||
| 8080 | HTTPS | 🇮🇳Chennai | Transparent | ✓ | 3783 ms | 38% | ||
| 8080 | HTTPS | 🇮🇳Galsi | Transparent | ✓ | 1132 ms | 21% | ||
| 83 | HTTPS | 🇮🇳Hyderabad | Transparent | ✓ | 3696 ms | 16% | ||
| 8080 | HTTPS | 🇮🇳Bengaluru | Transparent | ✓ | 3494 ms | 16% | ||
| 80 | HTTPS | 🇮🇳New Delhi | Transparent | ✓ | 4974 ms | 55% | not working last alive | |
| 8080 | HTTPS | 🇮🇳Phalodi | Transparent | ✓ | 173 ms | 50% | not working last alive | |
| 3128 | HTTPS | 🇮🇳Mumbai | Transparent | ✓ | 130 ms | 49% | not working last alive | |
| 80 | HTTPS | 🇮🇳Navi Mumbai | Transparent | ✓ | 147 ms | 49% | not working last alive | |
| 8080 | HTTPS | 🇮🇳Mumbai | Transparent | ✓ | 126 ms | 48% | not working last alive | |
| 80 | HTTPS | 🇮🇳Varanasi | Transparent | ✓ | 184 ms | 48% | not working last alive | |
| 8080 | HTTPS | 🇮🇳Mumbai | Transparent | ✓ | 152 ms | 48% | not working last alive | |
| 8888 | HTTPS | 🇮🇳Bengaluru | Anonymous | ✓ | 152 ms | 48% | not working last alive | |
| 8888 | HTTPS | 🇮🇳Bengaluru | Elite | ✓ | 142 ms | 47% | not working last alive | |
| Private connection options Compare authenticated SOCKS5/HTTP and optional dedicated IP plans. Check the service terms; availability can vary. See s4m Proxy → | ||||||||
| 80 | HTTPS | 🇮🇳Gurugram | Transparent | ✓ | 8890 ms | 47% | not working last alive | |
| 80 | HTTPS | 🇮🇳Mumbai | Anonymous | ✓ | 207 ms | 45% | not working last alive | |
| 8080 | HTTPS | 🇮🇳New Delhi | Transparent | ✓ | 5443 ms | 43% | not working last alive | |
| 8080 | HTTPS | 🇮🇳Tirupur | Transparent | ✓ | 5443 ms | 39% | not working last alive | |
| 9999 | HTTPS | 🇮🇳Mumbai | Elite | ✓ | 128 ms | 39% | not working last alive | |
| 8443 | HTTPS | 🇮🇳Bengaluru | Elite | ✓ | 126 ms | 38% | not working last alive | |
| 3128 | HTTPS | 🇮🇳Bengaluru | Transparent | ✓ | 140 ms | 37% | not working last alive | |
| 3129 | HTTPS | 🇮🇳Howrah | Transparent | ✓ | 154 ms | 37% | not working last alive | |
| 3128 | HTTPS | 🇮🇳Indore | Transparent | ✓ | 148 ms | 37% | not working last alive | |
| 3128 | HTTPS | 🇮🇳Bengaluru | Transparent | ✓ | 143 ms | 36% | not working last alive | |
| 3128 | HTTPS | 🇮🇳Kochi | Transparent | ✓ | 2080 ms | 34% | not working last alive | |
| 8080 | HTTPS | 🇮🇳Mumbai | Elite | ✓ | 780 ms | 33% | not working last alive | |
| 8080 | HTTPS | 🇮🇳Mharal Bk | Transparent | ✓ | 140 ms | 32% | not working last alive | |
| 80 | HTTPS | 🇮🇳Bengaluru | Elite | ✓ | 1039 ms | 32% | not working last alive | |
| 8080 | HTTPS | 🇮🇳Jaipur | Elite | ✓ | 1156 ms | 32% | not working last alive | |
| 8080 | HTTPS | 🇮🇳Phalodi | Transparent | ✓ | 154 ms | 31% | not working last alive | |
| 80 | HTTPS | 🇮🇳Ghaziabad | Transparent | ✓ | 159 ms | 31% | not working last alive | |
| 8080 | HTTPS | 🇮🇳Gurugram | Transparent | ✓ | 197 ms | 30% | not working last alive | |
| 3128 | HTTPS | 🇮🇳Mumbai | Transparent | ✓ | 125 ms | 29% | not working last alive | |
| 80 | HTTPS | 🇮🇳Ghaziabad | Transparent | ✓ | 161 ms | 28% | not working last alive | |
| 8080 | HTTPS | 🇮🇳Chennai | Transparent | ✓ | 5797 ms | 26% | not working last alive | |
| 82 | HTTPS | 🇮🇳New Delhi | Transparent | ✓ | 3194 ms | 25% | not working last alive | |
| 8080 | HTTPS | 🇮🇳Bengaluru | Transparent | ✓ | 151 ms | 24% | not working last alive | |
| 8080 | HTTPS | 🇮🇳Bengaluru | Elite | ✓ | 806 ms | 23% | not working last alive | |
| 8080 | HTTPS | 🇮🇳New Delhi | Transparent | ✓ | 4925 ms | 22% | not working last alive | |
| 8080 | HTTPS | 🇮🇳Noida | Elite | ✓ | 1053 ms | 22% | not working last alive | |
| 8080 | HTTPS | 🇮🇳Phalodi | Transparent | ✓ | 199 ms | 22% | not working last alive | |
| 8080 | HTTPS | 🇮🇳Jūnāgadh | Elite | ✓ | 4564 ms | 21% | not working last alive | |
| 443 | HTTPS | 🇮🇳Mumbai | Elite | ✓ | 134 ms | 21% | not working last alive | |
| 8080 | HTTPS | 🇮🇳Debra | Transparent | ✓ | 4029 ms | 20% | not working last alive | |
| 1256 | HTTPS | 🇮🇳Mumbai | Elite | ✓ | 2330 ms | 19% | not working last alive | |
| 8080 | HTTPS | 🇮🇳Indore | Transparent | ✓ | 2978 ms | 18% | not working last alive | |
| 84 | HTTPS | 🇮🇳Hyderabad | Transparent | ✓ | 3929 ms | 18% | not working last alive | |
| 32650 | HTTPS | 🇮🇳Jaipur | Transparent | ✓ | 148 ms | 18% | not working last alive | |
| 8080 | HTTPS | 🇮🇳Citeureup | Transparent | ✓ | 2906 ms | 17% | not working last alive | |
| 83 | HTTPS | 🇮🇳Tiruchirappalli | Transparent | ✓ | 2810 ms | 15% | not working last alive | |
| 8080 | HTTPS | 🇮🇳Gopālasamudram | Transparent | ✓ | 3572 ms | 13% | not working last alive | |
| 8080 | HTTPS | 🇮🇳Surat | Transparent | ✓ | 170 ms | 13% | not working last alive | |
| 83 | HTTPS | 🇮🇳Rāwatbhāta | Transparent | ✓ | 8669 ms | 12% | not working last alive | |
| 84 | HTTPS | 🇮🇳Hyderabad | Transparent | ✓ | 154 ms | 12% | not working last alive | |
| 58080 | HTTPS | 🇮🇳Mumbai | Transparent | ✓ | 5522 ms | 12% | not working last alive | |
| 1111 | HTTPS | 🇮🇳Mumbai | Transparent | ✓ | 5560 ms | 11% | not working last alive | |
| 8080 | HTTPS | 🇮🇳Chennai | Transparent | ✓ | 2599 ms | 11% | not working last alive | |
| 83 | HTTPS | 🇮🇳New Delhi | Transparent | ✓ | 3708 ms | 10% | not working last alive | |
| 83 | HTTPS | 🇮🇳Hyderabad | Transparent | ✓ | 5074 ms | 10% | not working last alive | |
| 80 | HTTPS | 🇮🇳Mumbai | Transparent | ✓ | 2865 ms | 10% | 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 5 entries marked working. Mean recorded check success across these entries is 34%; mean recorded response time, where available, is 3266 ms. By protocol: HTTPS (5). By anonymity level: Transparent (5). The most common ports are 8080, 80, 83. Measurements come from recorded checks, not a promise of availability. Use ⟳ to recheck before use.
This slice groups public proxy records for India / HTTPS. 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
- HTTPS
- free proxies HTTPS
- HTTPS proxy list
- what is a SOCKS5 proxy
- free proxy list
- elite proxies
- SOCKS5 & HTTP proxies
- download http proxies
- dedicated ip
- free proxies
Real search phrases this page answers — the linked ones open the page that covers them in depth.