IP purity report
168.151.20.33
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-24 11:40 UTC. This describes IP-level risk only; platforms' internal risk data is not visible to us.
- VPN exit
Profile
What this IP is
- Country / region
- United States · California · Los Angeles
- IP type
- Residential
- Native / broadcast
- Native IP
- Network
- AS63150 Bage Cloud LLC
- 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
Borderline
Main issue: Known VPN exit
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: Known VPN exit
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: Known VPN exit
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: Known VPN exit
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
Good fit
Main issue: Known VPN exit
Linked-account store closures are driven first by shared IPs, and only then by data center ranges
Email sending
SMTP · marketing email
Borderline
Main issue: Known VPN exit
Blocklists make or break deliverability, while sending from a data center IP is normal and is not penalised
Evidence
Why it got this score
- −20
Known VPN exit
Only 1 data source flags it as a VPN; the evidence is limited, so it counts at half weight
- −10
1 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
- +5
Native IP
Registered and used in the same country, allocated directly by a local carrier
- +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: 22
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
- rdap101ms
- team-cymru27ms
- ip-api.com69ms
- proxycheck.io98ms
- abuseipdb169ms
- cloud-ranges5ms
- tor-exits5ms
- rdns413ms
- shodan-internetdb127ms
- ipwho.is75ms
- dnsbl198ms
Machine-readable versions of this report: JSON · plain text · 中文报告