IPPure Alternative: Verify Your Browser Exit with Dual-Stack Probes & Multi-Source Evidence

Seeing different purity or risk scores for the same IP across checker sites is common because each tool uses different upstream feeds, network-type heuristics, and weighting rules. If you want an IPPure alternative or a transparent second opinion, IPOK checks IP purity, risk score, hosting vs. residential inference, and native vs. broadcast clues across up to 10 registered risk sources side by side.

This page describes IPOK's observable diagnostics and boundaries without making unverified claims about other tools' unexpanded subpages, asynchronous fields, or backend retention. Any checker's score reflects public network signals only and never replaces a target platform's internal risk decision.

Your public IP

Try a sample IP

Try sample:

Why Scores Differ Across Checkers: Single/Multi-Source Evidence vs. Type Inference

IPOK integrates up to 10 registered risk sources (IPQS is currently dormant; Scamalytics is attempted on explicit IP lookups when the shared cache misses and quota permits, or under narrow residential top-up rules; actual returned rows depend on query policy, address-family support, shared cache, and upstream quota/availability) and displays returned third-party metrics such as AbuseIPDB report counts and confidence directly.

Instead of hiding everything behind one opaque percentage, IPOK separates direct evidence floors—Tor (90), blocklists (70), proxy/VPN (65), and abuser (55)—from contextual hosting (35) and /24 neighborhood density (40 or 50) floors. EvidenceSummary.confidence (alongside directSources) measures only whether direct risk flags come from a single source or multiple sources (collection independence unverified), excluding bounded ASN/BGP hosting vs. residential inference and making no promise of uniform confidence or zero false positives. See https://ipok.io/en/t/ip-purity.

Verify Which Exit Your Browser Actually Uses: ip4.ipok.io & ip6.ipok.io

Before comparing scores across sites, confirm which exit address your browser actually presents. IPOK's main card and dual-stack card independently query ip4.ipok.io and ip6.ipok.io to echo each protocol stack's exit IP (without creating an application-level v4/v6 pairing record).

When both IPv4 and IPv6 exits are reachable, dual-stack reachability by itself is not a leak, and IPOK references RFC 7359 dual-stack tunnel traffic-protection considerations so you can verify whether your proxy covers only one stack while the other exits via your local ISP. If the other stack times out or does not respond, that does not prove IPv6 is disabled or absent, nor does it prove safety or absence of a leak.

On-Click WebRTC, Self-Hosted DNS Exit Observation & Privacy Boundaries

IPOK's WebRTC probe runs only when clicked, contacting Google / Cloudflare public STUN and parsing ICE candidates locally in the browser without sending them to IPOK. The DNS check prefers IPOK's self-hosted authoritative domain leak.ipok.io to observe the recursive resolver exit IP that reaches our authoritative server (5 minutes of readable lifetime; expired records become unreadable, are cleared on subsequent session activity, and may remain in memory while idle; falling back to bash.ws only if initial token issuance fails, this compares recursive resolver exits and is not a DNS pollution test).

Remember the observation boundary: IPOK only observes your browser's connection to ipok.io nodes. Proxy clients may apply different split-tunnel rules to different domains, and IPOK cannot read local client process configurations. IPOK builds no account profile and has no session replay or tracking cookie; operational logs, quotas, and caches are disclosed at https://ipok.io/en/privacy.

To review IPOK's score floors, single/multi-source direct evidence rules, and per-source flags, open the IP Purity Check.

FAQ

Can IPOK be used as an IPPure alternative or cross-check tool?

Yes. IPOK lists returned verdicts from up to 10 registered risk sources side by side with public floor rules, dual-stack echo endpoints, and on-click WebRTC/DNS checks so you can see which specific feed or contextual floor raised a score.

Why does IPOK separate direct risk evidence from hosting/residential inference?

Hosting vs. residential classification is a bounded inference from public ASN/BGP and upstream metadata (carrying a 35-point contextual floor for hosting), whereas blocklist, proxy, or abuse flags are direct risk evidence. Separating them—and scoping EvidenceSummary.confidence strictly to direct evidence—prevents confusing a clean cloud VM with a blocklisted IP.

Does a clean score on any IP checker guarantee my account won't be restricted?

No. IP checkers only observe public network reputation and your browser's connection to the checker itself; they cannot see a target platform's internal risk engine or verify how your proxy client routes traffic to other domains.

Related checks

IP speed test · proxy node bandwidth

ipinfo.io Alternative: Geolocation, IP Risk & Purity

proxycheck.io Alternative: Multi-Source Proxy Detection

ping0.cc Alternative: Multi-Source IP Purity & ASN Check Compared