EGRESS PROBE
Exit IP Lookup
This page reads the public network info your current connection presents to the outside world: exit IP, location, ISP, and proxy flags. Run a check before and after connecting to confirm your route is active.
- Exit IP
- Checking…
- Country / Region
- Checking…
- ISP / Carrier
- Checking…
- Proxy Flag
- Checking…
Lookups run through this site's own endpoint. Results display only in your current browser and nothing is saved.
What this information tells you
Exit IP is the address every site actually sees. Without an active connection, it's the public IP assigned by your local carrier. After connecting to a CKVPN route and refreshing this page, this field should switch to that route's exit address. A change between the two checks confirms your traffic is actually routed through it.
Country / Region comes from GeoIP database matching. These databases can lag behind reality, so city-level accuracy may not match the route's actual data center — that's normal. Use the country or region level as your indicator that the connection is working.
ISP / Carrier reflects who that IP block is registered to. Home broadband usually shows your local carrier; route exits are often registered to a data center or cloud provider, so seeing a data center name isn't a problem.
Proxy Flag shows whether the IP is listed in public databases as a data center or proxy exit. Most data center IPs get flagged this way, and it doesn't affect normal browsing. Some IP-sensitive services (certain streaming platforms, AI tools) may use this for region checks — if you hit restrictions, try a different route type on the nodes page.
Use this page to confirm your connection is working
- Open this page before connecting and note your exit IP and location — this is your local network baseline.
- Pick a route in your client and connect. For setup steps, see Quick Start.
- Come back to this page and click "Re-check." If the exit IP and location now match the route's region, it's working. Still seeing the baseline result? Check that your client is actually connected and system proxy is enabled.
DNS Leak Self-Check
A DNS leak means your traffic is routed through the connection, but domain lookups are still going to your local carrier's resolver. The exit IP looks fine, but the domains you visit are exposed to your local network — and services that rely on resolver location for region checks may get it wrong.
How to check:
- Check your client's DNS settings. Most clients offer a "remote resolution" option or a way to set a custom DNS server — enabling remote resolution routes domain lookups through the connection too.
- While connected, run a domain lookup from a terminal and check whether the responding server is your local carrier's address:
nslookup example.comIf the responding server is still your local carrier's resolver (often a router forwarding from 192.168.x.x, or a carrier IP range) and remote resolution isn't enabled in your client, lookups aren't going through the route. Adjust your client's DNS settings and check again.