| # | Proxy (IP:Port) | Protocol | HTTPS | Country | Anonymity | Latency | Uptime (7d) | Last checked |
|---|---|---|---|---|---|---|---|---|
| 1 | 120.232.115.170:17981 | http | ✓ TLS | China / Guangzhou | elite | 2967 ms | 100% | 1h ago |
| 2 | 61.158.175.38:9002 | http | — | China / Zhengzhou | elite | 911 ms | 100% | 1h ago |
| 3 | 183.215.23.242:9091 | http | — | China / Qingyuan | elite | 944 ms | 100% | 1h ago |
| 4 | 113.204.79.230:9091 | http | — | China / Jinrongjie | elite | 875 ms | 96.55% | 1h ago |
| 5 | 140.207.114.166:10080 | socks5 | ✓ TLS | China / Jinrongjie | elite | 3888 ms | 96.81% | 50m ago |
| 6 | 153.0.171.163:8085 | http | — | China / Jinrongjie | elite | 979 ms | 98.85% | 1h ago |
| 7 | 27.185.218.213:17981 | http | ✓ TLS | China / Shijiazhuang | elite | 2167 ms | 96.88% | 21m ago |
| 8 | 116.196.150.180:17981 | http | — | China / Hangzhou | elite | 964 ms | 85.12% | 1h ago |
| 9 | 119.188.131.55:17981 | http | ✓ TLS | China / Jinan | elite | 2694 ms | 83.33% | 1h ago |
| 10 | 124.128.149.84:8090 | http | ✓ TLS | China / Beijing | elite | 5066 ms | 56.84% | 1h ago |
| 11 | 120.237.232.172:8060 | http | — | China / Guangzhou | elite | 4045 ms | 56.68% | 7m ago |
| 12 | 58.254.153.146:17981 | http | — | China / Guangzhou | elite | 1912 ms | 25.68% | 3h ago |
| 13 | 218.95.39.5:59999 | socks5 | ✓ TLS | China / Chaowai | elite | 1835 ms | 27.66% | 16h ago |
| 14 | 36.111.33.167:13128 | http | — | China / Hangzhou | elite | 1829 ms | 36.94% | 5h ago |
| 15 | 183.236.232.160:8080 | http | — | China / Guangzhou | elite | 6651 ms | 19.67% | 11h ago |
| 16 | 218.95.39.107:59999 | socks5 | ✓ TLS | China / Chaowai | elite | 3540 ms | 32.69% | 2m ago |
| 17 | 39.129.25.66:8060 | http | — | China / Guangzhou | elite | 2013 ms | 44.15% | 47m ago |
| 18 | 122.246.3.12:17981 | http | ✓ TLS | China / Beijing | elite | 9974 ms | 91.11% | 4h ago |
| 19 | 218.95.39.55:59999 | socks5 | ✓ TLS | China / Chaowai | elite | 2656 ms | 60.42% | 3h ago |
| 20 | 39.172.97.192:8060 | http | — | China / Jiaxing | elite | 5248 ms | 43.8% | 20m ago |
| 21 | 218.95.39.8:59999 | socks5 | ✓ TLS | China / Chaowai | elite | 2255 ms | 19.44% | 8h ago |
| 22 | 120.220.197.199:59999 | socks5 | ✓ TLS | China / Chaowai | elite | 1946 ms | 60% | 22h ago |
| 23 | 183.162.197.197:8060 | http | — | China / Hefei | elite | 7963 ms | 64.32% | 32m ago |
| 24 | 218.95.39.109:59999 | socks5 | ✓ TLS | China / Chaowai | elite | 2083 ms | 62.22% | 3h ago |
| 25 | 218.95.39.48:59999 | socks5 | ✓ TLS | China / Chaowai | elite | 2538 ms | 29.41% | 8h ago |
| 26 | 218.95.39.43:59999 | socks5 | — | China / Chaowai | elite | 1293 ms | 23.33% | 33m ago |
| 27 | 113.46.227.104:2388 | http | ✓ TLS | China / Guangzhou | elite | 4631 ms | 44.26% | 16m ago |
| 28 | 120.220.197.200:59999 | socks5 | ✓ TLS | China / Chaowai | elite | 2617 ms | 55.26% | 8h ago |
| 29 | 218.95.39.67:59999 | socks5 | ✓ TLS | China / Chaowai | elite | 2883 ms | 20.45% | 23h ago |
| 30 | 218.95.39.58:59999 | socks5 | ✓ TLS | China / Chaowai | elite | 3924 ms | 57.89% | 7h ago |
| 31 | 218.95.39.30:59999 | socks5 | ✓ TLS | China / Chaowai | elite | 2733 ms | 21.43% | 8h ago |
| 32 | 120.220.197.196:59999 | socks5 | ✓ TLS | China / Chaowai | elite | 1491 ms | 38.46% | 4h ago |
| 33 | 218.95.39.111:59999 | socks5 | ✓ TLS | China / Chaowai | elite | 7678 ms | 61.36% | 45m ago |
| 34 | 203.3.112.2:6666 | http | — | China / Guangzhou | anonymous | 2078 ms | 30% | 5h ago |
| 35 | 218.95.39.54:59999 | socks5 | ✓ TLS | China / Chaowai | elite | 2936 ms | 45.1% | 8h ago |
| 36 | 218.95.39.49:59999 | socks5 | ✓ TLS | China / Chaowai | elite | 3070 ms | 58.54% | 2h ago |
| 37 | 218.95.39.57:59999 | socks5 | ✓ TLS | China / Chaowai | elite | 1797 ms | 36.21% | 9h ago |
| 38 | 218.95.39.42:59999 | socks5 | — | China / Chaowai | elite | 2364 ms | 39.13% | 1d ago |
| 39 | 180.125.216.109:8118 | http | ✓ TLS | China / Nanjing | elite | 1839 ms | 26.67% | 16h ago |
| 40 | 140.246.125.194:9099 | http | — | China / Jinan | anonymous | 884 ms | 11.11% | 14h ago |
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 China 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.