ONE-CLICK PRIVACY REPORT
Privacy Exposure Score
Score IP, IPv6, WebRTC, DNS, browser fingerprint, cookie, storage, screen, and timezone signals to see what a website can observe in one report.
The scan runs in your browser. If external IP lookups fail, the report still uses local browser signals. Do not enter passwords or account details.
Why this report helps visitors
A VPN can change the visible IP while IPv6, WebRTC candidates, DNS routing, browser fingerprinting, cookies, or timezone still expose useful identity signals. Comparing them together is more useful than reading a single IP result.
How to read the score
80+
Your IP and browser signals look comparatively controlled. Still cross-check DNS leak, WebRTC, and fingerprint details.
50-79
Some signals are exposed or incomplete. Review VPN, IPv6, DNS, and browser settings in order.
Below 50
Public IP, WebRTC, DNS, or fingerprint signals may be strongly exposed. Recheck in the same browser and adjust settings.
What does Privacy Exposure Score show?
It scores public IP, IPv6, WebRTC, DNS hints, browser fingerprint, cookies, storage, screen, timezone, and referrer signals in one report. It shows the broader surface a website can observe, not just one public IP.
Privacy Exposure Score is a one-click report that combines IP lookup, VPN checks, DNS leak signals, WebRTC leak signals, and browser fingerprint posture. It helps visitors understand the visible exposure surface and continue into the right detailed diagnostic.
- Summarize what a website can observe from the current browser session.
- Compare IP, IPv6, DNS, WebRTC, and fingerprint signals before and after enabling a VPN.
- Decide whether DNS leak, WebRTC leak, or fingerprint testing should be checked first.
Guide
Privacy Exposure Score is a one-click report that combines IP lookup, VPN checks, DNS leak signals, WebRTC leak signals, and browser fingerprint posture. It helps visitors understand the visible exposure surface and continue into the right detailed diagnostic.
Best for
- Summarize what a website can observe from the current browser session.
- Compare IP, IPv6, DNS, WebRTC, and fingerprint signals before and after enabling a VPN.
- Decide whether DNS leak, WebRTC leak, or fingerprint testing should be checked first.
- Copy a plain-language privacy report for support, teammates, or family.
How to use
- Run the scan to collect IP, IPv6, WebRTC, DNS, and browser fingerprint signals.
- Review the overall score, risk badge, and each normal/warning/risk signal card.
- Copy the summary or open the next-action cards for DNS Leak, WebRTC, and Fingerprint checks.
- Change VPN, Secure DNS, or WebRTC settings, then rerun the report to compare.
Interpretation tips
- When both IPv4 and IPv6 are available, the active address can change by target site and network policy.
- A clean public IP is not enough if DNS or WebRTC still exposes another route.
- Browser fingerprints can remain useful tracking signals even when the IP is masked.
Privacy & notes
The scan runs in the browser. External IP lookups are used only as live diagnostic signals. Do not enter passwords, VPN accounts, or internal company URLs.
How To Interpret The Result
Classify the result as good, needs review, or requires action before you change production settings.
Matches the expected signal
If Privacy Exposure Score matches the expected domain, IP, browser, or configuration and there are no critical warnings, you can treat it as a baseline.
Recheck under another condition
Privacy Exposure Score can vary by network, DNS cache, CDN, VPN, browser setting, or mail provider, so retest when the signal looks inconsistent.
Cross-check before production changes
Before changing production settings, confirm the same cause with related tools such as VPN & Privacy Check, DNS Leak Test, WebRTC Leak Test.
Related Tool Categories
Tool collections that help you check the same issue from more than one angle.
Troubleshooting Playbook
Use these symptom-based checks when a result does not match what you expected.
The result does not match expectations.
Confirm that the input, network, browser conditions, and cache state match the previous test.
Cross-check the same target with related tools and retest after changing one condition at a time.
FAQ
What does Privacy Exposure Score show?
Can it prove that a VPN is safe?
Is my data stored?
Recommended Next Steps
Follow this order before changing production settings so you can validate the likely cause faster.
DNS Leak Test
Start with the most important signal.
Check whether DNS requests are leaking outside expected network paths.
WebRTC Leak Test
Then cross-check adjacent policy or configuration.
Check whether WebRTC exposes network addresses and potential leak risk.
VPN & Privacy Check
Finish by confirming user-facing or security impact.
Combines WebRTC leak, DNS leak, and IP analysis to verify whether your VPN is actually protecting your privacy.
Concept Guides For This Tool
Use these short explainers to understand why the result matters before you act on it.
VPN Privacy, DNS Leaks, and WebRTC Leaks
Turning on a VPN does not automatically hide every signal. DNS resolvers, WebRTC candidate addresses, and browser fingerprints can still reveal more than users expect, so privacy checks need to look beyond the public IP alone.
VPN leak check normal, warning, and fix-needed examples
VPN leak status is not only a public IP check. IP, DNS, WebRTC, fingerprint, language, time zone, and cookie signals should be compared as normal, warning, or fix-needed examples.
Related Tools
Use these tools together for better diagnostics.
DNS Leak Test
Check whether DNS requests are leaking outside expected network paths.
WebRTC Leak Test
Check whether WebRTC exposes network addresses and potential leak risk.
Browser Info
Inspect browser name, version, language, and User-Agent details.
Digital Fingerprint
Review browser fingerprint surfaces such as Canvas and WebGL.
Check My IP Address
Instantly check your public IPv4/IPv6 address, ISP, and approximate location.
Data Handling & Privacy
ipnawa is a diagnostics service. Inputs are used to produce results and are not intended for account-based profiling.
- Server-side tools (WHOIS, SSL, DNS, header checks) send your input domain/IP to our server for lookup.
- Browser-side tools (fingerprint, cookies, JavaScript) run primarily in your browser when supported.
- Standard web/server security logs may include IP address, timestamp, and User-Agent.
- Some checks call external providers such as ipinfo.io and bigdatacloud.net.
- Ads and non-essential cookies are loaded only after your consent choice.
External Processors
- ipinfo.io (IP/ASN/location lookups)
- bigdatacloud.net (reverse geocoding)
- Advertising partners (only after ad-consent acceptance)
You can review or change cookie/ad consent at any time.