Instagram IP Check: Separate Account Action Blocks from Browser Exit Signals

An external checker page can only observe the network connection your browser makes to that checker. Proxy clients and anti-detect browsers frequently apply per-domain or per-app split-tunnel rules where instagram.com, graph.instagram.com, or mobile app traffic may follow a different outbound policy than ipok.io.

Furthermore, no web page can inspect local proxy client configurations, TUN interfaces, or mobile OS process rules. Always pair the browser diagnostics on this page with your proxy client's live connection logs for Instagram domains before switching IPs.

Meta services support IPv6 widely. On dual-stack mobile or broadband networks, if a proxy profile binds only IPv4, dual-stack requests may still exit over native IPv6. IPOK's main card and dual-stack card independently query ip4.ipok.io and ip6.ipok.io to echo each stack's exit IP (without creating an application-level v4/v6 pairing record).

When both IPv4 and IPv6 exits respond, dual-stack reachability by itself is not a leak, and different addresses or ISP labels across the two stacks do not by themselves prove a tunnel bypass. IPOK references RFC 7359 dual-stack tunnel traffic-protection considerations so you can verify against your client routing rules and connection logs whether the other stack left your intended tunnel and exited directly 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.

IPOK combines public ASN/BGP declarations and upstream metadata (such as ipapi.is company.type, asn.type, and is_datacenter) for bounded hosting (35-point contextual floor) vs. residential/ISP inference, and compares GeoIP country (geo.countryCode) with registration country (rdap.country ?? intel.asn.country) for native vs. broadcast clues (see https://ipok.io/en/t/datacenter-or-residential and https://ipok.io/en/t/native-ip). This is heuristic inference, not 100% absolute identification.

Across up to 10 registered risk sources, IPOK shows AbuseIPDB report counts and confidence when returned, while Scamalytics is attempted on explicit IP lookups when the shared cache misses and quota permits (or under narrow residential top-up rules). EvidenceSummary.confidence (and directSources) indicates only whether direct risk flags (Tor 90, blocklists 70, proxy/VPN 65, abuser 55) came from a single source or multiple sources (collection independence unverified). Pair this with the on-click WebRTC probe (contacting Google / Cloudflare public STUN with local ICE parsing and no candidate upload to IPOK) and leak.ipok.io DNS resolver exit check (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, not a DNS pollution test); see https://ipok.io/en/privacy.