IP purity report

104.194.88.240

40/ 100

High risk

confidence: high

No blocklist or abuse records, but several traits point to a datacenter / proxy exit; platforms with strict risk controls will most likely ask for extra verification.

Based on signals observed from public and partner data sources at 2026-10-26 04:09 UTC. This describes IP-level risk only; platforms' internal risk data is not visible to us.

VPN exit

Profile

What this IP is

Country / region: United States · California · Los Angeles
IP type: Hosting / data center
Native / broadcast: Broadcast IP
Network: AS25820 IT7 Networks Inc
Reverse DNS: 104.194.88.240.16clouds.com
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

Borderline

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

Borderline

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

Borderline

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

Borderline

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

Borderline

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

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

−25
IP type: Hosting / data center
Hosting / data center IPs are the main source of automated traffic
What it means
This IP sits in a hosting / datacenter range. Platforms assume real people browse from home or a phone, and machines live in datacenters.
Which uses care
Cares most: AI services, Social sign-up, Gaming platforms, Cross-border e-commerce; Barely looks at it: Email sending
Why it is weighted this way
The most basic signal there is: scrapers, bulk sign-ups and fake traffic overwhelmingly come from datacenters, so risk systems discount the whole range. It says nothing about what you did, only that you share the range.
Can it be fixed
The range type cannot be changed. What helps is not stacking other issues on top: stay off blocklists, close unneeded ports, avoid crowded exits.
−20
Known VPN exit
Only 1 data source flags it as a VPN; the evidence is limited, so it counts at half weight
What it means
Commercial risk databases mark this address as a VPN server exit. Platforms see "someone on a VPN", not you.
Which uses care
Cares most: AI services, Social sign-up, Streaming / short video, Gaming platforms, Cross-border e-commerce
Why it is weighted this way
Only one source says so, and a single database can be wrong (public DNS resolvers have been mislabeled), so it counts at half weight. If a second source follows in a few days, this item doubles.
Can it be fixed
Self-hosted proxies on VPS ranges are often labeled block-wide; changing the IP is the only fix. Commercial VPN exits are labeled by design.
−15
Broadcast IP
Range registered in CA but used in US (announced across borders)
What it means
The country the range is registered in differs from where it is actually used. Common when an international host uses a range registered in country A inside country B, or when a proxy vendor leases ranges.
Which uses care
Cares most: Streaming / short video, Gaming platforms; Barely looks at it: Email sending
Why it is weighted this way
Region-sensitive platforms (streaming, region-locked gaming) care most: they cross-check several geo databases and treat a mismatch as "wrong region". Little effect on scenarios that ignore region.
Can it be fixed
This is a registration attribute of the range and cannot be changed by the user. Platforms use different geo databases, so some may not notice at all.

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%

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
96ms
team-cymru
54ms
ip-api.com
93ms
proxycheck.io
90ms
abuseipdb
179ms
cloud-ranges
8ms
tor-exits
8ms
rdns
970ms
shodan-internetdb
timeout after 4000ms: https://internetdb.shodan.io/104.194.88.240
failed
ipwho.is
71ms
dnsbl
206ms

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