Your IP in one scan: type · risk evidence · leaks · region reference
Having sign-up, payment, or regional-access issues? Check IP-layer signals first; account, device, behavior, and platform policy are separate.
IP purity reflects how heavily an address is flagged across threat databases. IPOK has up to 8 integrated sources; dormant or failed sources are excluded, and each result reports the count actually returned.
🔒 Privacy-firstNo signup · no session replay · no tracking cookies · WebRTC contacts public STUN on click; ICE candidates stay on-device
Lookup caches are not tied to visitors; we do not sell query data. Privacy →
What “IP purity” and a risk score actually mean
Some platforms use an exit IP as one of many risk inputs, but IPOK cannot see their internal models. Here, “IP purity” means only observable IP-level evidence: usage type, proxy / VPN / Tor flags, abuse and blocklist records, attribution consistency, and the /24 neighborhood.
The 0–100 score summarizes those returned signals; higher means stronger adverse IP evidence observed by IPOK. It is not any platform's own score and cannot by itself predict signup, login, payment, or content access. Account state, device fingerprint, behavior, and platform policy are separate factors.
How IPOK gets to the number (the one-line version)
IPOK does not trust any single vendor. Up to 8 sources are integrated — ip-api, ipapi.is, proxycheck, AbuseIPDB, Scamalytics, StopForumSpam, currently dormant and uncalled IPQS, plus IPOK-DB. Dormant or failed sources are excluded and each result reports the actual count. Usable numeric scores are weighted, with hard-signal floors for Tor, authoritative blocklists, and confirmed proxies.
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 IP-evidence tiers
The hosting signal sets a 35-point floor, so a hosting IP can still land in Clean; mobile sharing is only a topology-based heuristic estimate. Every tier describes IP-level evidence only. Account, device, behavior, and platform policy are separate.
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; a hosting IP belongs to a data center (AWS, a VPS provider, etc.) where bots, scrapers, and proxies are also common. IPOK reflects that distinction with a 35-point hosting floor: a hosting IP can still be Clean, but hosting alone cannot qualify as Pristine. Additional proxy, abuse, or blocklist evidence is what pushes the score higher.
How is IPOK different from ping0.cc?
The core difference is explainability and source breadth. IPOK can blend up to 8 wired-in risk sources and shows which sources, signals, and hard floors actually contributed to this result. IPOK's aggregation and thresholds are public, but third-party providers still control their own algorithms and raw databases. It also maps /24 neighbors, detects residential vs. hosting, and provides official AI-service region snapshots plus known streaming-region restrictions; these are references, not live unlock tests of your current connection.
Does IPOK log or store the IPs I check?
IPOK has no accounts and does not store a per-request history tying a requester to a target IP and timestamp. It separately uses an instance-local one-minute requester-IP burst bucket, a requester-IP/UTC-day quota bucket, and a shared source-result cache keyed by target IP; no relationship between the three is stored. Normal cache entries are valid for 72 hours, with stale fallback readable for up to 7 days. Cloudflare still processes standard request metadata; WebRTC internal addresses stay local.
What score do I need to pass sign-ups and avoid bans?
IPOK has no data-supported pass line for that outcome. The score describes current IP-level evidence only; the same IP can produce different results across platforms, accounts, devices, and behavior. Use the score and source breakdown as diagnostic clues, not a pass guarantee.
My VPN / proxy scores badly — how do I find an exit with weaker adverse IP evidence?
Switch exits and compare the source breakdown, hard floors, and /24 neighborhood to identify candidates with weaker adverse evidence in IPOK's data. A residential or mobile label does not guarantee a platform outcome; validate against the target service and its rules yourself.
Related checks
Free tools
Lightweight network / developer tools — local tools stay in your browser; network lookups name the third party they contact.
+ Show all 32 tools
Mini-games
Take a break — core gameplay runs locally with no sign-up; statistics and leaderboard uploads are disclosed on each page.