Browse protected.
Consistent inside and out.
A Chrome extension that closes the leaks in your browser, so the language, time zone and network traits websites see match your proxy exit.
Protected Out of the Box
Works on its own, no setup.
Works even without Nexa: install it and these protections are on by default.
No local probing
Stops public websites from scanning your computer's ports and LAN addresses, for example to detect a proxy client running; opening your own router page is unaffected.
WebRTC leak protection
Stops websites from getting your real address over non-proxied UDP, and notices if another extension takes over control.
Block page geolocation
Denies websites your precise location by default, with exceptions for sites you trust.
Block third-party cookies
Stops cross-site tracking. When a page embeds login, payment or captcha components, the popup tells you, and one click allows the site if something breaks.
Ad profiling off
Turns off Topics, FLEDGE, ad measurement and network prediction.
No experiment ID
Stops sending the X-Client-Data experiment ID to Google sites.
Language header alignment
Optional. Makes Accept-Language match your target region; targets cover 250 countries and regions.
Clear this site's data
From the popup, clear the current site's cookies and local storage in one go, so once you disconnect it can't link your proxy IP to your real one.
Desktop Sync
Your desktop moves, your browser follows.
Once linked to the Nexa desktop app over the local bridge, your browser adjusts to your exit automatically.
Follows your exit
When Nexa's exit region changes, the consistency target follows; if rules send the browser to another exit, the browser's real exit is what counts.
Adaptive WebRTC
In system proxy mode, direct UDP is blocked; in TUN mode, WebRTC may leave through the virtual adapter, so video calls work as usual.
One-click time zone alignment
Click “Align” and Nexa adjusts the system time zone for now, restoring it when you disconnect; no injected scripts faking the browser clock.
Clear out before disconnecting
Before you disconnect Nexa, proxied tabs close first so they can't reconnect with your real IP. Only page host names are used, and they're never stored.
No false alarms on reconnect
While Nexa reconnects and the kill switch holds traffic, it shows “Waiting to recover, direct access blocked” instead of an error.
One place to manage
While connected, the shared switches are managed by the desktop app, so the two never fight.
Request details (optional)
Turned on from Nexa's Connections page, Guard hands Nexa the requests your browser makes (address without parameters, status code or error, timing) so each lines up with the connection that carried it. Off by default, in memory only, and it stops when the page closes or the switch is off.
Environment Check
Your exposure at a glance.
See in one page what your browser is exposing right now and where it doesn't match your exit.
One-page summary
Nexa connection, Chrome protection and environment consistency, with all 13 results listed (match / differs / not applied).
Browser exposure
Common fingerprint traits such as UA, platform, language, screen, hardware and cookies; checked, never faked. It also flags APIs rewritten by other extensions, automation traces, and a UA, platform and graphics card that contradict each other.
Current page check
Reads the language and time zone the page actually sees, compares them with your target and suggests a region.
Diagnostic report
Creates a local report you can copy and an anonymous snapshot ID; nothing is uploaded automatically.
External deep checks
Jump to Ping0, IPCheck.ing, BrowserScan, Pixelscan, IPhey and Whoer, opened only when you click.
Continuous watch
Every 5 minutes it checks the policies Chrome actually applies, and shows problems on the extension badge.
Privacy Boundaries
Clear about what we do, and what we don't.
Everything happens on your computer, and what we can't do is written here too.
What we do
- All local: no telemetry server; no browsing history, page content, IP or fingerprint is uploaded.
- Bridge stays local: no network ports; only connection status, exit region and page host names are shared. Request details exist only once you turn them on, and only in memory on this computer.
- All code included: all code is packaged in the extension, and no remote scripts are loaded.
What we can't do
- The extension can't change your exit IP, DNS, IPv6 routes, TLS fingerprint, IP reputation or account history; those depend on the desktop app and your nodes
- It doesn't fake Canvas, WebGL or other fingerprints, and it doesn't promise anonymity
- We suggest not installing several random-fingerprint extensions at once
How to install
- Comes with the desktop app, no separate download
- Turn on developer mode on the browser's extensions page and load it once; it reloads itself whenever Nexa updates
- Works with Chrome and Chromium-based browsers; Edge can install it, but some browser policies only take effect in Chrome