Skip to content
IPOK

Telegram IP Check: Observable Browser Exit Signals vs. Client MTProto/SOCKS5 Routing

When Telegram registration, SMS verification, or desktop/web sign-in encounters restrictions, community guides often conflate phone number ranges, client apps, and proxy IP reputation. On the network side, IPOK scopes its observation strictly to your browser's connection to ipok.io endpoints—combining independent IPv4/IPv6 probes, bounded hosting vs. residential inference, multi-source risk evidence, and on-click WebRTC/DNS checks.

Telegram's internal anti-spam and account restriction rules are not public; account status and recovery follow Telegram's official FAQ (https://telegram.org/faq_spam) and in-app notices, and IPOK cannot confirm why an account or verification attempt was restricted. The dual-stack, network classification, public risk, and WebRTC/DNS checks on this page are for local browser network self-checking only—they do not imply that Telegram uses those probe metrics as enforcement or registration criteria and never guarantee code delivery or unblock outcomes.

Your public IP
Try a sample IP
Try sample:

Step 1: Distinguish Browser Exit to ipok.io from Telegram's Built-In MTProto/SOCKS5 Proxy

Telegram Desktop and mobile apps support built-in MTProto or SOCKS5/HTTP proxy settings independent of your browser, and system proxy clients frequently route Telegram IP ranges (such as AS62041 / AS62014) through dedicated rules that differ from web traffic to ipok.io.

No web page can inspect local Telegram app proxy settings, TUN interfaces, or private system processes. Always verify both your in-app Telegram connection settings and your proxy client's live connection logs alongside the browser diagnostics on this page.

Step 2: Probe ip4.ipok.io & ip6.ipok.io Independently and Check RFC 7359 Conditions

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.

Step 3: Review Hosting vs. Residential Inference, Public Risk Feeds & On-Click WebRTC/DNS Checks

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.

To inspect IPOK's score bands, contextual hosting floor, and per-source flags, open the IP Purity Check.

FAQ

Why does Telegram still restrict my account or fail to send codes when IPOK shows a clean residential IP?

First, your browser's connection to ipok.io may not match the outbound path used by the Telegram app (especially if an in-app MTProto/SOCKS5 proxy or CIDR split-tunnel rule is active). Second, Telegram's internal anti-spam rules are not public and may involve phone number ranges, verification frequency, or client state. The dual-stack, WebRTC, DNS, and risk checks on this page are for local browser network self-checking only and do not imply that Telegram uses those probe metrics as enforcement criteria; check https://telegram.org/faq_spam and official prompts.

What if ip4.ipok.io and ip6.ipok.io show different exits, or the other stack does not respond?

Different addresses or ISP labels across the two stacks do not by themselves prove a tunnel bypass (a dual-stack tunnel or separate protected exits may also present different addresses). It may indicate single-stack coverage or different outbound policies, which you should verify against your client routing rules and connection logs—a bypass under RFC 7359 only applies once you confirm 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.

Does this page read my local Telegram proxy settings or upload WebRTC ICE candidates?

No. A browser page cannot read local Telegram app settings or proxy process configurations. The WebRTC probe runs only on click and parses ICE candidates locally in your browser without sending them to IPOK. Records on our self-hosted leak.ipok.io DNS test domain have 5 minutes of readable lifetime; expired records become unreadable, are cleared on subsequent session activity, and may remain in memory while idle. See https://ipok.io/en/privacy.

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