Skip to content
First-party authoritative DNS

DNS Leak Check

Investigate whether DNS lookups follow your expected network setup. A leak assessment requires resolver evidence; reaching a public DNS service does not prove your device uses it.

Observed resolver count--Waiting
Waiting
Public outlet IP--
DNS resolver--
Resolver location--
DNS query protection--

DNS evidence matrix

Shows recursive resolvers observed during this run. Resolver location is not collected; leakage and encryption remain undetermined.

Network & identity
Resolver observation status--
Method--
DNS / outlet parity--
Probe count--
FieldCurrent valueSourceStatusNote

Raw evidence JSON

Shows this visit’s authoritative DNS callback, resolver addresses, receipt time and limitations.

{}

How to read it

Check which DNS services handle domain lookups.

01

Resolver results

A random-domain check is needed to observe the actual resolver. Run again if no result arrives; missing results do not mean a leak was detected.

02

Evidence scope

Our authoritative DNS service returns results relayed by the browser. The HTTP request signature does not authenticate this DNS session. Resolver IPs do not establish browser-to-resolver encryption.

03

Different locations

Public DNS, Anycast and location databases can explain differences. Review your DNS or proxy settings; location alone does not prove a leak.