Encrypted DNS at Home So Your ISP Stops Logging Every Site
Every time a phone, laptop or smart speaker in your house opens a website, it first asks a DNS server to turn a name like a bank's domain into an IP address.

Every time a phone, laptop or smart speaker in your house opens a website, it first asks a DNS server to turn a name like a bank's domain into an IP address. On most home networks that question travels in plain text to a server run by your internet provider, and the provider can log every name, from every device, with a timestamp. Many providers keep those logs for months. Some use them for advertising profiles, and in several countries they are required to hand them over on request.
Switching to encrypted DNS closes that particular window. It is not hard, it costs nothing, and it takes about twenty minutes for a typical household. It also gets oversold. Below is what it actually hides, what it leaves visible, and how to set it up so that every device benefits, not just the one you happened to configure.
What your provider sees today, and why
Classic DNS dates from 1983 and was designed for a small network of trusted universities. Queries go out over UDP port 53 without encryption. Anyone on the path between your router and the resolver can read them: your provider, the operator of a hotel Wi-Fi network, or someone running a rogue access point in a cafe.
Your router usually hands every device the provider's resolver automatically through DHCP. So even if you have never touched a network setting, your TV, your children's tablets and your work laptop are all sending their lookups to the same place. A week of those records shows which news sites you read, which health portals you visit, what time you go to bed and when the house is empty.
Some providers go further and rewrite answers. Type a domain that does not exist and, instead of an error, you land on a search page full of their ads. That is a sign your lookups are being read and modified in transit.
What encrypted DNS changes
There are two common standards. DNS over HTTPS, usually called DoH, wraps queries inside ordinary HTTPS traffic on port 443, so they look like any other web request. DNS over TLS, or DoT, uses a dedicated port, 853, with the same kind of encryption. Both stop anyone between you and the resolver from reading or tampering with the names you look up.
The trade is that you now trust a different company with that data. Choosing a resolver is the real decision. Here is how the main public options compare on the points that matter for privacy.
| Resolver | Address for DoT | Stated log retention | Filtering option |
|---|---|---|---|
| Cloudflare 1.1.1.1 | one.one.one.one | Query logs deleted within 25 hours | 1.1.1.2 blocks malware |
| Quad9 | dns.quad9.net | No IP addresses logged, Swiss jurisdiction | Malware blocking on by default |
| Mullvad DNS | dns.mullvad.net | No query logging stated | Several ad and tracker blocking tiers |
| NextDNS | Personal address per account | You choose: none, 1 hour up to 2 years | Fully configurable, free up to 300,000 queries a month |
All four publish privacy policies and have had some form of outside audit or long public track record. I would not pick a resolver that appeared last year with no company behind it, however fast its benchmark looks. If you also want to block known malicious domains for the whole family, the filtering side is covered in more depth in our guide to DNS filtering at home.
The common claim that encrypted DNS makes you private
You will read that turning on DoH means your provider can no longer see where you go online. That is only partly true, and believing it fully leads people to skip protections they still need.
Two things leak even with encrypted DNS. The first is the IP address your device connects to after the lookup. Your provider still sees that you opened a connection to a particular address. For large sites on shared hosting that address reveals little, but for a small clinic or a niche forum on its own server it can identify the site directly.
The second is the Server Name Indication field. When your browser starts an HTTPS connection, it usually sends the site's name in plain text so the server knows which certificate to present. A fix called Encrypted Client Hello exists and is supported by Firefox and Chrome, but only for sites hosted by providers that have switched it on. As of late 2026, that still covers a minority of the web.
So encrypted DNS removes the cheapest, bulk form of tracking: the neat log of every name from every device. It does not hide your browsing from a provider willing to inspect connection metadata. If you need that, a trustworthy VPN with an audited no logs policy is the tool, though it shifts the same trust question onto the VPN company. For most households the aim is simply to stop handing over a free, complete diary, and encrypted DNS does that well.
Setting it up for the whole house
Configuring a single browser protects only that browser. The better approach starts at the router and then fills the gaps on devices that leave home.
- Check the router first. Log in to its admin page and look under WAN, Internet or DNS settings for an option named DNS over TLS, DoT or Private DNS. Recent firmware on ASUS, AVM Fritz!Box, GL.iNet and many OpenWrt builds includes it. Enter the resolver's DoT hostname from the table above. If you have not changed the router's default admin password yet, do that now as well, following the order in setting up a new router securely.
- If the router lacks encryption, still change the resolver. Set the plain DNS fields to your chosen provider's addresses. This does not encrypt anything, but it stops your provider rewriting answers and moves the logs to a company with a stricter policy.
- Android phones. Open Settings, Network and internet, Private DNS, choose the hostname option and type, for example, dns.quad9.net. This applies on mobile data and on any Wi-Fi network, which is exactly where the router cannot help.
- iPhone and iPad. Apple does not offer a simple toggle. Install a configuration profile published by your resolver, or use its app. Cloudflare's 1.1.1.1 app and NextDNS both handle this in two minutes.
- Windows 11. Go to Settings, Network and internet, your adapter, DNS server assignment, Edit. Enter the resolver's IP addresses and set DNS over HTTPS to On (automatic template). Repeat for both Wi-Fi and Ethernet if you use both.
- Test it. Visit the leak test page offered by your resolver, or Cloudflare's own help page at 1.1.1.1/help, from each device. It should report that encrypted DNS is in use and show the resolver you chose, not your provider.
One caution. Some providers' routers, especially rented combo units, silently intercept all traffic on port 53 and answer it themselves no matter what you configure. The leak test will reveal this. If it happens, device level DoH or DoT on port 443 or 853 gets around it, because the provider cannot read or redirect encrypted traffic without causing an obvious certificate error.
What to do this week
Pick one resolver from the table, set it on your router, and turn on Private DNS on every Android phone in the house. Run the leak test on two devices. That covers most of your traffic in under half an hour. Leave the browser settings for later, or skip them entirely if the router handles encryption. More guides on keeping household data to yourself sit in the privacy section.
FAQ
Does encrypted DNS slow down browsing?
Rarely in a way you will notice. The first lookup to a resolver can take a few extra milliseconds while the encrypted session starts, after which results are cached. Large public resolvers are often faster than a provider's own servers.
Is DoH or DoT better for privacy?
The encryption is equivalent. DoT is easier for a network to identify and block because it uses its own port. DoH blends in with web traffic. On a router, use whichever the firmware supports.
Can my internet provider still see what sites I visit?
It can still see the IP addresses you connect to and, on many sites, the site name in the TLS handshake. Encrypted DNS removes the full lookup log, not every trace.
Will encrypted DNS break parental controls?
It can, if those controls rely on the provider's DNS filter. Use a resolver with its own filtering, such as NextDNS or Cloudflare's family address, and set it on the router so every device follows the same rules.
More in Privacy
How Shop Wi-Fi Tracks You Even If You Never Connect
Walk into a large department store with your phone in your pocket and never touch the screen.
Privacy
Which Documents to Shred and Which to Keep at Home
A pile of old bank letters, pay slips and medical bills is sitting in a drawer, and you are not sure which papers are safe to...
How to Stop Your Smart TV Tracking What You Watch
Your television probably knows more about your evenings than your closest friends do.