Your DNS queries can give you away: what a DNS leak is and how to check
Every time you open a website, your device asks a DNS server where it lives. If that question travels outside your secure connection, it tells others exactly where you are going.
Before your device can load a website, it needs to turn a name like example.com into an address. That lookup is handled by DNS, and it happens before the page loads, for almost every connection you make. It is easy to forget, and just as easy to leave unprotected.
DNS in one minute
Think of DNS as a phone book. Your device asks a resolver, “what is the address of this name?”, and gets an answer. By default the resolver belongs to your internet provider or your Wi-Fi network, and the question is sent as plain, readable text. Anyone along the way can read it, so a list of your DNS queries is effectively a list of the sites you visit.
What a DNS leak is
When you use a secure connection, your web traffic travels inside an encrypted tunnel. A DNS leak happens when the lookups do not travel inside it. The traffic is protected, but the names of the sites you are visiting still go to your local resolver in the clear.
It usually happens when the operating system keeps using the network’s own resolver, when a connection falls back to a different network interface, or when an application sends queries on its own.
How Kite handles DNS
For traffic that goes through the tunnel, Kite resolves names through the encrypted tunnel, so your local network does not see those lookups. We do not record DNS queries.
There is one deliberate exception. With Auto Routing, sites that are better reached directly, such as local websites, connect without the tunnel, and their names are looked up through your local resolver, exactly as they would without Kite. We do it for speed and so that local services keep working. If you would prefer everything to stay inside the tunnel, choose Global mode, described in our smart routing guide.
How to test it yourself
- Connect to Kite and make sure you are in the mode you want to test.
- Open a DNS leak test website, such as dnsleaktest.com or the leak tests from BrowserLeaks, and run the extended test.
- Look at the resolvers it lists. If they belong to your internet provider or the local network, those lookups are not going through the tunnel.
- Run it again in the other mode. In Auto Routing, some local resolvers are expected for sites that are routed directly, so read the result against what the mode is meant to do.
Habits that help
- Keep the Kite app up to date, because routing and DNS handling improve with each release.
- Turn on ad and malware blocking in the app if your plan includes it. It filters known bad domains at the DNS level, before a page loads.
- On a shared or public network, prefer Global mode if you want every lookup protected.
- Remember that DNS is only one signal. A website you log in to still knows who you are.
Daniel Brooks
Privacy & security writer
Daniel writes about online privacy, network security and how Kite works under the hood.