Singapore: free HTTP proxies 🇸🇬
Singapore HTTP: 12 public proxies marked working in this snapshot. The table also includes check history; recheck before use.
showing 1–60 of 73 (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.
| 8382 | HTTP | 🇸🇬Singapore | Elite | – | 158 ms | 100% | ||
| 80 | HTTP | 🇸🇬Singapore | Elite | – | 164 ms | 100% | ||
| 3128 | HTTP | 🇸🇬Singapore | Transparent | – | 163 ms | 100% | ||
| 8118 | HTTP | 🇸🇬Singapore | Elite | – | 166 ms | 99% | ||
| 7777 | HTTP | 🇸🇬Singapore | Elite | – | 160 ms | 99% | ||
| 8118 | HTTP | 🇸🇬Singapore | Elite | – | 165 ms | 99% | ||
| 8080 | HTTP | 🇸🇬Singapore | Anonymous | – | 202 ms | 99% | ||
| 8080 | HTTP | 🇸🇬Singapore | Anonymous | – | 165 ms | 98% | ||
| 10290 | HTTP | 🇸🇬Singapore | Elite | – | 242 ms | 97% | ||
| 8118 | HTTP | 🇸🇬Singapore | Elite | – | 169 ms | 95% | ||
| 8080 | HTTP | 🇸🇬Singapore | Anonymous | – | 368 ms | 90% | ||
| 80 | HTTP | 🇸🇬Singapore | Elite | – | 2240 ms | 60% | ||
| 18080 | HTTP | 🇸🇬Singapore | Elite | – | 259 ms | 49% | not working last alive | |
| 3128 | HTTP | 🇸🇬Singapore | Elite | – | 158 ms | 49% | 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 → | ||||||||
| 8118 | HTTP | 🇸🇬Singapore | Elite | – | 165 ms | 49% | not working last alive | |
| 8080 | HTTP | 🇸🇬Singapore | Anonymous | – | 183 ms | 47% | not working last alive | |
| 3128 | HTTP | 🇸🇬Singapore | Transparent | – | 166 ms | 46% | not working last alive | |
| 80 | HTTP | 🇸🇬Singapore | Elite | – | 156 ms | 46% | not working last alive | |
| 8080 | HTTP | 🇸🇬Singapore | Elite | – | 154 ms | 41% | not working last alive | |
| 3128 | HTTP | 🇸🇬Singapore | Transparent | – | 1179 ms | 40% | not working last alive | |
| 12345 | HTTP | 🇸🇬Singapore | Elite | – | 4693 ms | 40% | not working last alive | |
| 3128 | HTTP | 🇸🇬Singapore | Elite | – | 154 ms | 39% | not working last alive | |
| 3128 | HTTP | 🇸🇬Singapore | Elite | – | 237 ms | 38% | not working last alive | |
| 8888 | HTTP | 🇸🇬Singapore | Transparent | – | 4676 ms | 36% | not working last alive | |
| 3128 | HTTP | 🇸🇬Singapore | Transparent | – | 246 ms | 32% | not working last alive | |
| 3128 | HTTP | 🇸🇬Singapore | Elite | – | 7266 ms | 32% | not working last alive | |
| 3128 | HTTP | 🇸🇬Singapore | Transparent | – | 1580 ms | 28% | not working last alive | |
| 3128 | HTTP | 🇸🇬Singapore | Anonymous | – | 955 ms | 27% | not working last alive | |
| 8085 | HTTP | 🇸🇬Singapore | Anonymous | – | 1077 ms | 26% | not working last alive | |
| 8080 | HTTP | 🇸🇬Singapore | Elite | – | 2472 ms | 25% | not working last alive | |
| 3128 | HTTP | 🇸🇬Singapore | Transparent | – | 163 ms | 24% | not working last alive | |
| 443 | HTTP | 🇸🇬Singapore | Elite | – | 194 ms | 22% | not working last alive | |
| 8080 | HTTP | 🇸🇬Singapore | Elite | – | 1470 ms | 22% | not working last alive | |
| 8080 | HTTP | 🇸🇬Singapore | Elite | – | 1620 ms | 21% | not working last alive | |
| 8080 | HTTP | 🇸🇬Singapore | Elite | – | 1011 ms | 20% | not working last alive | |
| 55555 | HTTP | 🇸🇬Singapore | Elite | – | 3716 ms | 19% | not working last alive | |
| 80 | HTTP | 🇸🇬Singapore | Elite | – | 7050 ms | 19% | not working last alive | |
| 80 | HTTP | 🇸🇬Singapore | Elite | – | 164 ms | 19% | not working last alive | |
| 8080 | HTTP | 🇸🇬Singapore | Elite | – | 1864 ms | 18% | not working last alive | |
| 8080 | HTTP | 🇸🇬Singapore | Elite | – | 1860 ms | 18% | not working last alive | |
| 8081 | HTTP | 🇸🇬Singapore | Elite | – | 1574 ms | 18% | not working last alive | |
| 8181 | HTTP | 🇸🇬Singapore | Anonymous | – | 6474 ms | 17% | not working last alive | |
| 8080 | HTTP | 🇸🇬Singapore | Elite | – | 991 ms | 17% | not working last alive | |
| 8080 | HTTP | 🇸🇬Singapore | Elite | – | 993 ms | 17% | not working last alive | |
| 8080 | HTTP | 🇸🇬Singapore | Elite | – | 1398 ms | 17% | not working last alive | |
| 5001 | HTTP | 🇸🇬Singapore | Elite | – | 1142 ms | 16% | not working last alive | |
| 8080 | HTTP | 🇸🇬Singapore | Elite | – | 5267 ms | 16% | not working last alive | |
| 10808 | HTTP | 🇸🇬Singapore | Elite | – | 166 ms | 15% | not working last alive | |
| 8080 | HTTP | 🇸🇬Singapore | Elite | – | 1676 ms | 14% | not working last alive | |
| 3128 | HTTP | 🇸🇬Singapore | Transparent | – | 7769 ms | 13% | not working last alive | |
| 6969 | HTTP | 🇸🇬Singapore | Transparent | – | 154 ms | 13% | not working last alive | |
| 8080 | HTTP | 🇸🇬Singapore | Elite | – | 2649 ms | 13% | not working last alive | |
| 8080 | HTTP | 🇸🇬Singapore | Elite | – | 1582 ms | 13% | not working last alive | |
| 8081 | HTTP | 🇸🇬Singapore | Elite | – | 6392 ms | 13% | not working last alive | |
| 8080 | HTTP | 🇸🇬Singapore | Elite | – | 3748 ms | 11% | not working last alive | |
| 6128 | HTTP | 🇸🇬Singapore | Transparent | – | 3001 ms | 9% | not working last alive | |
| 3129 | HTTP | 🇸🇬Singapore | Elite | – | 2510 ms | 9% | not working last alive | |
| 8081 | HTTP | 🇸🇬Singapore | Elite | – | 3618 ms | 9% | not working last alive | |
| 8080 | HTTP | 🇸🇬Singapore | Anonymous | – | 178 ms | 8% | not working last alive | |
| 3128 | HTTP | 🇸🇬Singapore | Elite | – | 8136 ms | 7% | 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 12 entries marked working. Mean recorded check success across these entries is 94%; mean recorded response time, where available, is 363 ms. By protocol: HTTP (12). By anonymity level: Elite (8), Anonymous (3), Transparent (1). The most common ports are 8118, 8080, 80. Measurements come from recorded checks, not a promise of availability. Use ⟳ to recheck before use.
This slice groups public proxy records for Singapore / 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
- free proxy list
- HTTP proxy list
- HTTP ip address
- SOCKS5 & HTTP proxies
- dedicated ip
- http proxies for android
- what is a SOCKS5 proxy
- is socks5 proxy safe
- anonymous proxies explained
- dedicated ip for scraping
- anonymous proxies by country
- fresh socks5 proxies
- dedicated ip provider
- socks5 proxies
Real search phrases this page answers — the linked ones open the page that covers them in depth.