IP purity report
2404:c140:2007:534e:cce8:89a5:13b0:830e
58/ 100
Suspicious
confidence: high
Mediocre reputation; not recommended for long-term use with important accounts.
Based on signals observed from public and partner data sources at 2026-09-21 16:41 UTC. This describes IP-level risk only; platforms' internal risk data is not visible to us.
Profile
What this IP is
- Country / region
- Japan · Tokyo · Tokyo
- IP type
- Hosting / data center
- Native / broadcast
- Broadcast IP
- Network
- AS138997 Eons Data Communications Limited
- Reverse DNS
- none
- Devices seen in subnet
- no data
Suitability
What it is good for
Each use case weighs the evidence differently; these are not one overall score.
AI services
ChatGPT · Claude · Gemini
Not recommended
Main issue: IP type: Hosting / data center
Least tolerant of data center and proxy exits: more likely to get degraded service, verification prompts or account limits. Spam history does not matter here
Social sign-up
X · Discord · Telegram · Reddit
Not recommended
Main issue: IP type: Hosting / data center
Sign-up is the strictest checkpoint: data center / proxy exits are more likely to be asked for phone verification or refused, and IPs with bulk-registration history are blocked far more often
Streaming / short video
TikTok · Netflix · YouTube
Not recommended
Main issue: IP type: Hosting / data center
Native IP and low sharing matter most: a broadcast IP reads as a region mismatch, and shared exits get throttled
Gaming platforms
Steam · PSN · Epic · Nintendo
Not recommended
Main issue: IP type: Hosting / data center
Region locks, regional pricing and gifting all follow the IP's location, so broadcast IPs tend to be treated as cross-region; data center exits carry a high risk of restrictions
Cross-border e-commerce
Amazon · eBay · Shopee
Not recommended
Main issue: IP type: Hosting / data center
Linked-account store closures are driven first by shared IPs, and only then by data center ranges
Email sending
SMTP · marketing email
Good fit
Main issue: IP type: Hosting / data center
Blocklists make or break deliverability, while sending from a data center IP is normal and is not penalised
Evidence
Why it got this score
- −25
IP type: Hosting / data center
Hosting / data center IPs are the main source of automated traffic
- −15
Broadcast IP
Range registered in HK but used in JP (announced across borders)
- −5
No rDNS record
No PTR record; IPs allocated by established carriers usually have one
- +3
No open ports
Network scans have not observed any open service on this IP
Reputation
Blocklists and abuse history
Not listed on any of the 3 blocklists checked (Spamhaus ZEN, blocklist.de, DroneBL).
- abuseipdb abuse confidence 0%
Limits
What an IP check cannot tell you
- Each platform's internal risk labels
- Platforms keep their own IP reputation data and ban records and do not publish them. No hit in public sources does not mean a platform has nothing on this IP.
- Whether the IP is truly exclusive
- Sharing is only the number of devices observed in the same subnet. It cannot show who else is using this exit right now, or what they are doing.
- Which accounts this IP has been tied to
- Account-to-IP links exist only inside each platform. Accounts previously banned on this IP are invisible to us.
- Device, browser and behaviour
- Risk systems look at IP + device fingerprint + behavioural rhythm together. A clean IP with an odd fingerprint or behaviour still gets blocked.
- Whether the account profile matches the IP
- When sign-up country, phone number, payment method, language or time zone disagree with the IP's location, platforms verify further. That is unrelated to IP purity.
Sources
Data sources and responses
- rdap164ms
- team-cymru69ms
- ip-api.com90ms
- proxycheck.io182ms
- abuseipdb407ms
- cloud-ranges19ms
- tor-exits19ms
- rdns1212ms
- shodan-internetdb552ms
- ipwho.is94ms
- dnsbl205ms
Machine-readable versions of this report: JSON · plain text · 中文报告