Documentation
Environment and leak checks
What the four Start stages check, and how the nine-layer leak verdict works.
The four stages of a Start
| Stage | What happens |
|---|---|
| Route | Turns on Strict Mode and builds the chain to the Static Residential IP. |
| Check | Scans the computer for mismatches and risky settings. |
| Network | Turns on the system firewall with the tunnel held, then measures the Static Residential IP, its country and network, DNS and WebRTC. |
| Verify | Checks that the firewall rules are loaded and that a direct connection outside the tunnel is blocked, then releases traffic only when the measured egress is the selected Static Residential IP in a confirmed country. |
Results from all four stages are kept, so you can open any stage afterwards and see its items.
What the check stage looks at
- System time zone and offset, compared with the Static Residential IP region
- System and browser language and locale
- IPv4 address, location and network of the Static Residential IP
- WebRTC candidates and any public IP they expose
- DNS mode, DNS bypass and the region DNS resolves through
- Proxy environment variables, and the settings Strict Mode relies on
- Other proxy apps running at the same time
- Local IPv6
- Hints of a virtual machine or remote desktop
- Claude Code privacy switches and reachability
Some items have a one-click fix you review before it runs: turning on Strict Mode, turning IPv6 off, DNS and LLMNR policy, and setting the time zone (and on Windows the system language) to match the Static Residential IP.
Leak verification
The leak verdict checks nine layers on their own: takeover, route, firewall, a bypass drill, IPv4 Static Residential IP (SIP), IPv6, DNS, WebRTC and UDP. Each is reported as pass, warning or fail, and the whole verdict can be exported as an HTML report.
The bypass drill and firewall layers need the kill switch, which is available on macOS and Windows.
Network diagnostics
- Every hop of the proxy chain is tested; by default the chain is re-tested every 10 seconds and a failing front node is replaced without restarting the core.
- The IP risk check gives a purity estimate. It is a local estimate, not a guarantee.
- Safe cleanup flushes the system DNS cache and the core’s DNS cache and fake-IP mappings.
These checks need a signed-in, approved account. Checks run on Windows and macOS.