With a rule-based proxy or VPN, different websites can see different IPs. This page asks 64 places at once, in mainland China and abroad, at AI services, over IPv4, IPv6 and WebRTC, and shows every exit your traffic takes. Run a full checkup
Because your proxy splits traffic by rules. Proxy and VPN apps with rules (Clash, Surge, Shadowrocket, sing-box and the like) pick a route by destination: sites in China go direct, AI services through one server, everything else through another. So a check that asks one site only sees one of those routes. This page asks dozens of places at once and groups the answers by network.
Through a public address Cloudflare provides. ChatGPT, Claude and many other sites sit behind Cloudflare, which answers /cdn-cgi/trace on their own domain with the IP that connected, and lets any page read it. Your browser connects to chatgpt.com as usual, through whatever route your rules pick, and reads back the IP chatgpt.com saw.
A path your proxy doesn't cover, where your real IP can slip out. WebRTC is what browsers use for video calls. It asks a STUN server for your public IP over UDP. Many proxies only carry TCP, so this UDP request leaves through your own line, and any web page can read the answer without a prompt. If a STUN server sees your local IP while websites see the proxy, this page reports a leak. To close it, turn on UDP forwarding or TUN mode in your proxy app, or limit WebRTC with a browser extension.
If your proxy only handles IPv4 but your line also has IPv6, connections over IPv6 can go around the proxy. The IPv6-only checkpoints show which exit your IPv6 traffic really takes. If it leaks, let the proxy handle IPv6 too, or turn IPv6 off on your device or router.
By who owns the IP. An IP registered to a cloud or hosting company (Amazon, Google Cloud, Alibaba, DigitalOcean…) is labeled a proxy; the first one owned by an internet provider is taken as your local line. So a residential proxy, or a VPN running on a provider's network, can't be told apart this way.
A server of 1ms.dog's own, in Tokyo. The other checkpoints change the destination; this group keeps it and changes the port and protocol: the same address over TCP on 443, 4433, 8080, 8443, 9443 and 10443, and over UDP (STUN) on 3478, 19302, 51820 and 40000. If the exit still differs, your proxy routes by port or protocol, for example it only handles TCP. The 443 check also reads the MSS (the most data one TCP packet carries): well under the usual 1460, the line probably has a tunnel such as a VPN. Some ISP tunnels and mobile networks do this too, so it is only a hint.
No. Your browser talks to each checkpoint directly; this site only serves static files and never sees your result. This site's own checkpoints (“This site” and the “1ms.dog's Tokyo server” group) see the IP and port you connect from, send them straight back to you and keep no record. Two more things are your choice: Share puts the result in the link after the #, a part that is never sent to the server when the link opens; Report a problem attaches a summary of this run, without IP addresses. Use Hide IPs before taking a screenshot.