Japanese residential IPs
Real Japanese home IPs, not datacentre ranges
Every IP comes from an actual household fibre line in Japan on NTT/OCN. Your traffic looks exactly like a person browsing from their living room in Chiba, because that is where it leaves the network.
Why it matters
Datacentre proxies get blocked. Household lines do not.
Anti-fraud systems classify IP addresses by the network that owns them. A datacentre range is flagged in seconds. A residential fibre line shared with millions of ordinary subscribers is not.
Genuine household lines
Each endpoint is an Android device plugged in at a real home in Japan, connected over that household's own fibre line. The exit IP belongs to a consumer ISP, not to us.
Sticky by default
Your IP stays the same for the whole subscription. Essential for account management, ticketing and anything that treats an IP change as suspicious.
SOCKS5 and HTTP
One endpoint, both protocols, on the same port. Works with curl, Python, Node.js, Puppeteer, Playwright, Scrapy and every standard proxy client.
DNS resolved in Japan
Hostnames are resolved on our Japanese servers, so DNS and exit IP stay in the same country and your requests stay consistent.
Abuse filtered at the gateway
SMTP ports are blocked and every session is logged. That keeps the IP pool clean, which is why our addresses stay unlisted on blocklists.
Live usage metering
Bandwidth is counted per session and shown in your dashboard. No surprise overage, no guessing what you have used.
How it works
Three steps, about two minutes
Pick a plan
Shared pool if you need bandwidth, a dedicated IP if you need the same address every time.
Pay
Japanese bank transfer or cryptocurrency. Your credentials appear the moment payment clears.
Point your client at us
One line of configuration. Nothing to install, nothing to maintain.
Works with what you already use
Standard proxy protocols. No SDK, no wrapper library, no vendor lock-in.
Docs →# curl
curl -x socks5h://user:pass@keironet.com:80 https://ipinfo.io/json
# Python
import requests
p = {"https": "socks5h://user:pass@keironet.com:80"}
requests.get("https://ipinfo.io/json", proxies=p)
# Puppeteer
puppeteer.launch({ args: ["--proxy-server=http://keironet.com:80"] })Pricing
Straightforward pricing in Japanese yen
No setup fee, no contract, no automatic renewal. Prices include Japanese consumption tax.
Trial · 5 GB
100 JPY per GB · No expiry
- Traffic never expires — use it whenever you want
- Japanese residential IPs, NTT/OCN
- SOCKS5 and HTTP, same endpoint
- Automatic failover between devices
50 GB
40 JPY per GB · No expiry
- Traffic never expires — use it whenever you want
- Japanese residential IPs, NTT/OCN
- SOCKS5 and HTTP, same endpoint
- Automatic failover between devices
200 GB
30 JPY per GB · No expiry
- Traffic never expires — use it whenever you want
- Japanese residential IPs, NTT/OCN
- SOCKS5 and HTTP, same endpoint
- Automatic failover between devices
Dedicated Japanese IP · 30 days
- One Japanese residential IP, yours alone
- Unlimited bandwidth
- IP never changes during the term
- SOCKS5 and HTTP
Need more than 200GB or a block of dedicated IPs? Contact us for volume pricing.
Use cases
What people use Japanese residential IPs for
Ad verification
Confirm your campaigns render correctly to real users in Japan instead of to a datacentre that advertisers geo-block.
Price monitoring
Japanese retailers show different prices and stock levels to domestic visitors. Datacentre IPs see the wrong catalogue.
Localisation QA
Test how your app behaves for a Japanese user, including region-locked content and payment flows.
Market research
Collect public Japanese market data at reasonable volume without triggering the blocks that datacentre ranges attract.
FAQ