China: free HTTPS proxies 🇨🇳
China HTTPS: latest snapshot has no proxies marked working. See check history and last-seen times; recheck before use.
showing 1–60 of 132 (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.
| 11111 | HTTPS | 🇨🇳Taizhou | Elite | ✓ | 254 ms | 49% | not working last alive | |
| 8081 | HTTPS | 🇨🇳Nanjing | Elite | ✓ | 257 ms | 49% | not working last alive | |
| 7080 | HTTPS | 🇨🇳Beijing | Elite | ✓ | 156 ms | 49% | not working last alive | |
| 80 | HTTPS | 🇨🇳Wuhan | Transparent | ✓ | 215 ms | 49% | not working last alive | |
| 15543 | HTTPS | 🇨🇳Lishui | Elite | ✓ | 198 ms | 48% | not working last alive | |
| 20172 | HTTPS | 🇨🇳Chengdu | Elite | ✓ | 262 ms | 48% | not working last alive | |
| 8816 | HTTPS | 🇨🇳Suzhou | Transparent | ✓ | 209 ms | 47% | not working last alive | |
| 11111 | HTTPS | 🇨🇳Taizhou | Elite | ✓ | 247 ms | 47% | not working last alive | |
| 8017 | HTTPS | 🇨🇳Chongqing | Transparent | ✓ | 224 ms | 47% | not working last alive | |
| 8080 | HTTPS | 🇨🇳Chengdu | Elite | ✓ | 221 ms | 46% | not working last alive | |
| 3128 | HTTPS | 🇨🇳Shanghai | Anonymous | ✓ | 195 ms | 46% | not working last alive | |
| 15818 | HTTPS | 🇨🇳Shanghai | Transparent | ✓ | 173 ms | 45% | not working last alive | |
| 3128 | HTTPS | 🇨🇳Jinrongjie | Elite | ✓ | 180 ms | 44% | not working last alive | |
| 3128 | HTTPS | 🇨🇳Beijing | Transparent | ✓ | 217 ms | 44% | 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 → | ||||||||
| 3333 | HTTPS | 🇨🇳Beijing | Transparent | ✓ | 163 ms | 43% | not working last alive | |
| 9401 | HTTPS | 🇨🇳Xi'an | Elite | ✓ | 200 ms | 42% | not working last alive | |
| 10808 | HTTPS | 🇨🇳Nanjing | Elite | ✓ | 1400 ms | 41% | not working last alive | |
| 9480 | HTTPS | 🇨🇳Xi'an | Elite | ✓ | 211 ms | 41% | not working last alive | |
| 8800 | HTTPS | 🇨🇳Xi'an | Elite | ✓ | 193 ms | 41% | not working last alive | |
| 14249 | HTTPS | 🇨🇳Lishui | Elite | ✓ | 198 ms | 36% | not working last alive | |
| 7890 | HTTPS | 🇨🇳Guangzhou | Elite | ✓ | 8631 ms | 35% | not working last alive | |
| 10808 | HTTPS | 🇨🇳Beijing | Elite | ✓ | 2491 ms | 35% | not working last alive | |
| 1081 | HTTPS | 🇨🇳Beijing | Elite | ✓ | 203 ms | 34% | not working last alive | |
| 9445 | HTTPS | 🇨🇳Hechi | Transparent | ✓ | 157 ms | 33% | not working last alive | |
| 3128 | HTTPS | 🇨🇳Shanghai | Transparent | ✓ | 229 ms | 29% | not working last alive | |
| 9000 | HTTPS | 🇨🇳Beijing | Transparent | ✓ | 152 ms | 27% | not working last alive | |
| 9099 | HTTPS | 🇨🇳Jinan | Elite | ✓ | 218 ms | 24% | not working last alive | |
| 10808 | HTTPS | 🇨🇳Chongqing | Elite | ✓ | 202 ms | 24% | not working last alive | |
| 9000 | HTTPS | 🇨🇳Beijing | Transparent | ✓ | 152 ms | 24% | not working last alive | |
| 13561 | HTTPS | 🇨🇳Lishui | Elite | ✓ | 275 ms | 23% | not working last alive | |
| 7890 | HTTPS | 🇨🇳Chengdu | Elite | ✓ | 225 ms | 22% | not working last alive | |
| 9000 | HTTPS | 🇨🇳Beijing | Transparent | ✓ | 214 ms | 21% | not working last alive | |
| 7890 | HTTPS | 🇨🇳Suzhou | Elite | ✓ | 3167 ms | 21% | not working last alive | |
| 9000 | HTTPS | 🇨🇳Beijing | Transparent | ✓ | 165 ms | 18% | not working last alive | |
| 8080 | HTTPS | 🇨🇳Haidian | Transparent | ✓ | 1426 ms | 17% | not working last alive | |
| 2021 | HTTPS | 🇨🇳Shanghai | Transparent | ✓ | 163 ms | 16% | not working last alive | |
| 8081 | HTTPS | 🇨🇳Nanjing | Elite | ✓ | 8513 ms | 16% | not working last alive | |
| 7890 | HTTPS | 🇨🇳Shanghai | Elite | ✓ | 158 ms | 16% | not working last alive | |
| 3128 | HTTPS | 🇨🇳Jinrongjie | Anonymous | ✓ | 7508 ms | 15% | not working last alive | |
| 14942 | HTTPS | 🇨🇳Lishui | Elite | ✓ | 199 ms | 15% | not working last alive | |
| 3128 | HTTPS | 🇨🇳Beijing | Transparent | ✓ | 2187 ms | 15% | not working last alive | |
| 8080 | HTTPS | 🇨🇳Guangzhou | Elite | ✓ | 215 ms | 14% | not working last alive | |
| 18888 | HTTPS | 🇨🇳Jinrongjie | Elite | ✓ | 239 ms | 14% | not working last alive | |
| 8088 | HTTPS | 🇨🇳Huilongguan | Transparent | ✓ | 175 ms | 13% | not working last alive | |
| 1080 | HTTPS | 🇨🇳Nanjing | Elite | ✓ | 179 ms | 13% | not working last alive | |
| 8888 | HTTPS | 🇨🇳Beijing | Elite | ✓ | 228 ms | 13% | not working last alive | |
| 13126 | HTTPS | 🇨🇳Beijing | Elite | ✓ | 196 ms | 12% | not working last alive | |
| 8118 | HTTPS | 🇨🇳Guangzhou | Elite | ✓ | 7919 ms | 12% | not working last alive | |
| 13088 | HTTPS | 🇨🇳Lishui | Elite | ✓ | 320 ms | 12% | not working last alive | |
| 12945 | HTTPS | 🇨🇳Lishui | Elite | ✓ | 333 ms | 12% | not working last alive | |
| 10809 | HTTPS | 🇨🇳Haidian | Elite | ✓ | 2927 ms | 11% | not working last alive | |
| 2088 | HTTPS | 🇨🇳Nanjing | Elite | ✓ | 2548 ms | 11% | not working last alive | |
| 8118 | HTTPS | 🇨🇳Liaocheng | Elite | ✓ | 8434 ms | 10% | not working last alive | |
| 12525 | HTTPS | 🇨🇳Lishui | Elite | ✓ | 212 ms | 10% | not working last alive | |
| 1081 | HTTPS | 🇨🇳Guangzhou | Elite | ✓ | 262 ms | 9% | not working last alive | |
| 1081 | HTTPS | 🇨🇳Shizishan | Elite | ✓ | 245 ms | 9% | not working last alive | |
| 1080 | HTTPS | 🇨🇳Nanjing | Elite | ✓ | 229 ms | 9% | not working last alive | |
| 18181 | HTTPS | 🇨🇳Guangzhou | Transparent | ✓ | 195 ms | 9% | not working last alive | |
| 8002 | HTTPS | 🇨🇳Guangzhou | Elite | ✓ | 324 ms | 9% | not working last alive | |
| 7890 | HTTPS | 🇨🇳Chengdu | Elite | ✓ | 235 ms | 9% | 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.
This slice groups public proxy records for China / HTTPS. 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
- HTTPS
- proxy server HTTPS
- HTTPS ip address
- free proxies HTTPS
- SOCKS5 & HTTP proxies
- free proxy list
- anonymous proxies
- what is a SOCKS5 proxy
- public proxies
- proxy list
- socks5 proxies without registration
- download elite proxies
- proxy list tutorial
Real search phrases this page answers — the linked ones open the page that covers them in depth.