Private checks. Clear answers.

Check what your browser and network reveal

See your public IP, test for WebRTC leaks, and inspect your browser fingerprint. The checks run in your browser and the results are not saved.

Free to useNo accountNo stored results
Connection overviewLive browser result

Current connection

Your public IP

Checking your public IP…

Check beyond your public address

Run two browser-side checks for WebRTC exposure and fingerprint signals.

Three checks. One clear picture.

Start with the address websites see, then inspect two browser-level signals when you need more detail.

Public IP

The address your connection presents

See your public IPv4 or IPv6 address, approximate location, network operator, and ASN without selecting a tool first.

Read the IP details
WebRTC

Another route out of the browser

Check whether browser connection negotiation exposes another public address, especially while a VPN is active.

Open the WebRTC test
Fingerprint

Signals that can make visits recognizable

Inspect canvas, WebGL, screen, language, hardware, and time-zone values available in the current browser.

Inspect browser signals

Questions people ask before they trust a privacy check

What the checks can show, what they cannot prove, and where the network requests go.

Does VeilVerify save my IP address?

No. The result stays in this page session. Your browser contacts the listed lookup providers directly, and those providers have their own data practices.

Can this confirm that a VPN is working?

It can show the public address and WebRTC addresses visible during this visit. Compare them with the location and network you expect from your VPN.

Is a browser fingerprint a unique identity?

Not by itself. Sites can combine several ordinary signals and other data to make repeated visits easier to recognize.

Why might a result be unavailable?

Privacy extensions, browser settings, network filtering, or a temporary provider issue can block part of a check.