Japan: free HTTP proxies 🇯🇵
Japan HTTP: 2 public proxies marked working in this snapshot. The table also includes check history; recheck before use.
showing 1–31 of 31 (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.
| 8118 | HTTP | 🇯🇵Tokyo | Elite | – | 6124 ms | 26% | ||
| 5050 | HTTP | 🇯🇵Manila | Transparent | – | 4102 ms | 17% | ||
| 80 | HTTP | 🇯🇵Chiba | Elite | – | 245 ms | 49% | not working last alive | |
| 10081 | HTTP | 🇯🇵Tokyo | Elite | – | 6353 ms | 47% | not working last alive | |
| 3128 | HTTP | 🇯🇵Tokyo | Elite | – | 251 ms | 43% | not working last alive | |
| 1089 | HTTP | 🇯🇵Tokyo | Elite | – | 1326 ms | 41% | not working last alive | |
| 3123 | HTTP | 🇯🇵Tokyo | Transparent | – | 222 ms | 35% | not working last alive | |
| 60808 | HTTP | 🇯🇵Ishigaki | Elite | – | 5785 ms | 25% | not working last alive | |
| 3128 | HTTP | 🇯🇵Tokyo | Anonymous | – | 7280 ms | 24% | not working last alive | |
| 8080 | HTTP | 🇯🇵Utan | Anonymous | – | 4652 ms | 23% | not working last alive | |
| 7890 | HTTP | 🇯🇵Tokyo | Elite | – | 245 ms | 21% | not working last alive | |
| 8087 | HTTP | 🇯🇵Cebu City | Transparent | – | 1054 ms | 19% | not working last alive | |
| 1080 | HTTP | 🇯🇵Tokyo | Elite | – | 268 ms | 19% | not working last alive | |
| 3128 | HTTP | 🇯🇵Santa Clara | Elite | – | 5654 ms | 19% | 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 → | ||||||||
| 80 | HTTP | 🇯🇵Chiyoda City | Elite | – | 309 ms | 18% | not working last alive | |
| 8080 | HTTP | 🇯🇵Manila | Transparent | – | 3408 ms | 17% | not working last alive | |
| 1083 | HTTP | 🇯🇵Tokyo | Elite | – | 1333 ms | 17% | not working last alive | |
| 8880 | HTTP | 🇯🇵Osaka | Elite | – | 235 ms | 17% | not working last alive | |
| 3128 | HTTP | 🇯🇵Tokyo | Transparent | – | 249 ms | 16% | not working last alive | |
| 80 | HTTP | 🇯🇵Chiyoda City | Elite | – | 308 ms | 16% | not working last alive | |
| 8085 | HTTP | 🇯🇵Manila | Transparent | – | 4784 ms | 13% | not working last alive | |
| 7890 | HTTP | 🇯🇵Singapore | Elite | – | 3669 ms | 12% | not working last alive | |
| 1080 | HTTP | 🇯🇵Minamishinagawa | Elite | – | 2143 ms | 10% | not working last alive | |
| 8080 | HTTP | 🇯🇵Tokyo | Elite | – | 222 ms | 9% | not working last alive | |
| 8080 | HTTP | 🇯🇵Singapore | Elite | – | 3970 ms | 8% | not working last alive | |
| 80 | HTTP | 🇯🇵Osaka | Elite | – | 5549 ms | 6% | not working last alive | |
| 1080 | HTTP | 🇯🇵Tokyo | Elite | – | 8581 ms | 4% | not working last alive | |
| 8443 | HTTP | 🇯🇵Hong Kong | Elite | – | 973 ms | 2% | not working last alive | |
| 3128 | HTTP | 🇯🇵Tokyo | Anonymous | – | 8492 ms | 2% | not working last alive | |
| 3128 | HTTP | 🇯🇵Tokyo | Anonymous | – | 222 ms | 1% | not working last alive | |
| 3128 | HTTP | 🇯🇵Tokyo | Anonymous | – | 223 ms | 0% | 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 2 entries marked working. Mean recorded check success across these entries is 21%; mean recorded response time, where available, is 5113 ms. By protocol: HTTP (2). By anonymity level: Elite (1), Transparent (1). The most common ports are 8118, 5050. Measurements come from recorded checks, not a promise of availability. Use ⟳ to recheck before use.
This slice groups public proxy records for Japan / 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
- proxy server HTTP
- HTTP ip address
- free proxies HTTP
- HTTP proxies online
- http proxies
- public proxies settings
- anonymous proxies
- free proxy list
- SOCKS5 & HTTP proxies
- what is a SOCKS5 proxy
- working proxies for beginners
- public proxies without registration
Real search phrases this page answers — the linked ones open the page that covers them in depth.