| # | Proxy (IP:Port) | Protocol | HTTPS | Country | Anonymity | Latency | Uptime (7d) | Last checked |
|---|---|---|---|---|---|---|---|---|
| 1 | 95.66.138.21:8880 | http | — | Russia / Vladimir | elite | 397 ms | 98.85% | 4m ago |
| 2 | 109.194.34.246:8082 | http | — | Russia / Tomsk | elite | 551 ms | 90.2% | 1h ago |
| 3 | 37.110.147.13:80 | http | — | Russia / Moscow | elite | 355 ms | 88.62% | 21m ago |
| 4 | 82.148.13.136:80 | http | — | Russia / Moscow | elite | 7882 ms | 63.72% | 1h ago |
| 5 | 185.135.69.34:80 | http | — | Russia / Chistopol' | elite | 160 ms | 89.09% | 42m ago |
| 6 | 91.202.185.69:80 | http | — | Russia / Mamyri | elite | 362 ms | 73.75% | 1h ago |
| 7 | 93.171.157.249:8080 | http | — | Russia / Moscow | elite | 498 ms | 73.08% | 40m ago |
| 8 | 176.106.241.50:80 | http | — | Russia / Mytishchi | elite | 400 ms | 75.91% | 20m ago |
| 9 | 212.46.242.185:1080 | socks4 | ✓ TLS | Russia / Moscow | elite | 487 ms | 47.77% | 5h ago |
| 10 | 213.178.39.170:8080 | http | — | Russia / Tolyatti | elite | 4865 ms | 23.68% | 15h ago |
| 11 | 188.226.89.87:8080 | http | ✓ TLS | Russia / Yekaterinburg | elite | 11261 ms | 29.82% | 15h ago |
| 12 | 85.237.62.189:3629 | socks4 | ✓ TLS | Russia / Penza | elite | 5816 ms | 59.42% | 17m ago |
| 13 | 31.220.163.133:1080 | socks4 | ✓ TLS | Russia / Novokuznetsk | elite | 1489 ms | 12% | 3h ago |
| 14 | 213.27.29.153:51000 | socks5 | — | Russia / Rostov-on-Don | elite | 4756 ms | 39.68% | 5h ago |
| 15 | 188.128.86.74:1080 | socks5 | ✓ TLS | Russia / Ulan-Ude | elite | 2353 ms | 7.14% | 5h ago |
| 16 | 91.226.172.214:1080 | socks5 | — | Russia / Moscow | elite | 1532 ms | 6.25% | 15h ago |
| 17 | 79.174.12.190:80 | http | — | Russia / Moscow | elite | 347 ms | 60.62% | 3h ago |
| 18 | 95.165.97.185:8080 | http | ✓ TLS | Russia / Moscow | elite | 3106 ms | 10.53% | 3h ago |
| 19 | 79.174.63.25:8081 | http | ✓ TLS | Russia / Odintsovo | elite | 5729 ms | 16.67% | 24m ago |
| 20 | 91.122.216.160:8080 | http | ✓ TLS | Russia / Arkhangelsk | elite | 3753 ms | 20.69% | 1h ago |
| 21 | 188.113.174.12:3629 | socks4 | — | Russia / Yuzhno-Sakhalinsk | elite | 4058 ms | 28.09% | 4h ago |
| 22 | 93.90.212.2:4153 | socks4 | ✓ TLS | Russia / Nezhinskiy | elite | 823 ms | 30.33% | 5h ago |
| 23 | 45.133.107.64:81 | http | ✓ TLS | Russia / Tul'skiy | elite | 9594 ms | 18.46% | 7h ago |
| 24 | 176.115.146.232:8080 | http | ✓ TLS | Russia / Nizhniy Novgorod | elite | 5141 ms | 35.45% | 44m ago |
| 25 | 89.237.33.113:51549 | socks4 | ✓ TLS | Russia / Novotroitsk | elite | 5841 ms | 11.11% | 18h ago |
| 26 | 92.62.149.82:8080 | http | ✓ TLS | Russia / Orenburg | elite | 5843 ms | 44.44% | 5h ago |
| 27 | 31.28.4.192:80 | http | — | Russia / Moscow | elite | 9911 ms | 57.99% | 3h ago |
| 28 | 31.10.83.158:8080 | http | — | Russia / Ramenskoye | elite | 473 ms | 82.73% | 43m ago |
| 29 | 93.91.112.247:41258 | http | ✓ TLS | Russia / Tver | elite | 10398 ms | 5.88% | 4h ago |
| 30 | 95.84.164.92:8998 | http | ✓ TLS | Russia / Moscow | elite | 7339 ms | 42.67% | 26m ago |
| 31 | 94.19.196.185:1080 | socks5 | — | Russia / St Petersburg | elite | 6328 ms | 7.14% | 5h ago |
| 32 | 195.91.129.101:1337 | socks5 | ✓ TLS | Russia / Moscow | elite | 527 ms | 33.33% | 38m ago |
| 33 | 31.131.248.51:3129 | http | ✓ TLS | Russia / St Petersburg | elite | 437 ms | 16.67% | 59m ago |
| 34 | 178.140.3.161:5678 | http | — | Russia / Moscow | anonymous | 400 ms | 77.97% | 32s ago |
| 35 | 46.47.197.210:3128 | http | — | Russia / St Petersburg | elite | 275 ms | 62.05% | 36m ago |
| 36 | 82.117.78.58:1080 | socks5 | — | Russia / Tomsk | elite | 2605 ms | 36.59% | 11h ago |
| 37 | 185.35.130.144:54782 | http | ✓ TLS | Russia / Sunzha | elite | 4749 ms | 18.75% | 20m ago |
| 38 | 92.39.129.50:1256 | http | ✓ TLS | Russia / Moscow | elite | 7116 ms | 38.3% | 13h ago |
| 39 | 84.21.166.105:1080 | socks5 | ✓ TLS | Russia / Voronezh | elite | 2332 ms | 8.33% | 3h ago |
| 40 | 91.230.65.202:8080 | http | ✓ TLS | Russia / Moscow | elite | 7606 ms | 40.27% | 15m ago |
| 41 | 88.84.223.156:5650 | http | ✓ TLS | Russia / Noginsk | elite | 9742 ms | 25% | 4h ago |
| 42 | 195.190.107.62:3389 | http | ✓ TLS | Russia / Moscow | elite | 9632 ms | 34.72% | 18m ago |
| 43 | 92.255.190.64:4153 | socks4 | — | Russia / Omsk | elite | 1792 ms | 47.33% | 2h ago |
| 44 | 46.146.220.180:1080 | socks5 | ✓ TLS | Russia / Perm | elite | 6213 ms | 43.55% | 2h ago |
| 45 | 81.162.60.120:8080 | http | ✓ TLS | Russia / Olginskaya | elite | 8939 ms | 48.28% | 53m ago |
| 46 | 217.77.102.18:3128 | http | ✓ TLS | Russia / Samara | elite | 2190 ms | 35.06% | 38m ago |
| 47 | 89.188.242.243:80 | http | — | Russia / Yuzhno-Sakhalinsk | elite | 832 ms | 67.47% | 19m ago |
| 48 | 92.39.69.134:11200 | socks5 | ✓ TLS | Russia / Kirov | elite | 3937 ms | 6.67% | 17h ago |
| 49 | 5.128.120.101:8181 | http | ✓ TLS | Russia / Novosibirsk | elite | 7685 ms | 20.83% | 1h ago |
| 50 | 176.99.134.183:8090 | http | — | Russia / Moscow | elite | 7927 ms | 55.88% | 11m 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 Russia 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.