IPure IP purity check

IP purity report

192.197.201.114

40/ 100

High risk

confidence: high

Most platforms will add verification or block outright; consider replacing it.

Based on signals observed from public and partner data sources at 2026-09-24 18:19 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 · San Francisco
IP type
Business broadband
Native / broadcast
Native IP
Network
AS400587 Ryamer, LLC
Reverse DNS
192.197.201.114.static.ryamer.net
Devices seen in subnet
19

Suitability

What it is good for

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

AI services

ChatGPT · Claude · Gemini

32

Not recommended

Main issue: Abuse reports (abuseipdb)

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

0

Best avoided

Main issue: Abuse reports (abuseipdb)

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

31

Not recommended

Main issue: Abuse reports (abuseipdb)

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

39

Not recommended

Main issue: Abuse reports (abuseipdb)

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

16

Best avoided

Main issue: Abuse reports (abuseipdb)

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

Email sending

SMTP · marketing email

0

Best avoided

Main issue: Abuse reports (abuseipdb)

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

Evidence

Why it got this score

  • −50

    Abuse reports (abuseipdb)

    Confidence 100%, 75 reports in the last 90 days

  • −15

    Proxy IP

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

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

  • +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 100%, 75 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
    234ms
  • team-cymru
    53ms
  • ip-api.com
    40ms
  • proxycheck.io
    120ms
  • abuseipdb
    117ms
  • cloud-ranges
    7ms
  • tor-exits
    7ms
  • rdns
    665ms
  • shodan-internetdb
    105ms
  • dnsbl
    201ms

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