HProxy · Free Japan pool
Free Japan proxy list 2026
Our checker keeps re-testing the Japanese entries below, and each stays listed two days after its last answer. In our test, most entries carried no traffic at all, so test one before you rely on it.
Every slice of the pool
The same live list, one thing at a time.
A page per country, protocol, anonymity grade, operator, port, network and block, each with its own count, download and API call.
Free proxies by country
24 pages
Japan proxies right now, by the numbers
The pool currently holds 500 Japan proxies spread across 21 different networks. They respond in 1893ms at the median, quicker than the 3100ms median across the whole free pool. The busiest exits are Tokyo, Osaka, Inzai. These figures come straight from the live pool and move every few minutes as proxies are re-verified.
By anonymity
About
Inside the Japanese list: what our test found
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 Proxy Checker, in the free app or online, and see which proxies are alive, fast and anonymous right now.
The long read
About free Japanese proxies.
This is our free Japanese list, limited to entries our checker reached in the past two days. Set one row in your tool: in our test, 21 of 24 working entries showed a Japanese address.
On 27 September 2026 at 16:06 UTC, our pool held 20,815 live entries, and 29 were Japanese. Every Japanese entry in rotation had been checked within the day, and 491 of 527 within the hour.
When our test began at 01:17 UTC on 28 September, 27 of the list's 314 rows were live. Most of the rest is not what it seems: 256 rows sat on 10 Amazon cloud addresses. Every address held 16 to 34 of those entries, one per port, each offered as HTTPS. Not one of the 256 carried a request to the site we named, though we tried them all.
Worse, 75 of them answered a request for Cloudflare with a certificate our server could not verify. Each one we examined carried Cloudflare's name, yet none was the certificate Cloudflare uses. A proxy that only relays traffic passes on the site's own certificate. A server that swaps in its own can read what you send, once you click past the warning.
The other 58 entries sat on 54 addresses across 18 networks, and a few of them worked well. In our test, 21 relayed a request from the address we listed, inside Japan. The median live Japanese entry replied in 2.1 seconds to our server in the United States.
Japanese entries that died lived a median of about 8 days; the rest of our pool, about 10. Before either median, we drop busy addresses and Amazon's networks, plus one June evening when our checker failed. If a job needs a Japanese address that keeps working, paid Japanese proxies are built for it.
01
Japan against the rest of the free pool
The table sets the live Japanese entries beside the rest of the pool, busy addresses aside.
| Measured 27 to 28 September 2026 | Japan | Rest of the pool |
|---|---|---|
| Live entries measured | 29 | 3,988 |
| Median success rate across its own checks | 69.1% | 34.4% |
| Passed ten checks at 90 percent | 24.1% | 8.9% |
| Median latency from our server in the United States | 2,076 ms | 6,462 ms |
| Answered in under one second | 20.7% | 6.8% |
| Median lifespan of entries that died | 181 hours | 237 hours |
| Died within a day | 27.1% | 24.6% |
| On datacenter address space | 75.9% | 22.8% |
Japanese live figures come from 16:06 UTC on 27 September. The rest column comes from 12:16 UTC on 28 September, every lifespan from 15:55. An address holding 20 or more of the entries a row counts is left out of that row. Lifespans also skip Amazon's networks and the June evening our checker marked about 128,000 entries dead.
Only 29 Japanese entries were live, so one server coming or going moves these shares. The latency was measured from the United States, and the Japanese entries still answered faster.
02
Ten addresses behind most of the list
The test took every one of the 314 Japanese entries our public list API returned at 01:17 UTC. Our server in the United States asked an echo service, through each entry, which address it saw. Each entry also had to open Cloudflare and Google, with 30 seconds allowed for every request.
| Tested at 01:17 UTC, 28 September 2026 | On 10 Amazon addresses | On 54 other addresses |
|---|---|---|
| Entries on the list | 256 | 58 |
| Passed their latest check | 0 | 27 |
| Did not accept a connection | 1 | 15 |
| Completed at least one request | 0 | 28 |
| Relayed our echo with a visible exit | 0 | 24 |
| Exited in Japan from the listed address | 0 | 21 |
| Opened Google | 0 | 13 |
| Failed a certificate check | 80 | 1 |
Every request left one HProxy server in the United States, and ip-api.com supplied the exit countries. For Google we fetched its connectivity check, www.google.com/generate_204, through each entry.
The Amazon entries are listed because they answered some of our routine checks within the last two days. Yet not one of them relayed a single request in our test.
Sixty of the 68 we probed again at 01:18 UTC completed the encrypted handshake. All 60 showed a certificate made out to www.cloudflare.com, and none was the one Cloudflare uses. Their 45 issuer names ran from Let's Encrypt and DigiCert to products such as SIMATIC WinCC. We checked ten against the real authority's own certificate, and every signature failed.
A request for a plain web page drew answers from 68, under 63 different server names. One port called itself Oracle-Application-Server-10g, another HP-ChaiServer, another Microsoft-IIS. Every reply said the same thing: Could not connect.
We cannot see who runs these ten servers. What they showed us fits a honeypot better than a proxy. NIST's glossary says a honeypot is designed to be attractive to intruders.
03
The Japanese entries that work
The working entries sit mostly on cloud servers in Tokyo. At 16:06 UTC on 27 September, Oracle held 7 of the 29 live entries and Akamai held 4. In all, 22 of the 29 were on datacenter address space.
Twenty-one of the 24 relaying entries used the address we listed, and all 21 exits were in Japan. Three exited abroad. One of them left from the listed address, which the echo placed in Bangkok. The other two came out in New York and in Colombia, from other addresses.
Through the working entries, Cloudflare answered 13 times from Tokyo and Osaka and once from Bogotá. Our list places that last entry in Tokyo.
One live entry on an Alibaba address showed a certificate for Cloudflare that was valid for two hours. Its root carried GlobalSign's name, but the real certificate of that name is signed by GlobalSign's own root.
04
How to use a free Japanese proxy
Take the address, port and protocol from one row, and set all three in your tool. Check each row's network too, because no entry on an Amazon address carried traffic in our test.
Before any real work, open a page through it that tells you your address and location. Most working Japanese entries exit from the address you copy, in Tokyo.
If your browser warns that a connection is not private, stop using that proxy and pick another.
SOCKS5 on a free entry carries your data as it is, without encryption. RFC 1928 ties any protection to the method agreed at the start of a session. An open entry agrees to no authentication, and that method protects nothing.
Rotate through a handful of entries; no single free address can be counted on to last. More than one in four Japanese entries that died had not lasted a day.
Questions
Frequently asked.
Yes, with no fee and no account. Anyone may use the same entry at the same time, so test it first.
Because most rows on that list are not working proxies at all. On 28 September 2026, ten Amazon addresses held 256 of the 314 entries, and none carried traffic.
Our server in the United States saw the live ones answer in a median 2.1 seconds. That is about seven times faster than the rest of our pool, at 14.3 seconds.
Mostly Tokyo. On 27 September 2026, 18 of the 29 live Japanese entries were in Tokyo and one in Osaka.
The working ones mostly do. On 28 September 2026, 21 of 24 relaying entries exited in Japan from the address we listed. The other three came out in Thailand, the United States and Colombia.
Assume someone is reading: the person running a server sees any traffic you send without encryption. In our test, 80 Amazon entries failed a certificate check, 75 of them for Cloudflare. Leave logins and payments out of any free entry.
Those that answered for a while and then died lasted about 8 days at the median. The rest of our pool, measured the same way, lived about 10 days. Addresses holding 20 or more such entries do not count, nor do Amazon's networks or one June evening.
HProxy's paid Japanese range covers residential, static ISP and datacenter addresses, for work that cannot stop. Residential plans can target a Japanese city, and you pay as you go. Purchased traffic has no scheduled expiry date.
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, ChatGPT, Cursor 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 and hosted at mcp.hproxy.com: the free proxy list, the checker and the IP lookup as tools in Claude, ChatGPT, Cursor, VS Code or any assistant that speaks MCP. Nothing to install, no key.
CLI
The list from a terminal: hproxy list --country DE --limit 20, from the command line of the free HProxy app.
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. Nothing to install.
claude mcp add --transport http hproxy https://mcp.hproxy.com/mcpClaude, ChatGPT, Cursor, VS Code, Windsurf or any assistant that speaks MCP: add https://mcp.hproxy.com/mcp as a remote server. This page's tool is proxy_list. - Command line
- The same tool without an assistant, from the free HProxy app's command line. Add --json for JSON.
hproxy list --country DE --protocol socks5 --limit 20Comes with the free HProxy app: hproxy.com/proxy-checker - 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: add https://mcp.hproxy.com/mcp as a remote MCP server (nothing to install, no key) and use the proxy_list tool. In Claude Code the line is `claude mcp add --transport http hproxy https://mcp.hproxy.com/mcp`. 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.