Skip to contentChina: free SOCKS4 proxies 🇨🇳
China SOCKS4: 6 public proxies marked working in this snapshot. The table also includes check history; recheck before use.
showing 1–60 of 61 (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.
| 10800 | SOCKS4 | 🇨🇳Hohhot | Elite | – | 242 ms | 100% | ||
| 1086 | SOCKS4 | 🇨🇳Shanghai | Elite | – | 222 ms | 95% | ||
| 7890 | SOCKS4 | 🇨🇳Zhangjiakou | Elite | – | 203 ms | 92% | ||
| 4145 | SOCKS4 | 🇨🇳Shanghai | Elite | – | 177 ms | 92% | ||
| 10808 | SOCKS4 | 🇨🇳Hangzhou | Elite | – | 190 ms | 90% | ||
| 10808 | SOCKS4 | 🇨🇳Beijing | Elite | – | 1027 ms | 75% | ||
| 5000 | SOCKS4 | 🇨🇳Beijing | Elite | – | 149 ms | 65% | not working last alive | |
| 10808 | SOCKS4 | 🇨🇳Nanjing | Elite | – | 2720 ms | 60% | not working last alive | |
| 7890 | SOCKS4 | 🇨🇳Guangzhou | Elite | – | 218 ms | 47% | not working last alive | |
| 1080 | SOCKS4 | 🇨🇳Shanghai | Elite | – | 203 ms | 46% | not working last alive | |
| 1080 | SOCKS4 | 🇨🇳Wuxi | Elite | – | 194 ms | 44% | not working last alive | |
| 2411 | SOCKS4 | 🇨🇳Hangzhou | Elite | – | 211 ms | 37% | not working last alive | |
| 10800 | SOCKS4 | 🇨🇳Hefei | Elite | – | 212 ms | 37% | not working last alive | |
| 5678 | SOCKS4 | 🇨🇳Chengdu | Elite | – | 218 ms | 36% | 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 → | ||||||||
| 4145 | SOCKS4 | 🇨🇳Shanghai | Elite | – | 220 ms | 35% | not working last alive | |
| 1080 | SOCKS4 | 🇨🇳Hangzhou | Elite | – | 277 ms | 35% | not working last alive | |
| 1181 | SOCKS4 | 🇨🇳Jinrongjie | Elite | – | 7623 ms | 32% | not working last alive | |
| 1080 | SOCKS4 | 🇨🇳Chongqing | Elite | – | 1416 ms | 32% | not working last alive | |
| 10800 | SOCKS4 | 🇨🇳Chengdu | Elite | – | 237 ms | 31% | not working last alive | |
| 7890 | SOCKS4 | 🇨🇳Chengdu | Elite | – | 7315 ms | 29% | not working last alive | |
| 7890 | SOCKS4 | 🇨🇳Suzhou | Elite | – | 222 ms | 27% | not working last alive | |
| 1083 | SOCKS4 | 🇨🇳Shanghai | Elite | – | 2505 ms | 26% | not working last alive | |
| 6382 | SOCKS4 | 🇨🇳Haidian | Elite | – | 282 ms | 22% | not working last alive | |
| 1084 | SOCKS4 | 🇨🇳Shanghai | Elite | – | 219 ms | 21% | not working last alive | |
| 8989 | SOCKS4 | 🇨🇳Nanjing | Elite | – | 184 ms | 20% | not working last alive | |
| 1080 | SOCKS4 | 🇨🇳Guangzhou | Elite | – | 262 ms | 19% | not working last alive | |
| 50001 | SOCKS4 | 🇨🇳Shaoxing | Elite | – | 214 ms | 18% | not working last alive | |
| 1081 | SOCKS4 | 🇨🇳Beijing | Elite | – | 8204 ms | 17% | not working last alive | |
| 1080 | SOCKS4 | 🇨🇳Shanghai | Elite | – | 242 ms | 17% | not working last alive | |
| 10808 | SOCKS4 | 🇨🇳Zhengzhou | Elite | – | 222 ms | 16% | not working last alive | |
| 10808 | SOCKS4 | 🇨🇳Hangzhou | Elite | – | 210 ms | 13% | not working last alive | |
| 1080 | SOCKS4 | 🇨🇳Dalian | Elite | – | 198 ms | 12% | not working last alive | |
| 4153 | SOCKS4 | 🇨🇳Shanghai | Elite | – | 194 ms | 12% | not working last alive | |
| 1083 | SOCKS4 | 🇨🇳Chengde | Elite | – | 187 ms | 10% | not working last alive | |
| 2000 | SOCKS4 | 🇨🇳Beijing | Elite | – | 2684 ms | 10% | not working last alive | |
| 10808 | SOCKS4 | 🇨🇳Shizishan | Elite | – | 228 ms | 10% | not working last alive | |
| 1088 | SOCKS4 | 🇨🇳Chongqing | Elite | – | 229 ms | 9% | not working last alive | |
| 1081 | SOCKS4 | 🇨🇳Shizishan | Elite | – | 186 ms | 9% | not working last alive | |
| 10808 | SOCKS4 | 🇨🇳Shizishan | Elite | – | 208 ms | 9% | not working last alive | |
| 10808 | SOCKS4 | 🇨🇳Haidian | Elite | – | 2965 ms | 8% | not working last alive | |
| 7892 | SOCKS4 | 🇨🇳Haidian | Elite | – | 5548 ms | 8% | not working last alive | |
| 4153 | SOCKS4 | 🇨🇳Shanghai | Elite | – | 225 ms | 6% | not working last alive | |
| 9999 | SOCKS4 | 🇨🇳Zhaoqing | Elite | – | 203 ms | 5% | not working last alive | |
| 20002 | SOCKS4 | 🇨🇳Jinan | Elite | – | 5519 ms | 5% | not working last alive | |
| 10090 | SOCKS4 | 🇨🇳Haidian | Elite | – | 6511 ms | 4% | not working last alive | |
| 10800 | SOCKS4 | 🇨🇳Chengdu | Elite | – | 219 ms | 4% | not working last alive | |
| 1080 | SOCKS4 | 🇨🇳Guangzhou | Elite | – | 204 ms | 3% | not working last alive | |
| 7890 | SOCKS4 | 🇨🇳Beijing | Elite | – | 5262 ms | 3% | not working last alive | |
| 3080 | SOCKS4 | 🇨🇳Liuzhou | Elite | – | 187 ms | 2% | not working last alive | |
| 4153 | SOCKS4 | 🇨🇳Shenzhen | Elite | – | 203 ms | 2% | not working last alive | |
| 10888 | SOCKS4 | 🇨🇳Fuzhou | Elite | – | 195 ms | 2% | not working last alive | |
| 5080 | SOCKS4 | 🇨🇳Beijing | Elite | – | 174 ms | 2% | not working last alive | |
| 1081 | SOCKS4 | 🇨🇳Jilin | Elite | – | 205 ms | 2% | not working last alive | |
| 7892 | SOCKS4 | 🇨🇳Beijing | Elite | – | 274 ms | 2% | not working last alive | |
| 1081 | SOCKS4 | 🇨🇳Hangzhou | Elite | – | 200 ms | 1% | not working last alive | |
| 1080 | SOCKS4 | 🇨🇳Hangzhou | Elite | – | 199 ms | 1% | not working last alive | |
| 1080 | SOCKS4 | 🇨🇳Guangzhou | Elite | – | 201 ms | 1% | not working last alive | |
| 15976 | SOCKS4 | 🇨🇳Guangzhou | Elite | – | 463 ms | 1% | not working last alive | |
| 8989 | SOCKS4 | 🇨🇳Nanjing | Elite | – | 579 ms | 1% | not working last alive | |
| 7890 | SOCKS4 | 🇨🇳Shanghai | Elite | – | 6752 ms | 0% | 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 6 entries marked working. Mean recorded check success across these entries is 90%; mean recorded response time, where available, is 343 ms. By protocol: SOCKS4 (6). By anonymity level: Elite (6). The most common ports are 10808, 1086, 10800. Measurements come from recorded checks, not a promise of availability. Use ⟳ to recheck before use.
This slice groups public proxy records for China / SOCKS4. 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
- SOCKS4
- working proxies SOCKS4
- SOCKS4 proxies online
- SOCKS5 & HTTP proxies
- what is a SOCKS5 proxy
- fresh free proxies
- proxy list explained
- free proxy list
- socks5 proxies settings
- elite proxies for windows
- working http proxies
Real search phrases this page answers — the linked ones open the page that covers them in depth.