WebRTC/STUN observations
When an environment check starts, the browser creates a WebRTC connection and contacts Cloudflare's public STUN service to gather ICE candidates exposed by the browser. The STUN service can see the public source address and port of the request.
IPVeya compares eligible public candidates with the current connection IP on this device only; candidates are not sent to the IPVeya API. A match means only that the candidates gathered in this run matched the comparison address. No candidates, a timeout, or an ICE error is unknown or failed, not proof that no leak exists.
DNS resolver observation
When configured, the browser resolves a one-time random hostname and IPVeya checks Cloudflare DNS Analytics for the resolver source address associated with it. This is usually a recursive resolver and may differ from the DNS server configured on the device. Missing, delayed, or failed records remain unknown.
This observation does not read the DNS settings on your device and cannot by itself determine whether a DNS leak occurred. DNS queries, web HTTP requests, and WebRTC ICE candidates are separate observation surfaces.
How to interpret the result
Candidate gathering may be affected by browser privacy settings, extensions, network policy, and UDP reachability. Treat the result as a limited observation of this browser run, not as a statement about every application or device traffic path.