IPure IP purity check

IP purity report

154.9.224.140

57/ 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-22 11:46 UTC. This describes IP-level risk only; platforms' internal risk data is not visible to us.

Profile

What this IP is

Country / region
United States · California · Los Angeles
IP type
Business broadband
Native / broadcast
Native IP
Network
AS979 NetLab Global
Reverse DNS
none
Devices seen in subnet
15

Suitability

What it is good for

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

AI services

ChatGPT · Claude · Gemini

29

Not recommended

Main issue: Known VPN exit

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

39

Not recommended

Main issue: Known VPN exit

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

45

Not recommended

Main issue: Known VPN exit

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

49

Not recommended

Main issue: Known VPN exit

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

42

Not recommended

Main issue: Known VPN exit

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

Email sending

SMTP · marketing email

67

Borderline

Main issue: Known VPN exit

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

Evidence

Why it got this score

  • −20

    Known VPN exit

    Only 1 data source flags it as a VPN; the evidence is limited, so it counts at half weight

  • −20

    19 known vulnerabilities

    Unpatched machines are easily compromised and turned into proxy exits: CVE-2026-60000, CVE-2026-35385, CVE-2026-35386 and more

  • −6

    4 open ports

    Open ports: 11112, 22222, 25565, 55555

  • −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

  • +5

    Native IP

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

  • +6

    Spamhaus ZEN: residential range declaration

    PBL — range judged dynamic by Spamhaus

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 0%

Open ports observed: 11112, 22222, 25565, 55555

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
    1455ms
  • team-cymru
    65ms
  • ip-api.com
    70ms
  • proxycheck.io
    172ms
  • abuseipdb
    248ms
  • cloud-ranges
    9ms
  • tor-exits
    9ms
  • rdns
    586ms
  • shodan-internetdb
    205ms
  • ipwho.is
    78ms
  • dnsbl
    299ms

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