Exit IP Intelligence
CheckingLocation, ASN, network registration info, IP type, native / broadcast IP detection, and risk signals.
Location, ASN, network registration info, IP type, native / broadcast IP detection, and risk signals.
Reads the exit IP and round-trip latency seen by CDNs of Chinese providers such as NetEase, Tencent, Douyin, Weibo, Youku, and Xiaohongshu to tell whether your traffic is routed outside the mainland.
Ask multiple sites at once "what IP do you see for me?" to uncover per-site proxy routing rules.
The DNS servers that actually resolve domain names for you when you visit websites, and the countries they're in.
Whether the public address obtained via STUN bypasses the proxy, and whether your LAN address is exposed.
Compares the round trip time measured by your browser with the exit TCP round trip measured by Cloudflare to detect a relay.
Whether both protocols share the same exit, and whether the proxy handles only one of them.
Infers the real engine version from features added in each release and cross-checks it against the User-Agent.
User-Agent, Client Hints, platform, language, and HTTP request headers.
System time zone, locale settings, installed Chinese and OS-specific fonts, and voice packs.
Screen, WebGL / WebGPU renderer, Canvas and Audio fingerprints, and their stability.
webdriver, headless browsers, automation framework variables, and tampered native properties.
Availability of 24 modern browser APIs and storage quota.
About this check
IP intelligence comes from Cloudflare, Regional Internet Registries (RDAP), the Tor Project exit list, public hosting ASN lists, and ip-api.com. All browser-side checks run locally. For the full methodology, seeMethodology.
IP purity reflects how likely websites are to treat an exit IP as a "regular user." cdnping calculates it from public signals: whether it's a Tor exit, whether public intelligence databases flag it as a proxy/VPN, whether it belongs to a datacenter network, whether its ASN is on a hosting list, whether the range's registration data shows datacenter traits, and whether it's a broadcast IP. Every match lists its source and weight. No black-box scoring.
A native IP is one whose block is registered with a Regional Internet Registry (RIR) in the same country where it is actually geolocated; a broadcast IP is registered in one country and announced via BGP for use in another. Many overseas VPS "local IPs" are actually broadcast IPs, and some websites use this to identify non-local users.
A datacenter IP belongs to a cloud provider or data center rather than a residential broadband or mobile network. When a website sees a datacenter IP, it usually infers the visitor is using a VPN, proxy, or server, and tightens verification accordingly.
Even when web traffic goes through a proxy, DNS queries may still be sent to your local ISP's DNS servers. As a result, the local DNS can see which sites you visit, and the DNS server's country won't match your exit IP.
WebRTC powers real-time audio and video in the browser, and it discovers your device's public address through STUN servers. If your proxy doesn't handle UDP traffic, the address it finds may be your real public IP, which websites can read directly with a script.
Cloudflare measures the TCP round trip to your exit IP, while the browser measures the full round trip from your device to Cloudflare. If the latter is much larger than the former, there's a long path between your device and the exit IP, which is a telltale sign of a proxy or VPN relay.
Browser fingerprint, font, and hardware information is computed and displayed entirely in your browser and is never uploaded. The server only handles IP ownership lookups. Lookup results are cached at the edge for up to 24 hours, are not linked to any identity information, and no check reports are stored.
Related articles
Sites read your timezone, language and fonts, which often clash with your proxy exit IP. See what each mismatch reveals and how to check it with cdnping /ip.
Fix Claude Code connection timeouts and errors layer by layer: service status, local network, exit IP and local config. Includes a curl timing command, an error-code table and cdnping tools.
How datacenter and residential IPs differ, and the five signals sites use for IDC IP detection (ASN, RDAP netname, reverse DNS, reputation, latency), with self-check commands.
A nine-point developer network self-check: exit IP, split routing, DNS, WebRTC, IPv6, AI API latency, CDNs and status feeds, with CLI checks and cdnping tools.