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
Public outlet IP--
DNS resolver--
Resolver location--
DNS query protection--
Waiting
DNS evidence matrix
Compare the observed resolver and its location with your network exit. Different locations alone do not prove a leak.
| Field | Current value | Source | Status | Note |
|---|
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.
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.
DoH probes
Browser access to public DoH endpoints proves reachability only; it does not prove system DNS is using DoH.
Different locations
Public DNS, Anycast and location databases can explain differences. Review your DNS or proxy settings; location alone does not prove a leak.