Direct
WaitingSource IP seen from your browser
—
Browser to endpoint
Independent community demo
Anyone Privacy Lab
See which IP address a website receives from your browser and which one it receives through the Anyone network.
Compare your connection
Each selected path sends its own HTTPS request to httpbingo.org .
Checking gateway configuration
The direct test shares your public IP with httpbingo.org. Each path uses a separate random ID, and the results are paired in this tab.
Anyone via lab server
WaitingSource IP seen from the exit relay
—
Gateway through SOCKS
Anyone in the browser
UnavailableThe experimental WebAssembly path is unavailable in this session.
See how it worksResults can be exported after a measurement.
Test method
Where each request goes
httpbingo.org echoes the source IP and test URL. Each response must match the ID sent for that path.
Direct request
Your browser httpbingo.org
Your browser connects directly to the test endpoint. It sees the public IP of your current connection, which may be a VPN exit IP. The lab serves this page but does not receive the direct test request.
Anyone via lab server
Your browserLab serverAnyone exit httpbingo.org
The lab receives your browser connection and the ID for this path. Its native Anyone Rust client makes the HTTPS request. The endpoint sees the exit relay’s IP.
Anyone in the browser
ExperimentalWASM in your tabLab bridgeAnyone exit httpbingo.org
WebAssembly verifies the signed Anyone directory and builds the circuit in your tab. The lab bridge forwards encrypted traffic to the first relay. It can see your incoming IP and the first relay address. The endpoint sees the exit relay’s IP.
What does the result show?
The measurements apply to the requests made by this test. The result cards show which path made each request. Your other browser traffic continues to use its usual connection.
How should I read the timings?
Direct measures the browser request. The lab server measures its own request through SOCKS. The browser WASM card shows setup and HTTPS request times separately. Run the comparison again right away to try a warm browser session.
What data is shared?
The destination sees each request’s own test ID, source IP and standard HTTP metadata. Each path uses a separate test ID. Other signals, such as timing, can still make requests linkable. Hosting and test infrastructure may keep operational logs.