Privacy Diagnostics

Privacy Diagnostics Tools

Start here when you want to understand what your current browser session and network path may expose. These tools show visible signals and explain their limits; they do not prove full anonymity or full VPN security.

IPWhat Is My IP

See your visible public IP and session summary.

VPNVPN Leak Test

Check IP, DNS, WebRTC, IPv6, and browser signals.

DNSDNS Leak Test

Run a limited resolver-signal DNS exposure check.

WebRTCWebRTC Leak Test

Inspect browser WebRTC candidate signals.

IPv6IPv6 Leak Test

Check IPv6 visibility in this browser session.

BrowserBrowser Fingerprint Test

Review browser-visible fingerprint surfaces.

TorTor Exit Node Check

Check whether a public IPv4 appears on the Tor exit list.

How to use this hub

Run the homepage diagnostic first, then use focused tools when a specific signal needs more context. For VPN checks, compare before and after reconnecting rather than relying on one result.

Limitations

Browser, DNS, and network signals can vary by app, network, resolver, and VPN settings. MyIPScan labels limited checks and avoids broad protection claims.

FAQ

What should I run first?

Start with the homepage diagnostic or VPN Leak Test, then open focused checks if you need detail.

Do these tools store results?

The browser-local checks do not add server-side storage. Server-assisted tools return the requested result only.

Can one test prove privacy?

No. These tools show visible signals and should be read together.

Check my browser/privacy

What this checks

Visible browser/session signals such as public route, DNS/WebRTC/IPv6 behavior, fingerprint traits, user-agent, or public IP context.

Limits

What this cannot check

It cannot certify anonymity, inspect every app, or prove that a VPN, ISP, device, or account is safe.

Read results

How to use the output

Treat results as review signals for this browser/session or public target. Re-test after one change, then use Safe Copy or notes that avoid raw identifiers.