Exit check
Discover every public exit IP on your network and see which exit popular sites observe.
Looking for exit IPs
| IP address | Location | ASN | Provider |
|---|
Exit seen by each site
Each site reports the visitor IP it sees
CKIPThis siteTesting
ByteDancebyte-test.comTestingNetEase127.netTesting
Cloudflare Chinawww.cloudflare-cn.comTesting
ChatGPTchatgpt.comTesting
Claudeclaude.aiTesting
Perplexitywww.perplexity.aiTesting
Grokgrok.comTesting
GitLabgitlab.comTesting
Node.jsnodejs.orgTesting
npmregistry.npmjs.orgTestingCoinbasewww.coinbase.comTesting
OKXwww.okx.comTesting
Frequently asked questions
What is an exit IP, and why might there be more than one?
An exit IP is the public source address a target service sees for a request. Your browser sends requests directly to several sites, and this page lists the distinct addresses they report. IPv4 and IPv6, different network paths, or changing exit addresses can produce multiple IPs. The list reflects this check and may not cover every exit used by your apps.
How is the exit seen by each site obtained?
Each site reports the visitor IP it sees: sites on Cloudflare return it from /cdn-cgi/trace, ByteDance and NetEase CDNs return it in response headers, and the CKIP row is the address our server sees. These are observations by the sites, not inferences. Which exit an unlisted site uses depends on your routing rules, and this page does not guess; the number of exits alone does not prove whether a proxy is in use.
Why was no exit IP found, or one missing?
Network changes, site restrictions, browser security policies, or extensions can stop a site from returning an address; that row then shows Not available. Exits already found are unaffected; check your network and browser settings, then try again. An exit that did not appear in this run may still be used by other apps.