Verify if your DNS requests are exposing your true activity—especially when using a proxy or VPN.
Click to start a quick DNS leak check. We’ll detect the resolvers that handled your queries.
Note: This demo shows the UI layout. Test runs automatically in production.
Waiting to run
Click “Run DNS Leak Test” to start. We’ll compare multiple signals and WebRTC candidates.
IP | Hostname/Org | Location |
---|---|---|
203.0.113.12 | Unblockium DNS | US |
Tip: Seeing your ISP here usually indicates a DNS leak.
DNS is like the internet’s phonebook. Even if your traffic is proxied, leaking DNS means your ISP can still see which “numbers” you look up—revealing the sites you visit.
This is a leak. Your DNS requests are handled by your ISP resolvers.
Likely a leak (Google/OpenDNS etc.). Your app/OS bypassed the proxy for DNS.
Good. DNS is routed through your privacy service (or Unblockium).
WebRTC can reveal your real IP via STUN candidates. Consider disabling or restricting it:
Note: Disabling WebRTC may affect voice/video calls and some real-time apps.
Enable encrypted DNS so your resolver queries aren’t exposed:
Tip: If your organization enforces a custom DoH/DoT, confirm policy to avoid mixed routes.
Many services forward web traffic but ignore DNS privacy. Our premium plans route all DNS via private, encrypted resolvers—eliminating leaks at the source.
Need help? Contact our team.