Skip to contentUpdated
China: free HTTP proxies 🇨🇳
China HTTP: 2 public proxies marked working in this snapshot. The table also includes check history; recheck before use.
showing 61–101 of 101 (working first, then history)
2Entries marked working
30%Mean check success
1050 msMedian recorded latency
100%Elite-labelled share
Rows marked “not working” are excluded from the working count. History retains recorded entries; a last-response time is shown when known.
| 21133 | HTTP | 🇨🇳Guangzhou | Transparent | – | 207 ms | 6% | not working last alive | |
| 8118 | HTTP | 🇨🇳Hong Kong | Elite | – | 4410 ms | 5% | not working last alive | |
| 9099 | HTTP | 🇨🇳Jinan | Elite | – | 210 ms | 5% | not working last alive | |
| 9000 | HTTP | 🇨🇳Beijing | Transparent | – | 217 ms | 5% | not working last alive | |
| 8087 | HTTP | 🇨🇳Shizishan | Elite | – | 5830 ms | 4% | not working last alive | |
| 11111 | HTTP | 🇨🇳Guangzhou | Elite | – | 2834 ms | 4% | not working last alive | |
| 45134 | HTTP | 🇨🇳Beijing | Elite | – | 183 ms | 4% | not working last alive | |
| 45041 | HTTP | 🇨🇳Beijing | Elite | – | 193 ms | 4% | not working last alive | |
| 45001 | HTTP | 🇨🇳Beijing | Elite | – | 199 ms | 4% | not working last alive | |
| 18255 | HTTP | 🇨🇳Chongqing | Elite | – | 241 ms | 4% | not working last alive | |
| 3128 | HTTP | 🇨🇳Shanghai | Transparent | – | 227 ms | 3% | not working last alive | |
| 18888 | HTTP | 🇨🇳Jinrongjie | Elite | – | 253 ms | 3% | not working last alive | |
| 1080 | HTTP | 🇨🇳Guangzhou | Elite | – | 249 ms | 3% | not working last alive | |
| 7890 | HTTP | 🇨🇳Chengdu | Elite | – | 5994 ms | 3% | 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 → | ||||||||
| 8081 | HTTP | 🇨🇳Nanjing | Elite | – | 6281 ms | 3% | not working last alive | |
| 1081 | HTTP | 🇨🇳Shizishan | Elite | – | 3592 ms | 3% | not working last alive | |
| 45077 | HTTP | 🇨🇳Beijing | Elite | – | 190 ms | 3% | not working last alive | |
| 45075 | HTTP | 🇨🇳Beijing | Elite | – | 183 ms | 3% | not working last alive | |
| 3128 | HTTP | 🇨🇳Shanghai | Anonymous | – | 240 ms | 3% | not working last alive | |
| 8080 | HTTP | 🇨🇳Jinrongjie | Elite | – | 6309 ms | 2% | not working last alive | |
| 1081 | HTTP | 🇨🇳Beijing | Elite | – | 174 ms | 2% | not working last alive | |
| 45150 | HTTP | 🇨🇳Beijing | Elite | – | 183 ms | 2% | not working last alive | |
| 9999 | HTTP | 🇨🇳Zhaoqing | Elite | – | 214 ms | 2% | not working last alive | |
| 45090 | HTTP | 🇨🇳Beijing | Elite | – | 206 ms | 2% | not working last alive | |
| 7890 | HTTP | 🇨🇳Hangzhou | Elite | – | 227 ms | 2% | not working last alive | |
| 8899 | HTTP | 🇨🇳Nanjing | Elite | – | 5273 ms | 1% | not working last alive | |
| 1080 | HTTP | 🇨🇳Nanjing | Elite | – | 198 ms | 1% | not working last alive | |
| 8118 | HTTP | 🇨🇳Chengdu | Elite | – | 227 ms | 1% | not working last alive | |
| 45199 | HTTP | 🇨🇳Beijing | Elite | – | 183 ms | 1% | not working last alive | |
| 45103 | HTTP | 🇨🇳Beijing | Elite | – | 183 ms | 1% | not working last alive | |
| 45231 | HTTP | 🇨🇳Beijing | Elite | – | 179 ms | 1% | not working last alive | |
| 45006 | HTTP | 🇨🇳Beijing | Elite | – | 180 ms | 1% | not working last alive | |
| 45177 | HTTP | 🇨🇳Beijing | Elite | – | 201 ms | 1% | not working last alive | |
| 8080 | HTTP | 🇨🇳Chengdu | Elite | – | 204 ms | 1% | not working last alive | |
| 8085 | HTTP | 🇨🇳Hangzhou | Elite | – | 229 ms | 1% | not working last alive | |
| 3128 | HTTP | 🇨🇳Jinrongjie | Elite | – | 494 ms | 1% | not working last alive | |
| 9091 | HTTP | 🇨🇳Jinrongjie | Elite | – | 256 ms | 0% | not working last alive | |
| 1083 | HTTP | 🇨🇳Xiamen | Elite | – | 215 ms | 0% | not working last alive | |
| 45116 | HTTP | 🇨🇳Beijing | Elite | – | 2585 ms | 0% | not working last alive | |
| 45062 | HTTP | 🇨🇳Beijing | Elite | – | 206 ms | 0% | not working last alive | |
| 45221 | HTTP | 🇨🇳Beijing | Elite | – | 192 ms | 0% | not working last alive | |
Public proxy reminder
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.
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
- free proxy list
- free HTTP proxy
- proxy server HTTP
- what is a SOCKS5 proxy
- elite proxies
- dedicated ip plans
- public proxies list txt
- working proxies list
- fresh free proxies
- socks5 proxies
- working http proxies
- http proxies
- free socks5 proxies
- how to check dedicated ip
- socks5 proxy
- SOCKS5 & HTTP proxies
- is http proxies safe
Real search phrases this page answers — the linked ones open the page that covers them in depth.