IPure IP purity check

IP purity report

202.214.238.59

100/ 100

Excellent

confidence: high

No risk signals found in any dimension we check; the IP itself is not an obstacle.

Based on signals observed from public and partner data sources at 2026-09-23 05:57 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 · Chiyoda City
IP type
Business broadband
Native / broadcast
Native IP
Network
AS2497 IIJ Internet
Reverse DNS
none
Devices seen in subnet
4

Suitability

What it is good for

Each use case weighs the evidence differently; these are not one overall score.

AI services

ChatGPT · Claude · Gemini

98

Excellent fit

No notable obstacle found for this use case

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

95

Excellent fit

No notable obstacle found for this use case

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

100

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

100

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

100

Excellent fit

No notable obstacle found for this use case

Linked-account store closures are driven first by shared IPs, and only then by data center ranges

Email sending

SMTP · marketing email

92

Excellent fit

No notable obstacle found for this use case

Blocklists make or break deliverability, while sending from a data center IP is normal and is not penalised

Evidence

Why it got this score

  • −5

    No rDNS record

    No PTR record; IPs allocated by established carriers usually have one

  • −4

    Abuse reports (abuseipdb)

    Confidence 8%, 4 reports in the last 90 days

  • −3

    IP type: Business broadband

    Business broadband is broadly trusted, though a small share are proxy exits

  • +3

    No open ports

    Network scans have not observed any open service on this IP

  • +4

    Very low observed sharing

    Only 4 devices observed in the same subnet

  • +5

    Native IP

    Registered and used in the same country, allocated directly by a local carrier

Reputation

Blocklists and abuse history

Not listed on any of the 8 blocklists checked (Spamhaus ZEN, SpamCop, PSBL, blocklist.de, UCEPROTECT L1, s5h.net, DroneBL, SpamRats).

  • abuseipdb abuse confidence 8%, 4 reports in 90 days

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

  • rdap
    237ms
  • team-cymru
    78ms
  • ip-api.com
    109ms
  • proxycheck.io
    103ms
  • abuseipdb
    147ms
  • cloud-ranges
    7ms
  • tor-exits
    7ms
  • rdns
    17ms
  • shodan-internetdb
    173ms
  • ipwho.is
    67ms
  • dnsbl
    198ms

Machine-readable versions of this report: JSON · plain text · 中文报告