Fix your leaks

Paste your log to begin

Run a test on the WebRTC leak test or the hardware fingerprint test, press its Copy button, paste below, and press Analyze. The log never leaves this screen.

WORKS HERE: Chrome · Edge · Firefox · Safari · Opera · Brave · Vivaldi (desktop) · Chrome on Android · every iPhone browser — anything else gets an honest “not covered yet”, never wrong instructions. Tor Browser and Mullvad Browser are read as Firefox — by their own design — and should come back green.

— visitors · — plans built, all time — one visit per person per 20 minutes; every analysis counts. This counter stores a number, nothing about you.

Live diagnostic log — how your paste was read

(analyze a log first)

Why fix it here

Your log stays on your screen. The analysis runs entirely inside your browser: the page's security policy (connect-src 'self') forbids it from talking to anyone but this site, and the only thing it ever sends is its own visit counter — a number, never a word of what you pasted. Open DevTools → Network and count for yourself.

Two lanes, both honest. Where a real Chrome fix exists you get it step-by-step — go here, click this. Where no switch exists, we say so in one sentence and hand you a verified source that explains it in depth. No false promises either way.

Paid counts too. If the right fix is a good VPN's leak protection, we say so — paid or free, a fix is a fix. We sell nothing, link to no shops, and earn nothing from any choice you make.

Verified for 2026. Every instruction was checked against today's Chrome — including the advice that went stale elsewhere. Every source link was tested live before this page shipped.

A loop, not a lecture. Fix, re-test, paste again — the meter shows what closed. Stop when you reach the maximum Chrome allows.

Questions people ask

Is my pasted log private?: Yes — and you can verify it instead of believing it. The page reads your paste locally and builds the plan on your screen. Its network policy allows exactly one destination, this site's own visit counter, which receives a number and a random browser id — never your log. Count the requests in DevTools.
Why can't everything be fixed?: Because some readings have no off-switch in Chrome — the browser simply answers. For those we tell you the truth, explain what it means, and point to browsers that were built to mask them. An honest "no switch exists" beats a fake fix.
Do the fixes cost money?: Most are free clicks inside Chrome. One class of leak (WebRTC bypassing a tunnel) is genuinely best solved by a VPN whose app has leak protection — that can be a paid product, and we say so plainly because it is the real fix. We are not affiliated with anyone and sell nothing.
Which browsers does this cover?: Desktop Chrome, Edge, Firefox, Safari, Opera, Brave and Vivaldi — plus Chrome on Android and every iPhone browser (they all run Apple’s engine). Brave hides its identity from websites, so the test pages detect it themselves and this page reads their verdict. Vivaldi hides as Chrome too — if that’s you, one click under the plan switches it. Tor Browser and Mullvad Browser (built with the Tor team) deliberately look like Firefox and are read as Firefox. Tor should come back all green with WebRTC off. Mullvad gets Tor-grade masking but keeps WebRTC on by design — so the real proof is running the WebRTC test with your VPN on and watching the two address columns match. The engine underneath is built for more; paste a log from another browser and you'll get an honest "coming later" instead of guessed instructions that might be wrong for you.
Why paste a log instead of scanning me again?: Because the log is yours. You choose what to share with this page, you can read every line of it first, and the plan is built only from what you pasted — nothing is probed behind your back.

How it works. The test pages write everything they saw into a log. This page reads the verdict lines out of that log (CHECK … [leak], [warn], [ok]), matches each finding to a playbook for your browser, and renders your plan: numbered steps with copy-ready addresses for what can be fixed, and a sourced explanation for what cannot. Built as a multi-browser engine; Chrome is the pilot. Start here: WebRTC leak test · hardware fingerprint test · what is my IP. Part of I4ROOT — trance music, 100% human-made.