Pick a proxy by the job it has to do
Everyday residential
Location-aware browsing
Advanced identity
Priority pools and ASN control
What teams run on Ludax
Collect
Gather public data at volume
Verify
Confirm what each market sees
Understand
Turn signals into decisions
Popular proxy locations, each with its own guide
Resources
Japanese residential proxies from $0.49/GB, 1 GB for $0.99: IPs by prefecture, city and ISP (Premium), sticky up to 1000 min, HTTP/SOCKS5. No subscription. Route each request through a home connection in the Japanese prefecture and city you choose, and read the page exactly as a local visitor sees it.
Pay per gigabyte, with no subscription. Test the prefectures and cities you need on a small plan, then scale the same parameters. Plans are valid for 30 days from activation.
# Normal plans (Residential, Residential TLS)
YOUR_PASSWORD-country-jp
YOUR_PASSWORD-country-jp-state-27
YOUR_PASSWORD-country-jp-state-13-city-tokyo
# Premium plans (Residential Premium, Premium TLS)
YOUR_PASSWORD-country-jp
YOUR_PASSWORD-country-jp-state-osaka-city-osaka
YOUR_PASSWORD-country-jp-asn-4713-os-ios
# Sticky: one Japanese exit for 30 minutes
YOUR_PASSWORD-session-jp01-time-30-country-jp-state-14-city-yokohamaEvery Ludax plan reaches Japan. Every plan goes down to the prefecture and the city. Premium plans do it on a separate, screened pool, with the prefecture and city written out in full, and add ISP (ASN) and device targeting. The TLS variant of each plan targets exactly like its normal one; it adds a real browser TLS handshake.
| Feature | Residential NORMAL | Residential TLS NORMAL | Residential Premium PREMIUM | Premium TLS PREMIUM |
|---|---|---|---|---|
| Country (JP) | Yes | Yes | Yes | Yes |
| Prefecture | 18 prefectures | 18 prefectures | 42 prefectures | 42 prefectures |
| City | 16 cities | 16 cities | 233 cities | 233 cities |
| ISP / ASN | No | No | 103 Japanese networks | 103 Japanese networks |
| Device | No | No | Windows, Android, iOS, macOS | Windows, Android, iOS, macOS |
| Rotating IPs | Every request | Every request | Every request | Every request |
| Sticky session | Up to 1000 minutes | Up to 1000 minutes | Up to 1000 minutes | Up to 1000 minutes |
| Protocols and port | HTTP/HTTPS 7777 · SOCKS5 7575 | HTTP/HTTPS 9999 | HTTP/HTTPS 8080 · SOCKS5 1080 | HTTP/HTTPS 8081 |
| Browser TLS fingerprint | No | Yes | No | Yes |
| From | $0.99 / 1 GB | $1.49 / 1 GB | $3.49 / 1 GB | $5.24 / 1 GB |
Counts are the current targeting lists; the gateway host is gw.ludaxproxy.com for every plan. Product details: Residential, Residential TLS, Residential Premium, Residential Premium TLS, or compare every product.
Each level narrows where the exit IP is. Pick the widest level that still changes the page you read: a wider level draws from more homes, a narrower one is closer to a single local visitor.
Send the prefecture’s code after the country. Normal plans list 18 prefectures. Premium plans list 42 prefectures, by full name: -state-osaka. A prefecture is enough for most regional pricing, availability and search comparisons.
-country-jp-state-27Add a city after its prefecture, written in lower case without spaces or accents. Normal plans list 16 cities across Japan. Premium plans list 233, each sent with its prefecture: -state-osaka-city-osaka.
-state-27-city-osakaPremium plans choose the home network by its ASN: 103 Japanese networks, including NTT Communications (OCN) (AS4713), KDDI (AS2516), SoftBank (AS17676), Sony Network Communications (AS2527), JCOM (AS9824). Premium combines it with a prefecture, a city and a device: -os-windows, -os-android, -os-ios or -os-macos.
-country-jp-asn-2516One location per request: a prefecture with an optional city on every plan, plus an optional ASN and device on Premium. Full syntax and order in the documentation.
Every prefecture Normal plans can target in Japan, with the number of cities listed in it. The code on each tile is the value of -state-.
Every city Normal plans list in Japan, with its prefecture. Premium plans write the prefecture and city in full (-country-jp-state-osaka-city-osaka) and can add an ASN and a device.
| City | Prefecture | Normal plans PREFECTURE + CITY |
|---|---|---|
| Fujisawa | Kanagawa | -state-14-city-fujisawa |
| Yokohama | Kanagawa | -state-14-city-yokohama |
| Osaka | Osaka | -state-27-city-osaka |
| Tarumichō | Osaka | -state-27-city-tarumicho |
| Fukuroi | Shizuoka | -state-22-city-fukuroi |
| Shizuoka | Shizuoka | -state-22-city-shizuoka |
| Machida | Tokyo | -state-13-city-machida |
| Tokyo | Tokyo | -state-13-city-tokyo |
| Nagoya | Aichi | -state-23-city-nagoya |
| Matsudo | Chiba | -state-12-city-matsudo |
| Takasaki | Gunma | -state-10-city-takasaki |
| Sapporo | Hokkaido | -state-01-city-sapporo |
| Himeji | Hyōgo | -state-28-city-himeji |
| Tsu | Mie | -state-24-city-tsu |
| Niiza | Saitama | -state-11-city-niiza |
| Yamagata | Yamagata | -state-06-city-yamagata |
Every code goes after -country-jp. The dashboard’s generator lists each prefecture’s cities and builds the string for you.
The same mechanic each time: a request that leaves from a home connection in the right prefecture and city, so the source answers as it answers a local visitor. What changes is what you read from the page.
Read listings, rankings and sellers on Japanese marketplaces as a shopper in Japan is shown them.
Market research guideTrack yen prices, points offers and stock on Japanese retailers from a Japanese home connection.
Price monitoring guideSee the Google.co.jp results, map packs and ads a searcher in Tokyo, Osaka or Nagoya is shown.
SEO monitoring guideCheck that campaigns bought for a prefecture render there, on the Japanese ISP you choose.
Ad verification guideCheck Japanese copy, yen pricing and the version of a site served to visitors in Japan.
Compare prices, assortment and availability between prefectures with one sampling method.
Market research guideCollect public Japanese pages at scale, rotating per request or holding one exit for a multi-step job.
Web scraping guideWith no session parameter, every request leaves from a new Japanese home connection inside the location you chose. Use it for independent page loads at scale.
DO -country-jp-state-27 for wide coverage, add -city- only where the page changes by city
Search, filter and paginate inside one session: the same exit for up to 1000 minutes on every plan.
DO -session-jp01-time-30 · a new session id gives a new exit
Ask the whoami endpoint through the same proxy and store its city and network with every result, so a country-level fallback never passes for a local one.
DO keep prefecture, city or ASN and run time in each row
import requests
USER, PASS = "YOUR_USERNAME", "YOUR_PASSWORD"
def jp_proxy(state, city=None, session=None):
pw = PASS
if session: pw += f"-session-{session}-time-30"
pw += f"-country-jp-state-{state}"
if city: pw += f"-city-{city}"
url = f"http://{USER}:{pw}@gw.ludaxproxy.com:7777"
return {"http": url, "https": url}
# the same page, read from three Japanese cities
for state, city in [("13", "tokyo"), ("27", "osaka"), ("23", "nagoya")]:
p = jp_proxy(state, city)
exit_ = requests.get("https://api.ludaxproxy.com/whoami", proxies=p, timeout=15).json()
page = requests.get("https://example.com/stores", proxies=p, timeout=30)
print(state, city, exit_.get("city"), len(page.content))Residential gateway gw.ludaxproxy.com:7777 (HTTP and HTTPS) or :7575 (SOCKS5). Every parameter in the documentation.
Yes, on every plan. Normal plans (Residential and Residential TLS) list 18 prefectures and 16 cities, each city sent after its prefecture: -country-jp-state-13-city-tokyo. Premium plans (Residential Premium and Residential Premium TLS) list 42 prefectures and 233 cities by full name, with an optional ISP (ASN) and device: -country-jp-state-osaka-city-osaka-os-ios.
Normal plans list 18 prefectures and 16 cities: Tokyo and Machida (Tokyo), Yokohama and Fujisawa (Kanagawa), Osaka and Tarumichō (Osaka), Nagoya (Aichi), Sapporo (Hokkaido), Himeji (Hyōgo), Shizuoka and Fukuroi (Shizuoka), Takasaki (Gunma), Niiza (Saitama), Matsudo (Chiba), Tsu (Mie) and Yamagata (Yamagata). Miyagi, Nagano, Shiga, Shimane, Hiroshima and Fukuoka are targeted at prefecture level.
On Premium plans, 103 Japanese networks can be chosen by their ASN, for example NTT Communications (OCN) (AS4713), KDDI (AS2516), SoftBank (AS17676), Sony Network Communications (AS2527), JCOM (AS9824): -country-jp-asn-4713. Normal plans choose the prefecture and the city instead.
The prefecture is its two-digit code: 13 for Tokyo, 27 for Osaka, 14 for Kanagawa, 23 for Aichi and 01 for Hokkaido. A city follows its prefecture: -country-jp-state-13-city-tokyo.
The request resolves at country level rather than failing. Check the exit with a whoami request and record the city it actually came from, so a fallback is never mistaken for a local result.
Rotate on every request, or hold one exit with a sticky session: up to 1000 minutes on every plan, Premium included.
Residential (port 7575) and Residential Premium (port 1080) accept SOCKS5 as well as HTTP and HTTPS. The TLS plans, Residential TLS and Residential Premium TLS, are HTTP and HTTPS gateways, because they rebuild the browser TLS handshake themselves.
Normal Residential covers most open pages and localized search results, with prefecture and city targeting. Residential TLS fits sources that inspect the connection or render content in JavaScript. Premium adds ISP (ASN) and device targeting on a screened pool, for sources that challenge ordinary traffic.
Buy the smallest amount of traffic, check the prefectures and cities you need, and keep the same parameters when you scale. Premium, with ISP (ASN) and device targeting on a screened pool, starts at $3.49 for 1 GB.
$0.99/ 1 GB · $0.49 / GB at 1 TB