Live browser privacy check

What does your browser reveal?

See the network, browser, and privacy-control signals websites can observe. Checks begin automatically and every result includes its evidence.

No account
No stored report
Evidence, not a score

Live privacy snapshotAutomatic browser result

Current result

Checking

Checking your browser

Ordinary network and browser signals are visible. The cards explain what was observed.

Checking now

Network identity

Checking

Loading address

Comparing public and WebRTC addresses

Network: Unavailable
Protocol: Unavailable

Browser exposure

Checking

Inspecting browser signals

These values can help make repeat visits recognizable.

Canvas: Checking
WebGL: Checking

Privacy controls

Checking

Reading browser privacy preferences

Preference signals ask sites to limit tracking but do not force compliance.

GPC: Checking
Connection: Checking

DNS resolver

Checking

Tracing DNS path

A fresh hostname is being checked. Results usually take one to three minutes.

Queries: Checking
Meaning: Waiting

What we found

Results are appearing as each check finishes

NetworkComparing public and WebRTC addresses
BrowserInspecting browser signals
ControlsReading browser privacy preferences

View technical evidenceIP, WebRTC, browser and control values

Current connection

Your public IP

Browser connection test

Checking browser exposure

Looking for public and local addresses exposed through WebRTC.

Browser signals

Inspecting available browser signals

Sites can combine ordinary browser and device details to make visits more recognizable. A value shown here is one signal, not a universal identity.

Browser preferences

Privacy control values

Secure connection: No
Global Privacy Control: Unavailable
Do Not Track: Unavailable
Cookies: Unavailable
Local storage: Unavailable
Session storage: Unavailable

Read the evidence

Understand what the result means

The snapshot separates normal visibility from a confirmed exposure. Open a focused test when you need a deeper explanation or a repeatable developer view.

Network identity

What the connection presents

Review the public IP, provider, ASN, protocol, and whether WebRTC returned another public address.

Open the WebRTC evidence

Browser exposure

What can make a visit recognizable

Inspect canvas, WebGL, screen, language, hardware, and time-zone signals without a uniqueness claim.

Inspect browser signals

Developer tools

Investigate a network address

Continue from an observed address to structured location, ASN, allocation, and registry evidence.

Open IP research tools

Transparent by design

Know what the check contacts

Privacy diagnostics should disclose their own network activity. These are the requests used for the live snapshot.

Network request

Same-site IP check

The page asks VeilVerify's Cloudflare endpoint for the public IP and selected network fields already available with the request. Documented browser fallbacks are used only if that endpoint fails.

Short-lived request

WebRTC comparison

The browser contacts Google's public STUN service to gather connection candidates. No camera or microphone permission is requested, and the peer connection is closed after the check.

Runs locally

Browser signal inspection

Fingerprinting signals and privacy preferences are read inside this page. They are not submitted to a fingerprint database or compared with other visitors.

Authoritative DNS probe

Resolver path check

The browser requests a random hostname under astrr.in. Cloudflare DNS analytics reports the recursive resolver that reached the authoritative nameserver. The random label is not stored in an application database.

Read the complete provider disclosure

Common questions about browser privacy checks

What this page can observe, what it cannot prove, and how to interpret an unavailable result.

Does VeilVerify save my privacy report?

No. VeilVerify does not create a result database. Values are held in page memory while this check is open, and the public IP endpoint returns only the connection fields shown on the page.

Why does the result say Review instead of giving a score?

A single privacy number can hide important differences. VeilVerify reports the observed signal, explains why it matters, and reserves Exposed for strong evidence such as a different public address returned through WebRTC.

Can this confirm that a VPN is working?

It can compare the public address used for the page with public addresses returned through WebRTC. It cannot inspect every application, route, DNS request, or VPN setting on the device.

Why might part of the check be unavailable?

Privacy extensions, browser policy, blocked STUN traffic, network filtering, or a temporary provider issue can prevent a signal from being observed. Unavailable does not mean protected.