Privacy Check: What Your Browser Reveals and How to Test It

A privacy check is a set of tests that shows what a website, ad network, or analytics script can learn about you the moment your browser loads a page. Most people assume the answer is "not much." In practice, a single visit can expose your approximate location, your internet provider, your device and browser version, your time zone and language, and a fingerprint that may be stable enough to recognize you again on a different site.

This guide explains what a privacy check actually measures, how to run one without installing anything, and what to do with the results. It focuses on browser-based diagnostics you can repeat in a few minutes.

What a Privacy Check Actually Measures

Privacy Check: What Your Browser Reveals and How to Test It - What a Privacy Check Actually Measures.

A useful privacy check is not one test. It is a group of tests that cover different layers of exposure. The layers matter because fixing one does not fix the others.

• Network layer: your IP address, ISP, approximate geolocation, and whether a proxy or VPN is detected.
• Transport layer: DNS resolution paths and WebRTC connections that can leak your real IP even when a VPN is active.
• Browser layer: user agent string, client hints, screen size, fonts, canvas rendering, and other fingerprint signals.
• Account layer: whether you appear logged in to popular sites, which some pages can infer without asking permission.
• Host layer: open ports and services on a server or home network you control.

A privacy check that only covers one layer gives a false sense of security. The most common mistake is running a VPN, passing an IP test, and never checking DNS, WebRTC, or fingerprinting.

Start With the Network: IP, DNS, and WebRTC

Privacy Check: What Your Browser Reveals and How to Test It - Start With the Network: IP, DNS, and WebRTC.

IP address lookup and geolocation

Your IP address is the first thing every server sees. An IP lookup reveals your ISP, your approximate city or region, and whether the connection looks like a VPN, hosting provider, or residential line. That last detail matters: some sites treat datacenter IPs differently from home connections.

DNS leak test

DNS is how domain names become IP addresses. If your device sends DNS queries outside the VPN tunnel, your real network can be visible even while your traffic is encrypted. A DNS leak test shows which resolvers are answering your queries and whether they belong to your VPN provider or your local ISP.

WebRTC leak test

WebRTC is a browser technology used for video calls and peer-to-peer connections. It can expose local and public IP addresses through the browser itself, bypassing a VPN. A WebRTC leak test is one of the fastest ways to confirm whether your VPN is doing what you paid for.

If you use a self-hosted setup, the same checks apply. Our guide to Algo VPN login and privacy checks walks through connecting clients and verifying that your IP is actually hidden. If you use a commercial service, Mozilla VPN login troubleshooting covers sign-in issues and the leak tests worth running afterward.

The Browser Layer: Fingerprinting and Client Hints

Privacy Check: What Your Browser Reveals and How to Test It - The Browser Layer: Fingerprinting and Client Hints.

Even with your IP hidden, your browser can still be recognizable. Fingerprinting combines many small signals into a profile:

• User agent string and client hints (browser version, platform, device type)
• Screen resolution, color depth, and available fonts
• Time zone, language, and installed plugins
• Canvas and WebGL rendering output, which varies slightly by hardware and driver
• Audio processing characteristics

Individually, none of these identify you. Combined, they can be distinctive enough that a tracker recognizes you across sites without cookies. A canvas fingerprint checker and a user agent parser help you see exactly what your browser reports and whether it matches what you expect.

This is also where spoofing tools can backfire. If you use an antidetect browser or a user agent changer, inconsistent values are themselves a signal. Our breakdown of how antidetect browsers work and how to verify them explains where spoofing tends to fail and how to test a profile before trusting it.

Account and Identity Exposure

Privacy Check: What Your Browser Reveals and How to Test It - Account and Identity Exposure.

Some privacy check pages demonstrate that a site can detect whether you are logged in to popular platforms. This usually works by loading a resource that only resolves for authenticated users, then measuring whether the request succeeds. The site does not need to read your account; the presence or absence of the response is enough.

This is a reminder that logging out of a service does not necessarily remove its tracking cookies. Reviewing active sessions and clearing cookies for accounts you do not need open is a practical first step. Our notes on BrowserLeaks login detection and safer alternatives cover what this class of test reveals and why it is worth checking periodically.

Host and Network Checks: Ports and Speed

Privacy is not only about what you leak outward. It is also about what you expose inward. An open port on a home router or a cloud server is an invitation. A browser-based port scanner can check common ports without installing anything, which is useful when you want a quick read on a VPS or a small network.

