IP purity report
168.222.0.107
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-23 05:07 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 · Utah · Salt Lake City
- IP type
- Business broadband
- Native / broadcast
- Broadcast IP
- Network
- AS205548 Zouter Limited
- Reverse DNS
- none
- Devices seen in subnet
- 13
Suitability
What it is good for
Each use case weighs the evidence differently; these are not one overall score.
AI services
ChatGPT · Claude · Gemini
Not recommended
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
Not recommended
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
Best avoided
Main issue: Broadcast 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
Not recommended
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
Not recommended
Main issue: Proxy IP
Linked-account store closures are driven first by shared IPs, and only then by data center ranges
Email sending
SMTP · marketing email
Not recommended
Main issue: Blocklist hit: s5h.net
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
- −15
Broadcast IP
Range registered in GB but used in US (announced across borders)
- −12
Blocklist hit: s5h.net
Listed by s5h.net
- −10
2 open ports
Includes admin ports 22: clear evidence of a server rather than home broadband
- −5
No rDNS record
No PTR record; IPs allocated by established carriers usually have one
- −3
IP type: Business broadband
Business broadband is broadly trusted, though a small share are proxy exits
Reputation
Blocklists and abuse history
Listed on 1 of 7 blocklists checked: s5h.net. 1 list(s) could not be queried this time.
- abuseipdb abuse confidence 0%, 7 reports in 90 days
Open ports observed: 22, 80
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
- rdap873ms
- team-cymru110ms
- ip-api.com86ms
- proxycheck.io143ms
- abuseipdb247ms
- cloud-ranges9ms
- tor-exits9ms
- rdns402ms
- shodan-internetdb211ms
- ipwho.is156ms
- dnsbl847ms
Machine-readable versions of this report: JSON · plain text · 中文报告