| # | Proxy (IP:Port) | Protocol | HTTPS | Country | Anonymity | Latency | Uptime (7d) | Last checked |
|---|---|---|---|---|---|---|---|---|
| 1 | 115.127.31.66:8080 | http | — | Bangladesh / Dhaka | elite | 892 ms | 96.63% | 55m ago |
| 2 | 103.149.75.82:1080 | socks4 | ✓ TLS | Bangladesh / Dhaka | elite | 2041 ms | 89.38% | 9m ago |
| 3 | 103.175.127.230:60606 | socks4 | ✓ TLS | Bangladesh / Madaripur | elite | 8958 ms | 71.13% | 1h ago |
| 4 | 103.155.42.38:1080 | socks4 | ✓ TLS | Bangladesh / Chauddagram | elite | 8822 ms | 63.33% | 51m ago |
| 5 | 103.189.218.76:6969 | socks5 | ✓ TLS | Bangladesh / Paltan | elite | 2720 ms | 48.89% | 26m ago |
| 6 | 103.137.158.112:83 | http | ✓ TLS | Bangladesh / Dhaka | elite | 9651 ms | 28.17% | 16m ago |
| 7 | 103.170.185.162:46 | http | ✓ TLS | Bangladesh / Tongi | elite | 9117 ms | 42.5% | 28m ago |
| 8 | 182.48.66.154:8080 | http | ✓ TLS | Bangladesh / Dhaka | elite | 3132 ms | 35.33% | 11m ago |
| 9 | 103.85.183.30:4995 | http | ✓ TLS | Bangladesh / Maulavi Bāzār | elite | 9694 ms | 22.92% | 1m ago |
| 10 | 182.160.127.29:12331 | http | ✓ TLS | Bangladesh / Dhaka | elite | 7850 ms | 24.66% | 11m ago |
| 11 | 103.115.255.225:36331 | socks4 | ✓ TLS | Bangladesh / Savar Upazila | elite | 5076 ms | 55.23% | 28m ago |
| 12 | 163.47.37.190:1080 | socks5 | — | Bangladesh / Paltan | elite | 4330 ms | 54.69% | 19m ago |
| 13 | 103.245.96.161:3214 | http | ✓ TLS | Bangladesh / Dhaka | elite | 10133 ms | 36.27% | 10h ago |
| 14 | 103.72.137.209:8080 | http | ✓ TLS | Bangladesh / Dhaka | elite | 8624 ms | 39.19% | 5h ago |
| 15 | 103.117.108.56:8080 | http | ✓ TLS | Bangladesh / Narayanganj | elite | 2711 ms | 21.05% | 10h ago |
| 16 | 103.141.70.48:8080 | http | ✓ TLS | Bangladesh / Bhatara | elite | 7991 ms | 15.15% | 11h ago |
| 17 | 27.131.14.9:1088 | socks5 | — | Bangladesh / Dhaka | elite | 3446 ms | 45.45% | 4h ago |
| 18 | 119.148.7.10:22122 | socks5 | ✓ TLS | Bangladesh / Dhaka | elite | 2813 ms | 64.47% | 3h ago |
| 19 | 103.151.75.21:2025 | socks5 | ✓ TLS | Bangladesh / Burirchar | elite | 1950 ms | 22.22% | 20h ago |
| 20 | 103.157.135.199:443 | http | ✓ TLS | Bangladesh / Jessore | elite | 7496 ms | 6.25% | 13h ago |
| 21 | 114.31.15.190:2024 | http | ✓ TLS | Bangladesh / Dhaka | elite | 10776 ms | 26.09% | 1h ago |
| 22 | 103.140.25.230:8080 | http | ✓ TLS | Bangladesh / Chittagong | elite | 6698 ms | 16.13% | 5h ago |
| 23 | 115.127.105.163:6699 | http | — | Bangladesh / Dhaka | elite | 8383 ms | 18.18% | 19h ago |
| 24 | 103.119.101.59:8080 | http | ✓ TLS | Bangladesh / Dhaka | elite | 3732 ms | 43% | 20m ago |
| 25 | 43.231.78.205:8080 | http | ✓ TLS | Bangladesh / Dhaka | elite | 9755 ms | 11.11% | 7h ago |
| 26 | 59.152.97.233:1080 | socks5 | — | Bangladesh / Chāndpur | elite | 2272 ms | 40.74% | 11h ago |
| 27 | 103.138.145.102:1999 | socks5 | — | Bangladesh / Kishoreganj Sadar Upazila | elite | 2454 ms | 8.33% | 1h ago |
| 28 | 103.204.211.48:32255 | http | ✓ TLS | Bangladesh / Dhaka | elite | 9261 ms | 40.2% | 1h ago |
| 29 | 103.162.57.42:1080 | socks5 | ✓ TLS | Bangladesh / Cox's Bazar | elite | 5977 ms | 41.94% | 13h ago |
| 30 | 101.2.166.73:1080 | socks5 | — | Bangladesh / Chittagong | elite | 3467 ms | 16.13% | 10h ago |
| 31 | 103.245.110.198:1452 | http | ✓ TLS | Bangladesh / Bhatara | elite | 11466 ms | 32.84% | 11m ago |
| 32 | 119.148.31.170:22122 | socks5 | — | Bangladesh / Dhaka | elite | 5641 ms | 11.54% | 15h ago |
| 33 | 103.6.251.240:8080 | http | ✓ TLS | Bangladesh / Dhaka | elite | 1817 ms | 31.43% | 2h ago |
| 34 | 103.151.74.29:2025 | socks5 | ✓ TLS | Bangladesh / Burirchar | elite | 1861 ms | 18.42% | 21h ago |
| 35 | 202.40.190.74:1080 | socks5 | — | Bangladesh / Dhaka | elite | 4659 ms | 34.25% | 4h ago |
| 36 | 103.134.242.121:8080 | http | ✓ TLS | Bangladesh / Chittagong | elite | 7589 ms | 28.45% | 53m ago |
| 37 | 103.197.48.209:1080 | socks5 | — | Bangladesh / Gafargaon | elite | 5454 ms | 11.11% | 7h ago |
| 38 | 202.84.39.103:8674 | http | ✓ TLS | Bangladesh / Dhaka | elite | 5053 ms | 19.35% | 14h ago |
| 39 | 103.142.69.169:8885 | http | ✓ TLS | Bangladesh / Paltan | elite | 7316 ms | 23.66% | 2h ago |
| 40 | 27.131.14.9:8812 | http | ✓ TLS | Bangladesh / Dhaka | elite | 8881 ms | 27.78% | 11h ago |
| 41 | 202.5.33.33:1101 | http | ✓ TLS | Bangladesh / Chittagong | elite | 8069 ms | 38.41% | 8h ago |
| 42 | 119.148.20.109:22122 | socks5 | ✓ TLS | Bangladesh / Dhaka | elite | 4151 ms | 44.33% | 4m ago |
| 43 | 103.148.217.247:8080 | http | — | Bangladesh / Narayanganj | elite | 9881 ms | 16.67% | 13h ago |
| 44 | 103.118.85.144:1080 | socks5 | — | Bangladesh / Sātkhira | elite | 8468 ms | 23.19% | 37m ago |
| 45 | 103.113.152.73:14158 | http | ✓ TLS | Bangladesh / Dhaka | elite | 11576 ms | 39.41% | 12m ago |
| 46 | 103.118.85.75:6321 | http | ✓ TLS | Bangladesh / Sātkhira | elite | 7127 ms | 26.47% | 20m ago |
| 47 | 202.5.47.60:1080 | http | ✓ TLS | Bangladesh / Chittagong | elite | 5958 ms | 18.33% | 1h ago |
| 48 | 103.254.85.66:8080 | http | ✓ TLS | Bangladesh / Dhaka | elite | 10252 ms | 6.67% | 1h ago |
| 49 | 103.248.206.188:8080 | http | ✓ TLS | Bangladesh / Paltan | elite | 9310 ms | 39.51% | 20m ago |
| 50 | 103.40.156.83:3128 | http | ✓ TLS | Bangladesh / Bhatara | elite | 7168 ms | 6.25% | 4h 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 Bangladesh 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.