Outbound IP detection
See where your traffic exits when you visit different websites.
Start sends direct, cookie-free requests to the listed destinations. IP location details use IPWhois. Privacy policy
Ready to check your exits
Run one check to compare the addresses these websites see.
IPv4 and IPv6 are compared separately. Results cover only the listed browser connections.
Website exits
| Website | Exit IP | Location | HTTP time | Status |
|---|---|---|---|---|
NetEasenosdn.127.net | — | — | — | Not tested yet |
ByteDanceperfops.byte-test.com | — | — | — | Not tested yet |
Cloudflare Chinawww.cloudflare-cn.com | — | — | — | Not tested yet |
ChatGPTchatgpt.com | — | — | — | Not tested yet |
Claudeclaude.ai | — | — | — | Not tested yet |
Cloudflarecloudflare.com | — | — | — | Not tested yet |
GitLabgitlab.com | — | — | — | Not tested yet |
Perplexitywww.perplexity.ai | — | — | — | Not tested yet |
ipify · IPv4api.ipify.org | — | — | — | Not tested yet |
A missing IP does not prove a site is blocked. HTTP time is not ping.
Check a little further
Frequently asked questions about your IP
Why do different websites see different IPs?
VPN routing, split tunneling, privacy relays and the selected IP version can change the address a website sees. This test sends requests from your browser to each named endpoint; the Domestic category describes the target, not a verified direct route. IPv4 and IPv6 are compared separately. Check the returned addresses against the routing rules you intended to use.
Does a different exit mean an IP leak?
A different exit alone does not establish a leak. Multiple exits may be intentional, and matching exits only describe the connections tested here. DNS resolvers and WebRTC candidates use different mechanisms and are checked separately. Missing results can also come from cross-origin restrictions, filtering, rate limits or a changed endpoint. Retry the affected target or use the related tools to gather more evidence.