Safety Leak test

Configuration is not evidence. The leak test asks the page.

The leak test opens the profile for real and asks its own page what a site can see: the address it reaches, what WebRTC hands out, the clock, the language and the position. Then it compares each with what the profile should show.

7checks: exit IP, WebRTC, local address, timezone, timezone vs exit, language, geolocation
4outcomes per check: pass, fail, warn, skip
A pinned profile’s actions menu in Mosaic: edit, leak test, warm up, unpin, duplicate, save as preset, move
A profile’s menu, where Run leak test sits beside warm-up, pin and the detector check.
01 How it works

Leak test, step by step

Launch for real

The profile starts in its own browser, with its proxy and fingerprint, exactly as a site would meet it.

Ask the page

A probe in the page looks up the address it reaches over HTTPS, gathers the WebRTC candidates, and reads the timezone, language and position the page is given.

Compare

Each reading is set against what the profile is meant to show. A mismatch is a fail, with the two values side by side.

02 Inside it

The smaller things it does

From the window, the companion or the API

Run it from the profile’s menu, from the companion inside its browser, or through the REST API and MCP.

A skip is not a pass

If the page never asked for a position, the geolocation row says skipped, not passed.

Limit

A clean leak test says nothing leaked on that run. It is not a verdict from any site, and it does not promise one.

Next Try it on your own accounts

Leak test is in every plan

Free holds 3 profiles and 10 profile creations, with the same engine as Pro. Pro is $49 a month for any number.