What Reach hides, and what it doesn't
Most products like this one only tell you what they protect. This page also tells you what they can't — including ours — because the gap between the two is where people get caught, and because you can't make a sensible decision without it.
Everything here was checked against the shipping build, not assumed.
The one thing to understand first
Reach only hides traffic it is actually carrying.
By default Reach is a selective tunnel, not a blanket one. It carries:
- traffic from browsers you've switched on, and
- destinations your rules match, when per-app routing is on.
Everything else leaves your machine the way it always did, from your real address. That's deliberate — it's why your bank, your printer and your work VPN keep working — but it means "I have Reach installed" is not the same as "my IP is hidden."
If you want everything covered, you have to say so: turn on per-app routing for the apps that matter, and turn on Route everything through Reach if you're sharing Reach over Wi-Fi to a device that can't run rules of its own.
The tray tells you which of these is in effect. When nothing is routed, the Wi-Fi sharing panel says so in as many words: "Guests appear from THIS machine — no destinations route through Reach yet." Believe it over any assumption.
What Reach does hide, reliably
Your IP address from the websites and services you connect to through it. They see
the gateway's address, or your chosen exit's. We checked the whole path: the gateway
strips every header that could carry your real address — X-Forwarded-For,
X-Real-IP, True-Client-IP, CF-Connecting-IP, CF-IPCountry, Forwarded, Via —
before the request goes upstream. The tunnel path forwards raw bytes and adds nothing at
all.
Your DNS lookups from your local network, for names that are routed. The gateway resolves them, not your ISP's resolver.
Which country you appear to be in, for routed traffic. That's the whole point of the gateway picker and of exit nodes.
What Reach cannot hide — ever
Anything, if the other side runs code on your device
If you install someone's app and it runs on your machine, it can read your real address directly from the operating system. It doesn't need to defeat the tunnel; it can simply ask Windows which addresses your network cards have, read your Wi-Fi region code, read your GPS if you granted location, or list your installed apps.
No VPN, proxy or tunnel protects against this. Not ours, not anyone's. A network tool works on the network; it cannot make software you're running lie to itself about the computer it's running on.
If that's your threat model, the answer isn't a better tunnel. It's not running that software, or running it on a machine that has nothing else on it.
Where you are, if someone measures how long you take to answer
If your traffic appears to come from Sydney but you answer interactive requests 300 ms slower than someone in Sydney would, that's evidence. Measuring round trips from a few places narrows you to a region.
This reveals an approximate region, not your identity — and it trades directly against choosing a distant exit. A nearby gateway is faster and leaks less timing; a distant one hides your country better. You cannot have both.
What you tell people yourself
A region in a profile, a screenshot with an account name in it, a post explaining exactly how you're getting around something. This is the most common way people are identified, and no software prevents it.
Current limitations, stated plainly
WebRTC can reveal your real address in browser mode
When you use Reach as a browser proxy, a web page can use WebRTC to discover your real public address. WebRTC uses UDP directly and doesn't go through an HTTP proxy, so our proxy never sees it.
This is a known gap we're closing. Until the fix ships, if this matters to you:
- use per-app routing instead of the browser proxy — our engine refuses the UDP that WebRTC needs, so the discovery fails; or
- disable WebRTC in your browser (Brave's
brave://settings/privacyhas a WebRTC policy setting; Chrome needs an extension). See Choosing a browser.
Every "is my VPN leaking" test site checks this, so you can verify it yourself.
IPv6, in one narrow case
Reach suppresses IPv6 answers for names it routes, so apps use IPv4 and go through the tunnel. It also refuses IPv6 outright while an exit is in use or while you're sharing over Wi-Fi.
The gap: software that connects to a literal IPv6 address rather than a name, while you're using a gateway without sharing. There's no lookup for us to filter. Rare in browsers, less rare in some apps.
Ping and traceroute do not work through Reach
Our engine carries TCP and UDP. It has no ICMP handling at all, so ping and
traceroute are dropped rather than carried. This is not a leak — a remote host learns
nothing — but tools that rely on ping will report the destination as unreachable while
it's perfectly reachable in a browser.
UDP is restricted by default
Traffic we can't carry safely is refused rather than quietly sent outside the tunnel. For UDP that means most applications fall back to TCP, which we do carry. Voice and video over UDP work only where your organisation has enabled it.
"It worked yesterday" is not evidence
Services that care about this do not usually block you the moment they notice. They lower a score, wait, and act later — often in batches, deliberately irregular, sometimes asking you to verify your identity rather than banning you.
So a thing working today tells you very little about whether you've already been flagged. Plan accordingly: don't build something you can't afford to lose on top of an account you're using this way.
Short version
| Question | Answer |
|---|---|
| Does a website see my real IP? | No, for traffic Reach carries. Yes, for everything else. |
| Does Reach carry everything by default? | No. You have to turn that on. |
| Can an app I installed find my real IP? | Yes, always. No tunnel changes this. |
| Can a web page find it via WebRTC? | Today, in browser mode — yes. Fix in progress. |
| Can someone work out my region from timing? | Roughly, yes. Unavoidable. |
| Does ping work? | No. Not a leak; just unsupported. |
Common questions
Does installing Reach hide all my traffic?
No. Reach is selective by default: browsers you switch on, plus destinations your rules match. That's why your bank and your printer keep working. To cover everything, turn on per-app routing and, for devices that can't run Reach at all, "Route everything through Reach" in Share Reach over Wi-Fi.
Can my employer or my ISP see what I'm doing?
Your ISP sees that you're connected to Reach and how much data you move, not what's inside. For routed traffic they don't see which sites you visit. For unrouted traffic they see everything they normally would.
Does Reach keep logs of the sites I visit?
Destination logging is off unless your organisation turns it on. Diagnostic reports are only ever uploaded when you choose to send one.
Is using Reach legal? Will I get banned?
We can't answer either for your situation. Reach is a network tool; whether a given service's terms permit using it is between you and them, and local law is yours to know. We'd rather say that than pretend.
If something on this page is wrong, tell us — an out-of-date limitation is a bug in the documentation, and we'd rather fix it than have you find out the hard way.