DNS is the internet’s phone book: every time you visit a website, your device first asks a DNS server to translate the domain name into a numeric IP address. A DNS lookup lets you read those published records directly — useful for checking whether your website’s domain is configured correctly, seeing where a domain’s email is handled, verifying a DNS change has propagated, or investigating a suspicious link before clicking it.
The leak test answers a different question: when you use a VPN, is your traffic actually private? A VPN is supposed to route everything — including DNS queries — through its encrypted tunnel. But misconfigured systems often keep sending DNS queries to the internet provider’s servers, which means your ISP still sees every site you visit despite the VPN. That is a DNS leak.
This tool also checks WebRTC exposure, a browser feature for video calls that can reveal your real IP address even with a VPN active, and IPv6 exposure, where a network quietly bypasses the VPN over the newer protocol. Running these checks takes seconds and tells you concretely whether your privacy setup does what it claims — no interpretation of marketing pages required.
A records map a domain to an IPv4 address and AAAA to IPv6. MX records name the servers that receive the domain’s email. NS records identify which name servers are authoritative. TXT records hold verification strings and email-security policies like SPF. CNAME points one name at another, SOA carries zone administration details, and CAA restricts which authorities may issue the domain’s security certificates.
A DNS leak means your domain-name queries travel outside your VPN tunnel to your ISP’s servers. The content of your browsing stays encrypted, but the list of every site you visit does not — which defeats a major reason people use a VPN. Leaks are usually fixable in your VPN app’s settings by enabling its own DNS or leak protection.
WebRTC can negotiate connections outside the tunnel and expose your address. Most privacy-focused browsers and VPN browser extensions offer a setting to limit or disable WebRTC; enable it and re-run the test to confirm the leak is closed.
Yes — a DNS lookup only reads public records that the domain owner has published; it does not contact the website itself. Checking a suspicious domain’s records is a safe first step that reveals infrastructure without visiting anything.
DNS answers can legitimately vary: changes take time to propagate through caches, and many large sites give different answers by region to route users to nearby servers. Both results can be correct at the same moment.