Hong Kong: free HTTP proxies 🇭🇰
Hong Kong HTTP: 4 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.
| 1080 | HTTP | 🇭🇰Hong Kong | Elite | – | 195 ms | 100% | ||
| 8080 | HTTP | 🇭🇰Hong Kong | Transparent | – | 325 ms | 100% | ||
| 8080 | HTTP | 🇭🇰Kwai Chung | Transparent | – | 3252 ms | 12% | ||
| 8888 | HTTP | 🇭🇰Kwai Chung | Elite | – | 4601 ms | 9% | ||
| 1080 | HTTP | 🇭🇰Hong Kong | Elite | – | 258 ms | 49% | not working last alive | |
| 808 | HTTP | 🇭🇰Mong Kok | Elite | – | 163 ms | 49% | not working last alive | |
| 8118 | HTTP | 🇭🇰Hong Kong | Elite | – | 242 ms | 49% | not working last alive | |
| 888 | HTTP | 🇭🇰Hong Kong | Elite | – | 244 ms | 49% | not working last alive | |
| 80 | HTTP | 🇭🇰Hong Kong | Elite | – | 252 ms | 49% | not working last alive | |
| 3128 | HTTP | 🇭🇰Hong Kong | Transparent | – | 233 ms | 49% | not working last alive | |
| 80 | HTTP | 🇭🇰Hong Kong | Elite | – | 176 ms | 49% | not working last alive | |
| 3125 | HTTP | 🇭🇰Kwun Tong | Transparent | – | 182 ms | 49% | not working last alive | |
| 12366 | HTTP | 🇭🇰Hong Kong | Elite | – | 250 ms | 48% | not working last alive | |
| 3125 | HTTP | 🇭🇰Kwun Tong | Transparent | – | 182 ms | 48% | 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 → | ||||||||
| 3128 | HTTP | 🇭🇰Hong Kong | Elite | – | 241 ms | 48% | not working last alive | |
| 3125 | HTTP | 🇭🇰Kwun Tong | Transparent | – | 181 ms | 48% | not working last alive | |
| 8888 | HTTP | 🇭🇰Hong Kong | Elite | – | 2153 ms | 48% | not working last alive | |
| 3125 | HTTP | 🇭🇰Kwun Tong | Transparent | – | 8826 ms | 45% | not working last alive | |
| 8888 | HTTP | 🇭🇰Lau Fau Shan | Elite | – | 246 ms | 43% | not working last alive | |
| 443 | HTTP | 🇭🇰Fanling | Elite | – | 1293 ms | 38% | not working last alive | |
| 1081 | HTTP | 🇭🇰Hong Kong | Elite | – | 2005 ms | 35% | not working last alive | |
| 8118 | HTTP | 🇭🇰Hong Kong | Elite | – | 241 ms | 34% | not working last alive | |
| 3128 | HTTP | 🇭🇰Hong Kong | Transparent | – | 240 ms | 32% | not working last alive | |
| 443 | HTTP | 🇭🇰Hong Kong | Elite | – | 201 ms | 31% | not working last alive | |
| 3128 | HTTP | 🇭🇰Hong Kong | Transparent | – | 235 ms | 30% | not working last alive | |
| 8118 | HTTP | 🇭🇰Hong Kong | Elite | – | 1009 ms | 30% | not working last alive | |
| 3129 | HTTP | 🇭🇰Mong Kok | Elite | – | 5931 ms | 25% | not working last alive | |
| 3128 | HTTP | 🇭🇰Hong Kong | Transparent | – | 5094 ms | 23% | not working last alive | |
| 80 | HTTP | 🇭🇰Hong Kong | Elite | – | 173 ms | 23% | not working last alive | |
| 80 | HTTP | 🇭🇰Hong Kong | Elite | – | 173 ms | 22% | not working last alive | |
| 80 | HTTP | 🇭🇰Hong Kong | Elite | – | 173 ms | 22% | not working last alive | |
| 10023 | HTTP | 🇭🇰Hong Kong | Anonymous | – | 326 ms | 21% | not working last alive | |
| 80 | HTTP | 🇭🇰Hong Kong | Elite | – | 173 ms | 21% | not working last alive | |
| 8080 | HTTP | 🇭🇰Hong Kong | Elite | – | 1200 ms | 20% | not working last alive | |
| 3128 | HTTP | 🇭🇰Ha Kwai Chung | Transparent | – | 187 ms | 20% | not working last alive | |
| 80 | HTTP | 🇭🇰Hong Kong | Elite | – | 173 ms | 20% | not working last alive | |
| 8888 | HTTP | 🇭🇰Hong Kong | Elite | – | 181 ms | 20% | not working last alive | |
| 8080 | HTTP | 🇭🇰North Jakarta | Transparent | – | 1677 ms | 18% | not working last alive | |
| 7890 | HTTP | 🇭🇰Hong Kong | Elite | – | 970 ms | 17% | not working last alive | |
| 8888 | HTTP | 🇭🇰Hong Kong | Elite | – | 1018 ms | 15% | not working last alive | |
| 8080 | HTTP | 🇭🇰Hong Kong | Elite | – | 179 ms | 15% | not working last alive | |
| 7890 | HTTP | 🇭🇰Hong Kong | Elite | – | 5415 ms | 14% | not working last alive | |
| 8118 | HTTP | 🇭🇰Shatin | Elite | – | 187 ms | 14% | not working last alive | |
| 9055 | HTTP | 🇭🇰Hong Kong | Elite | – | 247 ms | 13% | not working last alive | |
| 3128 | HTTP | 🇭🇰Mong Kok | Anonymous | – | 238 ms | 13% | not working last alive | |
| 1081 | HTTP | 🇭🇰Braemar Hill Mansions | Elite | – | 8491 ms | 10% | not working last alive | |
| 3129 | HTTP | 🇭🇰Central | Anonymous | – | 4323 ms | 8% | not working last alive | |
| 1080 | HTTP | 🇭🇰Central | Elite | – | 1254 ms | 8% | not working last alive | |
| 80 | HTTP | 🇭🇰Hong Kong | Elite | – | 5123 ms | 7% | not working last alive | |
| 11080 | HTTP | 🇭🇰Hong Kong | Elite | – | 7344 ms | 6% | not working last alive | |
| 20005 | HTTP | 🇭🇰Wan Chai | Elite | – | 3256 ms | 6% | not working last alive | |
| 443 | HTTP | 🇭🇰Hong Kong | Elite | – | 8613 ms | 5% | not working last alive | |
| 10080 | HTTP | 🇭🇰San Po Kong | Elite | – | 5608 ms | 5% | not working last alive | |
| 3125 | HTTP | 🇭🇰Kwun Tong | Transparent | – | 3688 ms | 4% | not working last alive | |
| 12522 | HTTP | 🇭🇰Hong Kong | Elite | – | 1247 ms | 4% | not working last alive | |
| 808 | HTTP | 🇭🇰Mong Kok | Elite | – | 4147 ms | 2% | not working last alive | |
| 8080 | HTTP | 🇭🇰Hong Kong | Elite | – | 1133 ms | 2% | not working last alive | |
| 3128 | HTTP | 🇭🇰Hong Kong | Transparent | – | 1936 ms | 1% | not working last alive | |
| 8213 | HTTP | 🇭🇰Hong Kong | Transparent | – | 6716 ms | 1% | not working last alive | |
| 1775 | HTTP | 🇭🇰Pattaya | Elite | – | 1432 ms | 1% | 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 4 entries marked working. Mean recorded check success across these entries is 55%; mean recorded response time, where available, is 2093 ms. By protocol: HTTP (4). By anonymity level: Elite (2), Transparent (2). The most common ports are 8080, 1080, 8888. Measurements come from recorded checks, not a promise of availability. Use ⟳ to recheck before use.
This slice groups public proxy records for Hong Kong / 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
- what is a SOCKS5 proxy
- HTTP proxy list
- anonymous proxies HTTP
- proxy server HTTP
- SOCKS5 & HTTP proxies
- working proxies
- dedicated ip settings
- dedicated ip with crypto payment
- elite proxies
- fresh socks5 proxies
- free proxy list
Real search phrases this page answers — the linked ones open the page that covers them in depth.