Everything about your IP in one scan: purity · type · leaks · access
Account bans? Payment declines? Endless CAPTCHAs or region blocks? Check whether your IP is “dirty” first.
🔒 Privacy-firstNo storage · no logs · no tracking · no cookies / analytics · WebRTC test runs on click and stays on your device
We don't collect, phone home, or sell your real IP. Privacy →
What “IP purity” and a risk score actually mean
When you sign up for an account, log into a marketplace, or open a streaming app, the platform doesn't just see your IP address — it runs that address through fraud and abuse engines that decide, in milliseconds, how much to trust you. “IP purity” is shorthand for the outcome of that judgment: how likely your IP is to trip a risk control before you've done anything wrong.
A risk score (0–100, higher is worse) compresses that judgment into one number. It rises when an IP looks like a proxy, VPN, Tor exit, or data-center machine; when it has a history of spam or abuse reports; or when the addresses around it are dirty. It stays low when the IP looks like an ordinary home or mobile connection with a clean record. IPOK reports the same kind of score so you can see a problem before a platform silently shadow-bans, rate-limits, or blocks you — and it tells you why the score is what it is instead of handing you a sealed verdict.
How IPOK gets to the number (the one-line version)
IPOK does not trust any single vendor. It queries up to 8 risk sources in parallel — ip-api, ipapi.is, proxycheck, AbuseIPDB, Scamalytics, StopForumSpam, IPQS, plus IPOK-DB (a self-built offline library: official Tor exits, X4BNet community VPN ranges, Spamhaus DROP, and tested open proxies, refreshed weekly) — blends their verdicts by reliability weight, and applies a few hard-signal floors: if any trustworthy source proves the IP is a Tor exit, on a major blocklist, or a confirmed proxy, the score cannot drop below that floor no matter how the averages land. That's what keeps a data-center IP from being mislabeled “pristine” just because most sources happen to give it a low number.
Every result is auditable — open “How is this score computed?” on any check and the contributing sources, weights, and triggered floors map exactly to the methodology page. Dormant or failed sources are excluded.
How to read the score tiers
A note for hosting and mobile users: a data-center IP rarely scores below the Clean band even when its reputation is otherwise clean — that's by design, because platforms treat hosting traffic with suspicion. Carrier-grade mobile NAT can read “clean” yet still get rate-limited because thousands of users share it.
FAQ
Why is my IP showing a high risk score even though I've never done anything wrong?
Risk scores are about reputation, not just your own behavior. The most common reasons: your IP sits in a data-center / hosting range (VPS, cloud server, some “residential” proxies), your VPN's exit IP is shared by many users, or your /24 neighborhood is full of flagged addresses so you get caught by guilt-by-association. Open the score breakdown and signals list on your result — IPOK names the exact reason (e.g. “hosting”, “proxy/VPN”, “on blocklist”, “dirty neighborhood”) rather than leaving you to guess.
What's the difference between a residential IP and a hosting (data-center) IP, and why does it matter?
A residential IP is assigned by a consumer ISP to a home connection — fraud systems trust it because real people live behind it. A hosting IP belongs to a data center (AWS, a VPS provider, etc.) and is treated with suspicion because bots, scrapers, and proxies run there. IPOK detects the type and reflects it in the score: hosting IPs rarely fall below the Caution band by design. If you're running a server or proxy and getting blocked, this is usually the root cause.
How is IPOK different from ping0.cc?
The core difference is explainability and source breadth. Where a single-source checker hands you one number, IPOK blends up to 8 risk sources, shows each source's verdict side by side, and exposes exactly which signals and hard-signal floors produced your score. It also maps your /24 neighbors, detects residential vs. hosting, checks AI/streaming reachability, and ships in both English and Chinese. The methodology is fully public — no black box.
Does IPOK log or store the IPs I check?
No. IPOK is built as a privacy-clean alternative — it does not record the IPs you look up. Checks are run live against risk sources and returned to you; the page is a diagnostic tool, not a logging service. Browser-side features (like consistency and leak checks) read your environment locally without sending it anywhere.
What score do I need to pass sign-ups and avoid bans?
As a rule of thumb: aim for the Clean band (under 50) for everyday sign-ups and logins, and Pristine (under 15) for anything a platform scrutinizes heavily. Caution (50–70) means expect extra verification; High risk (70+) means expect to be blocked. Scores are reference signals — different platforms weigh sources differently, so treat IPOK as an early-warning check, not an absolute guarantee.
My VPN / proxy scores badly — how do I find a cleaner IP?
Switch exit nodes and re-check until you land in the Clean band; shared VPN exits and abused proxy IPs are the usual culprits. Residential or mobile exits generally score far better than data-center ones. You can also use the /24 neighborhood map to avoid IPs in a heavily flagged block, and the side-by-side compare view to pick the cleaner of two candidate IPs before you commit.
Related checks
Free tools
Lightweight network / developer tools — all run locally in your browser.