China: free HTTP proxies 🇨🇳
China HTTP: 14 public proxies marked working in this snapshot. The table also includes check history; recheck before use.
showing 1–60 of 103 (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.
| 9000 | HTTP | 🇨🇳Beijing | Transparent | – | 177 ms | 100% | ||
| 8085 | HTTP | 🇨🇳Haikou | Elite | – | 192 ms | 100% | ||
| 17981 | HTTP | 🇨🇳Shanwei | Elite | – | 183 ms | 100% | ||
| 7080 | HTTP | 🇨🇳Shanghai | Transparent | – | 194 ms | 100% | ||
| 9000 | HTTP | 🇨🇳Beijing | Transparent | – | 220 ms | 97% | ||
| 8060 | HTTP | 🇨🇳Guangzhou | Elite | – | 320 ms | 97% | ||
| 9002 | HTTP | 🇨🇳Zhengzhou | Elite | – | 171 ms | 97% | ||
| 8080 | HTTP | 🇨🇳Haidian | Elite | – | 191 ms | 96% | ||
| 9000 | HTTP | 🇨🇳Beijing | Transparent | – | 152 ms | 96% | ||
| 8118 | HTTP | 🇨🇳Nanjing | Elite | – | 212 ms | 95% | ||
| 3128 | HTTP | 🇨🇳Beijing | Transparent | – | 199 ms | 92% | ||
| 8118 | HTTP | 🇨🇳Shanghai | Elite | – | 198 ms | 91% | ||
| 8118 | HTTP | 🇨🇳Jinan | Elite | – | 166 ms | 51% | ||
| 1181 | HTTP | 🇨🇳Jinrongjie | Elite | – | 3084 ms | 26% | ||
| Private connection options Compare authenticated SOCKS5/HTTP and optional dedicated IP plans. Check the service terms; availability can vary. See s4m Proxy → | ||||||||
| 11101 | HTTP | 🇨🇳Taizhou | Elite | – | 191 ms | 49% | not working last alive | |
| 5004 | HTTP | 🇨🇳Guangzhou | Elite | – | 173 ms | 48% | not working last alive | |
| 7890 | HTTP | 🇨🇳Beijing | Elite | – | 204 ms | 48% | not working last alive | |
| 13128 | HTTP | 🇨🇳Chengdu | Anonymous | – | 216 ms | 47% | not working last alive | |
| 3128 | HTTP | 🇨🇳Jinrongjie | Elite | – | 191 ms | 47% | not working last alive | |
| 80 | HTTP | 🇨🇳Haidian | Elite | – | 242 ms | 47% | not working last alive | |
| 80 | HTTP | 🇨🇳Changzhou | Elite | – | 175 ms | 47% | not working last alive | |
| 8880 | HTTP | 🇨🇳Ulanqab | Elite | – | 261 ms | 45% | not working last alive | |
| 808 | HTTP | 🇨🇳Beijing | Elite | – | 160 ms | 40% | not working last alive | |
| 80 | HTTP | 🇨🇳Haidian | Transparent | – | 268 ms | 38% | not working last alive | |
| 7890 | HTTP | 🇨🇳Guangzhou | Elite | – | 2357 ms | 38% | not working last alive | |
| 8060 | HTTP | 🇨🇳Jiaxing | Elite | – | 239 ms | 37% | not working last alive | |
| 8088 | HTTP | 🇨🇳Huilongguan | Transparent | – | 175 ms | 37% | not working last alive | |
| 8060 | HTTP | 🇨🇳Fuzhou | Elite | – | 268 ms | 36% | not working last alive | |
| 9000 | HTTP | 🇨🇳Shenzhen | Transparent | – | 215 ms | 35% | not working last alive | |
| 8118 | HTTP | 🇨🇳Guangzhou | Elite | – | 169 ms | 33% | not working last alive | |
| 2021 | HTTP | 🇨🇳Shanghai | Transparent | – | 211 ms | 28% | not working last alive | |
| 3128 | HTTP | 🇨🇳Jinrongjie | Anonymous | – | 1884 ms | 27% | not working last alive | |
| 8009 | HTTP | 🇨🇳Nanjing | Elite | – | 175 ms | 26% | not working last alive | |
| 6666 | HTTP | 🇨🇳Hangzhou | Elite | – | 219 ms | 25% | not working last alive | |
| 8989 | HTTP | 🇨🇳Guangzhou | Elite | – | 318 ms | 25% | not working last alive | |
| 6666 | HTTP | 🇨🇳Guangzhou | Elite | – | 222 ms | 24% | not working last alive | |
| 9000 | HTTP | 🇨🇳Beijing | Transparent | – | 161 ms | 23% | not working last alive | |
| 2088 | HTTP | 🇨🇳Nanjing | Elite | – | 206 ms | 23% | not working last alive | |
| 2411 | HTTP | 🇨🇳Hangzhou | Elite | – | 3214 ms | 22% | not working last alive | |
| 8080 | HTTP | 🇨🇳Guangzhou | Elite | – | 216 ms | 21% | not working last alive | |
| 3128 | HTTP | 🇨🇳Shanghai | Transparent | – | 198 ms | 21% | not working last alive | |
| 1081 | HTTP | 🇨🇳Guangzhou | Elite | – | 260 ms | 17% | not working last alive | |
| 9000 | HTTP | 🇨🇳Shenzhen | Transparent | – | 224 ms | 14% | not working last alive | |
| 9002 | HTTP | 🇨🇳Chongqing | Elite | – | 286 ms | 14% | not working last alive | |
| 3128 | HTTP | 🇨🇳Beijing | Transparent | – | 199 ms | 13% | not working last alive | |
| 7890 | HTTP | 🇨🇳Shijiazhuang | Elite | – | 1594 ms | 13% | not working last alive | |
| 18181 | HTTP | 🇨🇳Guangzhou | Transparent | – | 205 ms | 12% | not working last alive | |
| 8118 | HTTP | 🇨🇳Jinrongjie | Elite | – | 228 ms | 12% | not working last alive | |
| 9000 | HTTP | 🇨🇳Shenzhen | Transparent | – | 219 ms | 12% | not working last alive | |
| 9000 | HTTP | 🇨🇳Beijing | Transparent | – | 182 ms | 11% | not working last alive | |
| 1088 | HTTP | 🇨🇳Chongqing | Elite | – | 173 ms | 11% | not working last alive | |
| 8085 | HTTP | 🇨🇳Hangzhou | Elite | – | 294 ms | 10% | not working last alive | |
| 10090 | HTTP | 🇨🇳Haidian | Elite | – | 217 ms | 9% | not working last alive | |
| 1080 | HTTP | 🇨🇳Nanjing | Elite | – | 234 ms | 9% | not working last alive | |
| 2388 | HTTP | 🇨🇳Guangzhou | Transparent | – | 185 ms | 8% | not working last alive | |
| 25000 | HTTP | 🇨🇳Taohua | Elite | – | 244 ms | 8% | not working last alive | |
| 9445 | HTTP | 🇨🇳Hechi | Transparent | – | 175 ms | 6% | not working last alive | |
| 8085 | HTTP | 🇨🇳Hangzhou | Elite | – | 297 ms | 6% | not working last alive | |
| 18080 | HTTP | 🇨🇳Nanjing | Transparent | – | 166 ms | 6% | not working last alive | |
| 45051 | HTTP | 🇨🇳Beijing | Elite | – | 187 ms | 6% | 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 14 entries marked working. Mean recorded check success across these entries is 88%; mean recorded response time, where available, is 404 ms. By protocol: HTTP (14). By anonymity level: Elite (9), Transparent (5). The most common ports are 8118, 9000, 17981. Measurements come from recorded checks, not a promise of availability. Use ⟳ to recheck before use.
This slice groups public proxy records for China / HTTP. 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
- HTTP
- HTTP proxies online
- proxy server HTTP
- anonymous proxies HTTP
- HTTP ip address
- free proxy list
- proxy list
- http proxies
- socks5 proxy for android
- SOCKS5 & HTTP proxies
- what is a SOCKS5 proxy
Real search phrases this page answers — the linked ones open the page that covers them in depth.