IP purity report
2604:9cc0:27:262:d41b:75c3:5ba5:8683
78/ 100
Fair
confidence: high
Usable; platforms with strict risk controls may occasionally show a CAPTCHA.
Based on signals observed from public and partner data sources at 2026-09-21 13:59 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 · Washington · Seattle
- IP type
- Hosting / data center
- Native / broadcast
- Native IP
- Network
- AS50131 Spartan Host Ltd
- Reverse DNS
- none
- Devices seen in subnet
- no data
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
Good fit
Main issue: IP type: Hosting / data center
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
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
- −25
IP type: Hosting / data center
Hosting / data center IPs are the main source of automated traffic
- −5
No rDNS record
No PTR record; IPs allocated by established carriers usually have one
- +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 3 blocklists checked (Spamhaus ZEN, blocklist.de, DroneBL).
- 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
- rdap118ms
- team-cymru63ms
- ip-api.com81ms
- proxycheck.io89ms
- abuseipdb346ms
- cloud-ranges12ms
- tor-exits12ms
- rdns719ms
- shodan-internetdb225ms
- ipwho.is77ms
- dnsbl207ms
Machine-readable versions of this report: JSON · plain text · 中文报告