IP purity report
97.221.201.13
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-22 03:45 UTC. This describes IP-level risk only; platforms' internal risk data is not visible to us.
- Proxy exit
Profile
What this IP is
- Country / region
- United States · Florida · Hialeah
- IP type
- Mobile network
- Native / broadcast
- Native IP
- Network
- AS6167 Verizon Business
- Reverse DNS
- 13.sub-97-221-201.myvzw.com
- Devices seen in subnet
- 27
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: Proxy IP
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: Proxy IP
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
Good fit
Main issue: Proxy IP
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
Good fit
Main issue: Proxy IP
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: Blocklist hit: Spamhaus ZEN
Linked-account store closures are driven first by shared IPs, and only then by data center ranges
Email sending
SMTP · marketing email
Unusable
Main issue: Blocklist hit: Spamhaus ZEN
Blocklists make or break deliverability, while sending from a data center IP is normal and is not penalised
Evidence
Why it got this score
- −45
Blocklist hit: Spamhaus ZEN
SBL CSS — automatically detected spam source; PBL — range judged dynamic by Spamhaus; XBL — compromised host / open proxy
- −15
Proxy IP
Only 1 data source flags it as a proxy; the evidence is limited, so it counts at half weight
- −6
1 open ports
Open ports: 35000
- −2
Abuse reports (abuseipdb)
Confidence 4%, 1 reports in the last 90 days
- +5
IP type: Mobile network
Mobile IPs are heavily shared but are generally treated as real users
- +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: Spamhaus ZEN.
- abuseipdb abuse confidence 4%, 1 reports in 90 days
Open ports observed: 35000
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
- rdap230ms
- team-cymru88ms
- ip-api.com97ms
- proxycheck.io152ms
- abuseipdb264ms
- cloud-ranges12ms
- tor-exits12ms
- rdns376ms
- shodan-internetdb201ms
- ipwho.is291ms
- dnsbl336ms
Machine-readable versions of this report: JSON · plain text · 中文报告