Skip to content
IPOK

E-Commerce Anti-Association IP Check: Verifiable Exit & Leak Diagnostics

When configuring anti-detect browser profiles or static residential proxies for multi-store e-commerce operations, sellers need verifiable evidence of what the browser actually exposes. IPOK scopes its observation strictly to your browser's connection to ipok.io endpoints—combining independent IPv4/IPv6 single-stack probes, verdicts from up to 10 registered risk sources, on-click WebRTC candidate parsing, and DNS resolver exit checks.

Marketplaces such as Amazon, Etsy, eBay, and TikTok Shop evaluate account linkage across registration records, payment instruments, device parameters, behavioral patterns, and network signals. IPOK's classifications and scores are network-layer diagnostic clues only; they do not reflect internal platform rules or guarantee account safety.

Your public IP
Try a sample IP
Try sample:

Datacenter vs. Residential/ISP Inference & Direct Evidence Confidence

Distinguishing cloud hosting from residential ISP connections is a baseline check for store proxies. IPOK combines public ASN/BGP declarations with upstream metadata (such as ipapi.is company.type, asn.type, and is_datacenter fields) for bounded network-type inference—flagging mixed ISP/hosting metadata as dual_isp and applying a 35-point contextual floor to hosting usage (see https://ipok.io/en/t/datacenter-or-residential). Network-type inference is heuristic and does not guarantee 100% detection of disguised proxies.

For risk scoring, IPOK separates direct evidence floors—Tor (90), blocklists (70), proxy/VPN flags (65), and abuse reports (55)—from contextual hosting (35) and /24 neighborhood density (40 or 50) floors. EvidenceSummary.confidence (and directSources count) measures only single-source vs. multi-source support for direct risk floors (with upstream collection independence unverified). AbuseIPDB report counts and confidence are shown when returned; Scamalytics is attempted on explicit IP lookups when the shared cache misses and quota permits, or under narrow residential top-up rules.

Dual-Stack Exit Probes: ip4.ipok.io, ip6.ipok.io & RFC 7359 Considerations

Many proxy profiles bind only an IPv4 endpoint while leaving the host machine's native IPv6 stack active. IPOK's main card automatically probes the other stack after self-check, and the dual-stack card below independently queries ip4.ipok.io and ip6.ipok.io on click (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, but 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 directly via your local ISP. Conversely, 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. IPOK does not inspect local client routing tables or attribute split-tunnel paths automatically.

On-Click WebRTC, DNS Resolver Exit Observation & Client Split-Tunnel Boundaries

Below the main card, the WebRTC test runs strictly on click: your browser queries Google / Cloudflare public STUN servers and parses ICE candidates locally without sending them to IPOK. The DNS test prefers IPOK's self-hosted authoritative domain leak.ipok.io to observe which recursive resolver exit IP 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 observes recursive resolver exits and is not a DNS pollution test).

Keep client split-tunnel boundaries in mind: a proxy client or anti-detect profile may apply different routing rules to ipok.io than to seller portals, and a web page cannot read private 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 inspect how IPOK distinguishes hosting from residential ISP and dual_isp metadata, open the Datacenter or Residential IP check.

FAQ

Does a low-risk residential result on IPOK guarantee my e-commerce store won't be linked or suspended?

No. E-commerce platforms evaluate business registration, payout accounts, browser/device parameters, catalog compliance, and account behavior alongside network signals. IPOK provides public IP reputation snapshots and browser connection checks; it cannot see platform rules or guarantee anti-association outcomes.

Why does IPOK reference RFC 7359 when both stacks respond, and does a single-stack timeout prove IPv6 is off?

Under RFC 7359 dual-stack tunnel traffic-protection considerations, dual-stack reachability is normal on dual-stack networks/tunnels and is not itself a leak, but a bypass occurs if your proxy covers one stack while the other exits via your local ISP. If the other stack does not respond or times out, that does not prove IPv6 is disabled or absent, nor does it prove safety.

Why is Scamalytics omitted on a self-check, and what does EvidenceSummary.confidence mean?

Scamalytics is attempted on explicit IP lookups when the shared cache misses and quota permits (or under narrow residential top-up rules), not on default self-checks. EvidenceSummary.confidence indicates whether direct risk floors came from a single source or multiple sources (collection independence unverified); see https://ipok.io/en/t/ip-purity.

Related checks

IP speed test · proxy node bandwidth
IP Purity Check — Multi-Source Risk Score & Abuse Evidence
Native IP Check — Native IP vs Broadcast IP
IP fraud score check — every source's verdict shown
ChatGPT Degraded or IP Blocked? Check IP-Side & Degrade Clues
WebRTC Leak Test — Check Browser STUN & Real IP Exposure
Datacenter or Residential IP Checker — Multi-Source ASN & ISP Audit