Skip to contentChina: free SOCKS5 proxies 🇨🇳
China SOCKS5: 11 public proxies marked working in this snapshot. The table also includes check history; recheck before use.
showing 1–60 of 174 (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.
| 1080 | SOCKS5 | 🇨🇳Guangzhou | Elite | – | 226 ms | 100% | ||
| 39105 | SOCKS5 | 🇨🇳Chongqing | Elite | – | 192 ms | 98% | ||
| 1080 | SOCKS5 | 🇨🇳Jinan | Elite | – | 175 ms | 97% | ||
| 63180 | SOCKS5 | 🇨🇳Fuzhou | Elite | – | 278 ms | 95% | ||
| 15163 | SOCKS5 | 🇨🇳Beijing | Elite | – | 158 ms | 93% | ||
| 59999 | SOCKS5 | 🇨🇳Nanchangshi | Elite | – | 239 ms | 92% | ||
| 59999 | SOCKS5 | 🇨🇳Nanchangshi | Elite | – | 230 ms | 92% | ||
| 1080 | SOCKS5 | 🇨🇳Chongqing | Elite | – | 212 ms | 82% | ||
| 1080 | SOCKS5 | 🇨🇳Guangzhou | Elite | – | 259 ms | 69% | ||
| 10808 | SOCKS5 | 🇨🇳Beijing | Elite | – | 2040 ms | 66% | ||
| 1081 | SOCKS5 | 🇨🇳Fuzhou | Elite | – | 239 ms | 43% | ||
| 10808 | SOCKS5 | 🇨🇳Nanjing | Elite | – | 304 ms | 62% | not working last alive | |
| 1080 | SOCKS5 | 🇨🇳Guangzhou | Elite | – | 184 ms | 56% | not working last alive | |
| 7890 | SOCKS5 | 🇨🇳Haidian | Elite | – | 225 ms | 49% | 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 → | ||||||||
| 7890 | SOCKS5 | 🇨🇳Chongqing | Elite | – | 183 ms | 49% | not working last alive | |
| 59999 | SOCKS5 | 🇨🇳Guangzhou | Elite | – | 283 ms | 48% | not working last alive | |
| 6666 | SOCKS5 | 🇨🇳Shangli | Elite | – | 204 ms | 48% | not working last alive | |
| 80 | SOCKS5 | 🇨🇳Guangzhou | Elite | – | 203 ms | 48% | not working last alive | |
| 32735 | SOCKS5 | 🇨🇳Chongqing | Elite | – | 247 ms | 48% | not working last alive | |
| 59999 | SOCKS5 | 🇨🇳Nanchangshi | Elite | – | 229 ms | 47% | not working last alive | |
| 1080 | SOCKS5 | 🇨🇳Wenzhou | Elite | – | 180 ms | 47% | not working last alive | |
| 10808 | SOCKS5 | 🇨🇳Beijing | Elite | – | 160 ms | 47% | not working last alive | |
| 1080 | SOCKS5 | 🇨🇳Ningbo | Elite | – | 214 ms | 47% | not working last alive | |
| 59999 | SOCKS5 | 🇨🇳Nanchangshi | Elite | – | 201 ms | 47% | not working last alive | |
| 2080 | SOCKS5 | 🇨🇳Guangzhou | Elite | – | 189 ms | 47% | not working last alive | |
| 59999 | SOCKS5 | 🇨🇳Nanchangshi | Elite | – | 194 ms | 46% | not working last alive | |
| 1080 | SOCKS5 | 🇨🇳Shanghai | Elite | – | 205 ms | 46% | not working last alive | |
| 64077 | SOCKS5 | 🇨🇳Beijing | Elite | – | 192 ms | 46% | not working last alive | |
| 2080 | SOCKS5 | 🇨🇳Shanghai | Elite | – | 201 ms | 46% | not working last alive | |
| 1080 | SOCKS5 | 🇨🇳Beijing | Elite | – | 150 ms | 46% | not working last alive | |
| 59999 | SOCKS5 | 🇨🇳Nanchangshi | Elite | – | 217 ms | 46% | not working last alive | |
| 7001 | SOCKS5 | 🇨🇳Shanghai | Elite | – | 231 ms | 45% | not working last alive | |
| 59999 | SOCKS5 | 🇨🇳Nanchangshi | Elite | – | 202 ms | 45% | not working last alive | |
| 59999 | SOCKS5 | 🇨🇳Nanchangshi | Elite | – | 179 ms | 45% | not working last alive | |
| 59999 | SOCKS5 | 🇨🇳Nanchangshi | Elite | – | 211 ms | 43% | not working last alive | |
| 59999 | SOCKS5 | 🇨🇳Nanchangshi | Elite | – | 241 ms | 43% | not working last alive | |
| 59999 | SOCKS5 | 🇨🇳Guangzhou | Elite | – | 286 ms | 42% | not working last alive | |
| 59999 | SOCKS5 | 🇨🇳Nanchangshi | Elite | – | 214 ms | 42% | not working last alive | |
| 59999 | SOCKS5 | 🇨🇳Nanchangshi | Elite | – | 232 ms | 42% | not working last alive | |
| 59999 | SOCKS5 | 🇨🇳Nanchangshi | Elite | – | 229 ms | 41% | not working last alive | |
| 1080 | SOCKS5 | 🇨🇳Chongqing | Elite | – | 208 ms | 40% | not working last alive | |
| 7000 | SOCKS5 | 🇨🇳Shanghai | Elite | – | 205 ms | 38% | not working last alive | |
| 1080 | SOCKS5 | 🇨🇳Shanghai | Elite | – | 203 ms | 37% | not working last alive | |
| 1088 | SOCKS5 | 🇨🇳Beijing | Elite | – | 142 ms | 35% | not working last alive | |
| 1080 | SOCKS5 | 🇨🇳Guangzhou | Elite | – | 223 ms | 34% | not working last alive | |
| 1181 | SOCKS5 | 🇨🇳Jinrongjie | Elite | – | 5432 ms | 33% | not working last alive | |
| 1081 | SOCKS5 | 🇨🇳Jinan | Elite | – | 4987 ms | 32% | not working last alive | |
| 8989 | SOCKS5 | 🇨🇳Suzhou | Elite | – | 233 ms | 30% | not working last alive | |
| 10800 | SOCKS5 | 🇨🇳Hangzhou | Elite | – | 2515 ms | 29% | not working last alive | |
| 9009 | SOCKS5 | 🇨🇳Liuzhou | Elite | – | 201 ms | 29% | not working last alive | |
| 7891 | SOCKS5 | 🇨🇳Hefei | Elite | – | 187 ms | 29% | not working last alive | |
| 1080 | SOCKS5 | 🇨🇳Guangzhou | Elite | – | 208 ms | 28% | not working last alive | |
| 59999 | SOCKS5 | 🇨🇳Nanchangshi | Elite | – | 252 ms | 28% | not working last alive | |
| 7001 | SOCKS5 | 🇨🇳Shanghai | Elite | – | 205 ms | 25% | not working last alive | |
| 2411 | SOCKS5 | 🇨🇳Hangzhou | Elite | – | 3057 ms | 24% | not working last alive | |
| 1314 | SOCKS5 | 🇨🇳Shanghai | Elite | – | 201 ms | 24% | not working last alive | |
| 18888 | SOCKS5 | 🇨🇳Jinrongjie | Elite | – | 239 ms | 23% | not working last alive | |
| 1080 | SOCKS5 | 🇨🇳Changsha | Elite | – | 1568 ms | 23% | not working last alive | |
| 1081 | SOCKS5 | 🇨🇳Beijing | Elite | – | 162 ms | 23% | not working last alive | |
| 1080 | SOCKS5 | 🇨🇳Xiaogan | Elite | – | 195 ms | 23% | 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 11 entries marked working. Mean recorded check success across these entries is 84%; mean recorded response time, where available, is 386 ms. By protocol: SOCKS5 (11). By anonymity level: Elite (11). The most common ports are 1080, 59999, 39105. Measurements come from recorded checks, not a promise of availability. Use ⟳ to recheck before use.
This slice groups public proxy records for China / SOCKS5. 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
- SOCKS5
- anonymous proxies SOCKS5
- free proxies SOCKS5
- SOCKS5 proxies online
- working proxies SOCKS5
- free proxy list
- download elite proxies
- anonymous proxies
- socks5 proxy
- SOCKS5 & HTTP proxies
- how dedicated ip works
- how to check working proxies
- dedicated ip
- public proxies
- free working proxies
- best anonymous proxies 2026
- proxy list for android
- what is a SOCKS5 proxy
Real search phrases this page answers — the linked ones open the page that covers them in depth.