IP purity report
82.26.72.131
73/ 100
Fair
confidence: high
Usable; platforms with strict risk controls may occasionally show a CAPTCHA.
Based on signals observed from public and partner data sources at 2026-09-25 07:49 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
- Business broadband
- Native / broadcast
- Native IP
- Network
- AS36530 IDC Cube
- Reverse DNS
- none
- Devices seen in subnet
- 39
Suitability
What it is good for
Each use case weighs the evidence differently; these are not one overall score.
AI services
ChatGPT · Claude · Gemini
Good fit
Main issue: 1 open ports
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
Good fit
Main issue: 1 open ports
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
Excellent fit
No notable obstacle found for this use case
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
Excellent fit
No notable obstacle found for this use case
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
Good fit
Main issue: 1 open ports
Linked-account store closures are driven first by shared IPs, and only then by data center ranges
Email sending
SMTP · marketing email
Borderline
Main issue: Blocklist hit: DroneBL
Blocklists make or break deliverability, while sending from a data center IP is normal and is not penalised
Evidence
Why it got this score
- −12
Blocklist hit: DroneBL
Listed by DroneBL
- −10
1 open ports
Includes admin ports 22: clear evidence of a server rather than home broadband
- −5
No rDNS record
No PTR record; IPs allocated by established carriers usually have one
- −3
IP type: Business broadband
Business broadband is broadly trusted, though a small share are proxy exits
- −2
Abuse reports (abuseipdb)
Confidence 4%, 1 reports in the last 90 days
- +5
Native IP
Registered and used in the same country, allocated directly by a local carrier
Reputation
Blocklists and abuse history
Listed on 1 of 8 blocklists checked: DroneBL.
- abuseipdb abuse confidence 4%, 1 reports in 90 days
Open ports observed: 22
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
- rdap689ms
- team-cymru78ms
- ip-api.com78ms
- proxycheck.io155ms
- abuseipdb156ms
- cloud-ranges13ms
- tor-exits13ms
- rdns169ms
- shodan-internetdb185ms
- ipwho.is95ms
- dnsbl278ms
Machine-readable versions of this report: JSON · plain text · 中文报告