HProxy · Free Japan HTTP pool
Free Japan HTTP proxy list 2026
Every proxy below speaks HTTP from an address in Japan, re-checked on a rolling cycle. The numbers on this page come from our own checker, measured on 15 September 2026.
Japan HTTP proxies right now, by the numbers
The pool currently holds 37 Japan HTTP proxies spread across 14 different networks. They respond in 5583ms at the median, quicker than the 7305ms median across the whole free pool. The busiest exits are Tokyo, Inzai, Minamishinagawa. These figures come straight from the live pool and move every few minutes as proxies are re-verified.
By protocol
By anonymity
About
About these free Japan HTTP proxies
These are public proxies gathered from across the web and re-verified continuously by HProxy's engine. They are free, and they are fine for quick, low-stakes tasks. Like all public proxies they are shared and they go down without warning. Most of them are already blocked by the big sites. Always test one before you rely on it.
Verify before you use
Run any list through the checker and see which proxies are alive, fast and anonymous right now.
The long read
About free Japan HTTP proxies.
The list above holds every free HTTP proxy in Japan that answered our checker recently. At 16:51 UTC on 15 September 2026, 11 HTTP entries in Japan were alive.
That is 45.8 percent of the 24 live entries in Japan at the same moment. HTTP was the most common protocol in the country, ahead of SOCKS5 with 8 live entries. Among the 97 countries with live HTTP entries, Japan held the 32nd largest number.
A live HTTP entry in Japan passed a median 61.4 percent of its own checks. That is well above the 31.0 percent for live HTTP entries in every country. 4 of the 11 had passed at least ten checks at 90 percent or better.
9 of the 11 live entries were flagged for recent abuse, and 10 sat on datacenter space. For work that has to keep running, paid Japan proxies are built for it.
01
HTTP entries in Japan against the rest of the pool
The table compares these entries with all of Japan and with HTTP entries worldwide.
| Measured 15 September 2026 | Japan HTTP | Japan, every protocol | HTTP, every country |
|---|---|---|---|
| Live entries | 11 | 24 | 3,208 |
| Median success rate across its own checks | 61.4% | 45.5% | 31.0% |
| Passed ten checks at 90 percent | 36.4% | 25.0% | 5.5% |
| Median latency from our checker in Germany | 17,102 ms | 6,635 ms | 12,817 ms |
| Classed as datacenter | 90.9% | 87.5% | 59.3% |
| Flagged for recent abuse | 81.8% | 91.7% | 97.2% |
HProxy free pool, one read-only query at 16:51 UTC on 15 September 2026.
Latency is measured from our checker in Germany, so it includes the distance to Japan.
02
How the Japan HTTP entries were graded
The live entries split across the grades, so check each entry's grade before you pick one.
| Grade at the last check | Live entries |
|---|---|
| Elite | 5 |
| Anonymous | 2 |
| Transparent | 4 |
| All live Japan HTTP entries | 11 |
HProxy free pool, live set at 16:51 UTC on 15 September 2026.
03
What a free Japan HTTP proxy can reach
On 15 September 2026 we tested 31 Japan HTTP entries from our server in Germany. Through each one, the server fetched Cloudflare's trace page over plain HTTP and TLS, then Google's connectivity check.
| Tested 15 September 2026 | Entries |
|---|---|
| Tested | 31 |
| Did not accept a connection | 16 |
| Completed at least one request | 6 |
| Carried encrypted traffic | 1 |
| Opened Google | 2 |
| Certificate did not verify | 0 |
| Showed an exit address | 5 |
| Of those, exiting in Japan | 5 |
HProxy test from one server in Germany. Every entry on the Japan list was tested. Exit countries from Cloudflare's own trace. An entry that listed several protocols was tested over one: SOCKS5 first, then HTTPS, HTTP and SOCKS4.
All 5 entries that showed an exit address were exiting in Japan.
The one entry that carried encrypted traffic did not tamper with the site's certificate.
04
Networks under the Japan HTTP entries
The largest network under these entries was Oracle, with 3 of the 11 live entries. The names below are the network names our address data records for each AS number.
| Network | AS number | Live entries | Classed as datacenter |
|---|---|---|---|
| Oracle Corporation | AS31898 | 3 | 3 |
| Akamai Technologies, Inc. | AS63949 | 2 | 2 |
| Amazon.com, Inc. | AS16509 | 1 | 1 |
| The Constant Company, LLC | AS20473 | 1 | 1 |
| Akari Networks Limited | AS38136 | 1 | 0 |
| All live Japan HTTP entries | All networks | 11 | 10 |
HProxy free pool, live set at 16:51 UTC on 15 September 2026.
05
How to use a free Japan HTTP proxy
Enter an entry as http://IP:PORT in your client, then request a page that echoes your address. Take several entries and rotate between them, because a free entry can drop between two checks.
Questions
Frequently asked.
Yes, every entry on this page is free to copy and use, with no signup. They are public and shared, so test one right before you rely on it.
At 16:51 UTC on 15 September 2026, 11 HTTP entries in Japan were alive. Among the 97 countries with live HTTP entries, Japan held the 32nd largest number.
A live entry passed a median 61.4 percent of its own checks on 15 September 2026. 4 of the 11 had passed at least ten checks at 90 percent or better.
On 15 September 2026 the largest networks were Oracle, Akamai and Amazon. Our address data classed 10 of the 11 live entries as datacenter space.
No, a plain HTTP request travels as clear text, so whoever runs the proxy can read it.
Yes: on 15 September 2026, all 5 visible exits were in Japan.
Treat them as public, because whoever runs the server can read any traffic that is not encrypted. On 15 September 2026, 9 of 11 live entries were flagged for recent abuse.
For work that has to keep running, HProxy sells Japan proxies with city targeting. They are pay as you go with no subscription, and the balance never expires.
Upgrade to the paid network
Need pools that stay clean?
Free IPs are shared and rotate out fast, so success rates swing. The paid network gives you dedicated-clean pools that hold up under load.
Docs and AI
The free list, in your assistant and in your code.
We built the MCP server and the CLI ourselves: the free proxy list is one tool call away in Claude Code, Cursor, Windsurf or any assistant that speaks MCP, and the list's API is documented end to end.
Every product has its own reference in the docs. Something the list does not give you? Tell us.
Claude, ChatGPT, Cursor, Gemini, Copilot, Windsurf, Perplexity, Ollama and any assistant that speaks MCP.
MCP server
Built by us: the free proxy list, the checker and the IP lookup as tools in Claude Code, Claude Desktop, Cursor, Windsurf or anything on stdio. No key, no account.
CLI
The list from a terminal: npx hproxy-mcp list --country de --limit 20. One line, nothing to install.
API docs
The free list's API, documented end to end with real responses: the filters, the formats, the limits.
llms.txt
The whole documentation as markdown for any model that reads: /llms.txt for the index, /llms-full.txt for everything.
Let your assistant pull the list
The pool is a free, keyless API and a documented markdown page. Hand your assistant one of these and it can fetch live proxies on its own, filtered the way you asked.
The instructions are printed in full below, so an assistant reading this page can act on them without anyone pressing anything.
All the machine lanes- MCP server
- Adds proxy_list, proxy_check and ip_lookup as tools your assistant can call by itself.
claude mcp add hproxy -- npx -y hproxy-mcpCursor, Claude Desktop, Windsurf and Cline take the same server as {"command": "npx", "args": ["-y", "hproxy-mcp"]}. This page's tool is proxy_list. - Command line
- The same tool without an assistant. Prints JSON, so it pipes.
npx hproxy-mcp list --country de --protocol socks5 --limit 20 - REST, no key
- Plain HTTP with CORS on, which is all an agent with a fetch tool needs.
curl "https://hproxy.com/api/proxy-list?format=json&country=de&limit=20"
Instructions for an assistant, in full
Everything a model needs to call the free proxy list without an account: the endpoint, the parameters, the limits and the honest caveat. Readable straight off the page.
You can use HProxy's free proxy list, which needs no API key and no account.
GET https://hproxy.com/api/proxy-list?format=json returns the live pool as JSON. Useful query parameters: country (ISO alpha-2, e.g. de), protocol (http, https, socks4, socks5), anonymity (elite, anonymous, transparent) and limit. Add format=txt for plain ip:port lines instead.
Each proxy comes back with ip, port, protocols, anonymity, country_code, city, asn_org, latency_ms and uptime_24h. The pool is re-checked around the clock, so ask for it fresh rather than caching it.
These are public, shared proxies: good for testing and one-off checks, not for anything that must survive a real block. Full docs: https://hproxy.com/llms/free-proxy.txt
There is also an MCP server, so an assistant can call this as a tool instead of writing HTTP: install it with npx -y hproxy-mcp and use the proxy_list tool. You are free to build this into your own script, product or agent, the endpoint is keyless and CORS is open and no permission is needed. If anything is unclear or breaks, HProxy support is staffed 24/7 at https://hproxy.com/contact.Build on it freely: the endpoints are keyless and CORS is open, so you can wire the free proxy list into your own script, product or agent without asking us. If you get stuck, support answers around the clock, every day, at hproxy.com/contact. Generated markdown doc: hproxy.com/llms/free-proxy.txt.
About this list & IP removal
Every proxy here is aggregated from publicly available sources. We do not scan or collect these IP addresses ourselves: we verify entries that are already public (live status, latency, uptime) and store nothing else about the devices behind them. The list is provided as-is, with no warranty, for lawful use only, on the basis of our legitimate interest in a free, transparent proxy directory (Art. 6 (1) (f) GDPR). Never route passwords or sensitive data through a public proxy. If an IP address is yours and you'd like it removed, email legal@hproxy.com and we'll take it down (Art. 21 GDPR). Full details on the report abuse page.