IP purity report
216.231.52.80
98/ 100
Excellent
confidence: high
No risk signals found in any dimension we check; the IP itself is not an obstacle.
Based on signals observed from public and partner data sources at 2026-09-21 13:34 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 · Hawaii · Honolulu
- IP type
- Residential
- Native / broadcast
- Native IP
- Network
- AS5065 GTT Americas
- Reverse DNS
- dsl231-052-080.sea1.dsl.speakeasy.net
- Devices seen in subnet
- 46
Suitability
What it is good for
Each use case weighs the evidence differently; these are not one overall score.
AI services
ChatGPT · Claude · Gemini
Excellent fit
No notable obstacle found for this use case
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
Excellent fit
No notable obstacle found for this use case
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
Excellent fit
No notable obstacle found for this use case
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
Excellent fit
No notable obstacle found for this use case
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
Excellent fit
No notable obstacle found for this use case
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
- −15
Proxy IP
Only 1 data source flags it as a proxy; the evidence is limited, so it counts at half weight
- −6
12 open ports
Open ports: 666, 2000, 5555, 6000, 6001, 6002, 6666, 6667
- +5
Native IP
Registered and used in the same country, allocated directly by a local carrier
- +6
rDNS looks residential
Reverse hostname dsl231-052-080.sea1.dsl.speakeasy.net matches residential broadband naming
- +8
IP type: Residential
Residential broadband is the IP type risk systems trust most
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: 666, 2000, 5555, 6000, 6001, 6002, 6666, 6667, 7778, 8889, 9100, 9527
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
- rdap305ms
- team-cymru122ms
- ip-api.com136ms
- proxycheck.io210ms
- abuseipdb195ms
- cloud-ranges22ms
- tor-exits22ms
- rdns558ms
- shodan-internetdb209ms
- ipwho.is113ms
- dnsbl320ms
Machine-readable versions of this report: JSON · plain text · 中文报告