Check what WebRTC reveals about you
Any website can ask your browser for connection candidates and read what comes back — no permission prompt involved. This page asks in exactly the same way and shows you the answer. It deliberately uses no STUN server, so not a single packet leaves your machine.
- Runs entirely in your browser
- Works offline
- No upload
- No sign-up
- No watermark
Loading the tool…
How it works
- Open the page — the check runs by itself. Run it again after changing a browser setting or your VPN.
- Read the verdict: protected placeholder names, a local network address, or a routable public address.
- Each address found is listed with what it is and what a website could do with it.
Why nothing is uploaded
Every operation on this page is done by code running inside your browser tab, using the same engine that renders web pages. The file is read from disk into your tab’s memory, transformed there, and written back out as a download. It is never sent anywhere — not to us, not to a third party.
Verify it yourself
- Open your browser’s developer tools (F12) and select the Network tab.
- Load your file and run the tool.
- The only requests you will see fetch the tool’s own code — and, for a few heavy tools, their open-source engine from a public CDN — plus one small page-view ping to loreatec.jp (page address and title, nothing more). None of them carry your file.
Frequently asked questions
What is a WebRTC leak?
WebRTC is the browser machinery behind video calls. To connect two machines it lists your network addresses (“candidates”), and a script on any page can request that list without asking you anything. Historically that exposed your local network address and, on IPv6 connections, a globally routable one — including behind VPNs that forgot to cover WebRTC. Browsers have since tightened this, and this page shows you where yours stands.
Why does this test not show my public IPv4 address?
Finding that would mean asking an outside server (STUN) to report where your packets come from — in other words, sending traffic out. This page is deliberately offline, so it shows only what leaks with no server involved. Bear in mind that a website checking you out WOULD typically use a STUN server too, and could learn your public NAT address on top of whatever appears here.
What does a name ending in .local mean?
Protection working. Modern browsers replace your real local address with a random placeholder name that only devices on your own network can resolve. The website sees the placeholder; the address stays home. If you see raw numbers instead, that protection is off or overridden.
When does the browser reveal real addresses anyway?
Once you grant a site camera or microphone permission, browsers switch to real addresses to make the call connect well — a sensible trade-off for a video call, and a good reason to revoke permissions from sites that no longer need them. This page never requests those permissions.
Is anything sent anywhere?
No. The test creates a local connection object and reads what your browser writes into it. No STUN, no TURN, no request to our server. You can switch to flight mode first and it behaves identically.