If you are evaluating scanning tools, it helps to know that the underlying engine is free. Our explanation of Nmap pricing and what the Network Mapper includes covers what is open source and how to scan ports without a local install.

Connection speed belongs in the same conversation. A slow or unstable VPN makes people disable it, which defeats the purpose. Testing speed before and after connecting tells you whether the privacy trade-off is sustainable for your daily use.

How to Run a Privacy Check in Practice

A repeatable routine takes about ten minutes and works on any device.

1. Baseline first. Run the tests with your normal connection before enabling any privacy tool. Save or screenshot the results.
2. Connect your VPN or proxy. Re-run the IP lookup, DNS leak test, and WebRTC leak test. The IP and DNS resolvers should change; WebRTC should not reveal your original address.
3. Check the browser layer. Review your user agent, client hints, and canvas fingerprint. Note whether values are consistent with your actual device and browser.
4. Test at a second location. Repeat on a different network, such as mobile data. Leaks often appear only on specific networks or when switching between Wi-Fi and cellular.
5. Fix one thing at a time. Change a setting, re-test, and compare. Bulk changes make it impossible to know which fix worked.
6. Recheck after updates. Browser and VPN updates can change defaults. A monthly recheck catches regressions early.

BrowserScan provides this full set of tests in one place, including fingerprint analysis, DNS and WebRTC leak checks, IP lookup with proxy detection, a port scanner, a speed test, and a user agent parser. Because everything runs in the browser, there is nothing to install and no account required to get a reading.

Interpreting Results Without Overreacting

Not every finding is a problem. Some signals are unavoidable: your browser must send a user agent, and your connection must have an IP address. The goal is not invisibility. It is making sure that what you expose is intentional and consistent.

A practical way to judge a result:

• Expected and consistent: your VPN IP appears, DNS resolvers belong to the VPN, WebRTC shows no real IP, and fingerprint values match your device. Nothing to do.
• Expected but inconsistent: the IP changed but the time zone or language still reflects your real location. This is a common fingerprint mismatch worth addressing.
• Unexpected: your real IP appears in a WebRTC test, DNS queries go to your ISP, or a proxy is flagged when you are not using one. These are the findings that deserve immediate attention.

Related reading

• What Is Algo VPN? Self-Hosted WireGuard & IPsec Guide - Algo VPN is an open-source Ansible toolkit that deploys a personal WireGuard or IPsec server on your own cloud account. Learn how it works and how to verify it.

Sources and further reading

• Privacy Test & Analyzer: See what information websites know about you - You might be surprised just what information a website knows about you. This can include your browser, other websites you are logged in to and even your IP address.
• Check Privacy Score | Free Personal Exposure Check - Check your online exposure risk, understand what may be exposed, and follow a simple cleanup plan. Free to start. No sensitive ID required.

FAQ

What is a privacy check?

A privacy check is a group of tests that show what data your browser and network expose to websites. It typically covers IP address and geolocation, DNS and WebRTC leaks, browser fingerprint signals, and sometimes account login detection and open ports.

Can a website really identify me without cookies?

Sometimes. Browser fingerprinting combines many small signals into a profile that can be distinctive enough to recognize a returning visitor. It is not guaranteed to be unique, but it can be stable over time, especially on desktop browsers with uncommon configurations.

Does a VPN make me anonymous?

No. A VPN hides your IP from the sites you visit and encrypts traffic between you and the VPN server, but it does not change your browser fingerprint, and it does not stop you from logging in to accounts that identify you. It is one layer, not a complete solution.

Why does my WebRTC test show my real IP when my VPN is on?

WebRTC can establish peer-to-peer connections outside the VPN tunnel, depending on browser settings and the VPN client. Disabling WebRTC in the browser or using a VPN client that handles it correctly usually resolves the leak.

How often should I run these tests?

After any change to your browser, VPN, or network, and then on a monthly schedule. Updates can silently change defaults, and a quick recheck is the only reliable way to catch that.

Conclusion

A privacy check is less about fear and more about visibility. Once you can see your IP, your DNS resolvers, your WebRTC behavior, and your browser fingerprint in one place, you can make decisions based on facts instead of assumptions. Start with the network layer, confirm your VPN is not leaking, then look at the browser layer to see how recognizable you are. Re-test after every change, and treat the results as a baseline to improve rather than a verdict.

Run the tests on your current setup, note what surprised you, and fix the highest-impact item first. That single habit does more for your privacy than any one tool.