OWL Claude
OWL / NETWORK LAB

WebRTC leak test

Inspect ICE candidates and compare public addresses with your HTTP connection.

Start test

Comparison mode uses the Google STUN endpoint seen in BrowserLeaks and a receive-only offer, without capturing audio/video. Extended mode samples a second provider. Browser policies and routing can still produce different observations.

Starting uses the selected Google / Cloudflare STUN services plus addr.tools for HTTP IPv4/IPv6. Camera and microphone access are never requested. Existing permission states and device types are read without device IDs or labels. If OWL’s HTTP baseline is unavailable, addr.tools looks up the organization and approximate location of an independently measured public IP.

Ready when you are. External network probes begin only after you start.

Network reports stay in this tab unless you download them. OWL does not store candidate IPs, resolver IPs or SDP in its database. External services can observe your connection and apply their own policies.
HTTP / BASELINE

HTTP public addresses

Not observed

Comparison uses independently observed HTTP addresses. Missing IPv4/IPv6 baselines stay unverified.

Browser capabilities

Not observed

Why can BrowserLeaks look different?

BrowserLeaks can display “No Leak” when it finds neither a local IP nor a mismatching public IP, including when both address fields are empty. OWL shows the same evidence but marks a missing public candidate as unverified. No observed address is not proof that every network path is protected.

How to read the result

A data channel gathers ICE candidates through Google and Cloudflare STUN, without opening camera or microphone. Direct public candidates are compared only with HTTP addresses of the same IP family. Relay addresses are not treated as your own IP. mDNS names are recorded without attempting to resolve them.

Different public addresses can indicate VPN/proxy bypass or multiple network paths; verify your setup. Matching addresses, mDNS masking, blocked STUN or no candidates cannot prove that every application is leak-free. Hidden devices may reflect browser permission restrictions.

Independent diagnostics by Owl. Results do not guarantee Claude access or account safety.

Source code & methodology ↗AGPL-3.0 ↗BrowserLeaks ↗