Network Privacy Checks

DNS & WebRTC Leak Test

Inspect observed addresses and resolvers, with inconclusive results clearly identified

WebRTC address test

Starting contacts public STUN services. No camera or microphone permission is needed. Candidate addresses are processed on this page and are not uploaded to our backend.

Network probes run only after you start the test.

DNS resolver observation

Starting attempts to resolve 16 random names unique to this session. Request failures are normally expected. Results come from authoritative DNS queries actually received, not explicit DoH probes. Service providers may record the names and resolver sources in their logs and analytics.

Checking whether DNS observation is available…

How to interpret these tests

A different WebRTC address needs context

Browsers may use multiple interfaces and both IPv4 and IPv6. Only public addresses of the same family can be compared directly. Private addresses, mDNS names, missing candidates, and timeouts need separate interpretation. This test does not establish a remote media connection.

DNS observations are real but may be incomplete

Unique names avoid reuse of previously queried names, and the session links authoritative observations to the test. Analytics is sampled and delayed: a missing record does not mean no query or no leak. Forwarding resolvers can also use several egress addresses.

The site caches session observations for about 30 seconds; a session expires after ten minutes. Service providers have separate log and analytics retention policies that do not end when a site session expires.