Privacy DNS guide — Quad9, DNS-over-HTTPS and DNS-over-TLS

Every time you visit a website, a DNS request is made — a translation of domain name to IP address. By default this goes through your ISP or Google (8.8.8.8). Those parties can log what you request, when, and how often.

Privacy DNS guide — Quad9, DNS-over-HTTPS and DNS-over-TLS

Privacy DNS guide

Every time you visit a website, a DNS request is made — a translation of domain name to IP address. By default this goes through your ISP or Google (8.8.8.8). Those parties can log what you request, when, and how often.

A privacy-friendly DNS resolver solves this: no record of your IP address (Quad9’s policy), no sale of your query data, and often protection against malware domains too.


Who this is useful for

This guide is mainly useful for readers who:

  • want to give their internet provider less visibility into their browsing behaviour
  • want a small but meaningful privacy improvement without new hardware
  • are looking for a simple network step with little maintenance

For most readers, this is a low-friction baseline measure, not an advanced project.

If you are unsure whether this is a useful improvement or just another technical hobby project, use this rule of thumb: privacy-friendly DNS is usually worth doing; building your own full DNS stack usually comes later.


What you gain, and what it costs

With privacy-friendly DNS, you usually gain:

  • less direct visibility for your internet provider into which domains you look up
  • encrypted DNS traffic if you use DoH or DoT instead of plain default DNS
  • sometimes extra malware or tracker blocking, depending on the provider

But it does not solve everything:

  • websites still see your IP address
  • tracking cookies and browser fingerprinting still exist
  • you move trust from your provider to a different DNS operator

Adoption friction is usually low. Maintenance is also low, as long as you choose a simple provider configuration instead of self-hosted DNS.

For most readers, this is a sensible baseline improvement. It becomes overkill when you turn a simple DNS change into a self-hosted network project before your more important basics are in place.


What the right next step is for most readers

For most PrivacyGear readers, the right route is simple:

  1. choose a reliable provider such as Quad9
  2. set it system-wide on your phone or computer
  3. leave router-wide or self-hosted DNS until you have a concrete reason to manage it

Choose roughly like this:

  • choose Quad9 if you want one solid default setting with very little thought or maintenance
  • choose AdGuard Home or router DNS only if you are already actively managing your home network

Used Mullvad DNS? Mullvad set 2 November 2026 as the end date of its public DNS service and points its users to Quad9 (see below). In France, Quad9 itself stops serving users on 24 November 2026 (see the Quad9 section).


What is DNS and why does it matter?

DNS (Domain Name System) is the phone book of the internet. When you type privacygear.nl, your device asks a DNS server: “What is the IP address of privacygear.nl?”

The problem: Your internet provider or network administrator sees these queries by default. Even if you use HTTPS for the website’s content, the DNS query is visible — unless you use DNS-over-HTTPS or DNS-over-TLS.

What DNS providers see:

  • Which domains you request
  • What time
  • How often
  • From which IP address

How providers handle this differs by company and country. That is exactly why it makes more sense not to send DNS unencrypted through your default provider unless you have to.


DNS-over-HTTPS and DNS-over-TLS

Standard DNS travels unencrypted over the network (UDP port 53) — visible to your ISP, router, or anyone monitoring your network.

DNS-over-HTTPS (DoH): DNS queries are sent as HTTPS traffic (port 443). Looks like normal web traffic. Supported by Firefox and Windows 11, among others.

DNS-over-TLS (DoT): DNS queries are encrypted over TLS (port 853). More clearly recognisable as DNS, but also encrypted. Better suited for routers and system-wide configuration. Android’s Private DNS uses it.

Which to choose? For browser level: DoH. For system-wide or router: DoT or DoH with system settings.

DNS-over-QUIC (DoQ): a newer third option, supported by Quad9 since 2026. Combines QUIC’s speed (less connection overhead than TLS-over-TCP) with the same encryption as DoT. Not yet as widely supported across operating systems and apps as DoH/DoT, so for most readers DoH or DoT remains the practical choice for now.


Quad9 is the default recommendation for most PrivacyGear readers.

Why Quad9:

  • Non-profit — no advertising model
  • Based in Switzerland
  • Blocks malware domains via Threat Intelligence feeds
  • Positioned as a privacy-friendly resolver with very low maintenance friction

Quad9 addresses:

Type Address
IPv4 9.9.9.9 / 149.112.112.112
IPv6 2620:fe::fe / 2620:fe::9
DoH https://dns.quad9.net/dns-query
DoT tls://dns.quad9.net

Variants:

  • 9.9.9.9 — with malware blocking (recommended)
  • 9.9.9.10 — no malware blocking (Quad9: for experts only)
  • 9.9.9.11 — with blocking + ECS (passes part of your IP address on so sites can pick a nearby server; less private)

Best fit: normal users and privacy-conscious readers who want one good system-wide setting without having to manage filters, dashboards or custom rules.

Not in France from 24 November 2026. A French court ordered Quad9 to block a list of domains for users in France (a case brought by the broadcaster beIN over sports-streaming sites). Quad9 says it cannot tell reliably which users are in France and will not block the names for everyone, so it stops serving users in France on 24 November 2026; an appeal is pending, and Quad9 says about 20 similar cases against it and other resolver operators are waiting in France. If you live in France, or travel there with Quad9 set on your phone or travel router, set another resolver from the comparison below before that date and check on the provider’s own site that it still serves France, or use your VPN’s own DNS. Outside France nothing changes.


Mullvad DNS: end date 2 November 2026

Mullvad runs a free public encrypted DNS service (dns.mullvad.net and blocking variants such as adblock, base, extended, family, all). On 3 September 2026 Mullvad announced that it would shut the service down on 2 November 2026 and financially support Quad9 instead. On 6 November Mullvad’s Mullvad Browser 16.0 post called it “now discontinued”. Its servers still answered in our tests on 5 and 11 November, but they can stop at any moment: treat it as off.

What to do if you still have it set:

  • Manually set Mullvad DoH/DoT (Android Private DNS, Windows, router, AdGuard Home upstream, browser): switch to Quad9 (outside France), using the steps below.
  • Mullvad DNS profile on iPhone, iPad or Mac: Mullvad says it will stop working; remove it (Settings → General → VPN & Device Management; Mac: System Settings → General → Device Management) and install Quad9’s profile instead.
  • Mullvad Browser: if you kept the default DNS setting or the built-in ad-blocking option, Mullvad moves you to Quad9 automatically (since Mullvad Browser 16.0). If you picked a variant such as base or family, set it back to the default.
  • Mullvad VPN users: nothing changes. While connected, DNS goes through the VPN server’s own resolver, which Mullvad says is faster anyway.

DNS provider comparison

Provider Privacy Malware blocking Ad blocking Owner Location
Quad9 Good Yes No Non-profit Switzerland (no service in France from 24 Nov 2026)
Cloudflare (1.1.1.1) Fair Via 1.1.1.2 No (1.1.1.3 adds an adult-content filter) Cloudflare Inc. US
Google (8.8.8.8) Poor No No Google US
NextDNS Good Yes Yes NextDNS Inc. US
AdGuard DNS Good Yes Yes AdGuard Cyprus

Cloudflare 1.1.1.1 is still better for many people than Google or their ISP’s default resolver, but PrivacyGear still prefers Quad9 because it is a better privacy fit for this site.


Setting up on different devices

Using a VPN? VPN apps (and iCloud Private Relay) usually handle DNS themselves and ignore the settings below. Android’s Private DNS is the exception: according to GrapheneOS, which builds on Android, it takes precedence over the VPN’s DNS (GrapheneOS FAQ), and GrapheneOS recommends against combining the two (GrapheneOS FAQ); Quad9’s Android guide says instead that Private DNS isn’t used with a VPN. Either way: set Quad9 in the VPN app’s own DNS setting instead, or keep the VPN’s DNS.

Android

System-wide Private DNS (Android 9+):

  1. Settings → Network & internet → Private DNS (not there, for example on another brand? Search Settings for “Private DNS”)
  2. Select “Private DNS provider hostname”
  3. Enter: dns.quad9.net and tap Save

This covers every app that uses Android’s own DNS, not only the browser.

iOS / iPadOS

iOS has no DoH/DoT switch in Settings. Use Quad9’s configuration profile (iOS 14 and later):

  1. Do this at home or another familiar location. With Stolen Device Protection on, Apple only lets you install a profile elsewhere after turning the protection off, and away from familiar places that itself takes a one-hour security delay.
  2. In Safari, open Quad9’s iOS guide and download the profile for 9.9.9.9 (HTTPS is Quad9’s recommendation for most people). Other browsers won’t work for this.
  3. Within 8 minutes (iOS deletes it after that): Settings → Profile Downloaded → Install, enter your passcode, then Install again and Done. The warning that traffic may be filtered or monitored is normal for any DNS profile.

You can see or remove the profile later under Settings → General → VPN & Device Management. Quad9’s current profiles expire on 19 January 2027; download a new one before then.

Alternative: use a DNS filtering app like AdGuard for iOS if you explicitly want filtering too, not only a different resolver.

Windows 11

  1. Settings → Network & internet → Wi-Fi → Manage known networks → your network (or Ethernet → your network)
  2. Next to DNS server assignment (Quad9’s name for it; Microsoft’s help doesn’t name this field), select Edit → Manual, and turn on IPv4
  3. Preferred DNS: 9.9.9.9, DNS over HTTPS: On (automatic template)
  4. Alternate DNS: 149.112.112.112, DNS over HTTPS: On (automatic template)
  5. Save. Repeat for IPv6 (2620:fe::fe, 2620:fe::9) only if your connection has IPv6; otherwise leave it off, or DNS can fail

“Fallback to plaintext” off means no DNS at all on a network that blocks DoH; on a laptop that roams, Quad9 suggests turning it on. Windows 10 has no DoH setting.

macOS

Without encryption: System Settings → Network → select connection → Details → DNS → + → add 9.9.9.9 and 149.112.112.112.

For DoH or DoT, use Quad9’s profile (macOS 11 Big Sur and later):

  1. In Safari, download the 9.9.9.9 profile from Quad9’s macOS guide
  2. Open it from Downloads, then System Settings → General → Device Management (scroll down if needed), double-click the profile under Downloaded → Install, and enter your password

Like on iOS, Quad9’s current profiles expire on 19 January 2027. Firefox uses its own DNS over HTTPS in some regions; set it as under Firefox below, or switch it off so the profile applies.

Router (OPNsense)

Following Quad9’s OPNsense guide (back up your configuration first):

  1. Services → Unbound DNS → DNS over TLS → +, and add one entry per address, each with Server Port 853 and Verify CN dns.quad9.net:

    Server IP: 9.9.9.9
    Server IP: 149.112.112.112
    Server IP: 2620:fe::fe      (only if your WAN has IPv6)
    Server IP: 2620:fe::9       (only if your WAN has IPv6)
  2. Apply

  3. System → Settings → General: switch off Allow DNS server list to be overridden by DHCP/PPP on WAN, then Save and Apply. Otherwise your provider’s DNS servers can still be used.

Leave Domain empty so all queries go to Quad9. OPNsense’s own docs add a tip: block outbound port 53 with a firewall rule so devices can’t bypass Unbound.

Router-wide DNS means all devices on your network benefit too, including smart TVs and IoT devices you cannot configure individually.

This only becomes the better next step if you are already actively managing your home network. For most readers, per-device or system-wide DNS comes first.

Firefox

  1. Settings → Privacy and security → DNS over HTTPS → Advanced settings
  2. Choose Custom and enter https://dns.quad9.net/dns-query (Quad9 is not in Firefox’s built-in provider list)

On any system this setting goes before the system DNS for Firefox itself: on Default, Firefox uses its own provider in some regions.


AdGuard Home — self-hosted DNS with blocking

If you have a home server or Raspberry Pi, AdGuard Home is a more powerful option: a local DNS resolver with configurable blocklists. Our Raspberry Pi privacy box guide covers running one at home.

Advantages over external DNS:

  • All logging stays local
  • Block lists fully customisable
  • Per-device statistics
  • Can forward upstream to Quad9 via DoH/DoT

This is not the default recommendation for most readers. It gives you more control, but also more setup work and more maintenance.

Installation (Docker):

docker run -d \
  --name adguardhome \
  --restart unless-stopped \
  -p 53:53/tcp -p 53:53/udp \
  -p 80:80/tcp -p 3000:3000/tcp \
  -v /opt/adguardhome/conf:/opt/adguardhome/conf \
  -v /opt/adguardhome/work:/opt/adguardhome/work \
  adguard/adguardhome

Navigate to http://[server-ip]:3000 for the configuration wizard. AdGuard lists ports 80 and 3000 for the admin panel, so both are mapped. In this bridged setup AdGuard Home sees every client as the Docker host; add --network host (Linux only, then without -p) if you want per-device statistics (AdGuard Home Docker wiki).

See also the AdGuard Home review for a complete discussion.


Limits of DNS privacy

DNS encryption solves one problem, but not everything:

What DNS privacy does NOT solve:

  • SNI (Server Name Indication): When connecting to an HTTPS website, the domain name is visible in the TLS handshake, unless Encrypted Client Hello (ECH) is active
  • IP address tracking: Your IP address remains visible to websites you visit
  • Tracking via cookies/fingerprinting: DNS says nothing about what happens afterwards on the website

For complete protection:

  • DNS privacy: Quad9
  • IP address: VPN (Mullvad, ProtonVPN) or Tor
  • Tracking: uBlock Origin, Firefox + strict mode

DNS privacy is one layer — not a complete solution.

Verification — does it work?

Test whether your DNS setting works:

Browser test:

  • Visit on.quad9.net, Quad9’s own check: it says whether your queries reach Quad9

Command line:

# Windows (PowerShell): which protocol reaches Quad9 (expect "doh")
Resolve-DnsName -Type txt proto.on.quad9.net.

# Linux: same check
dig +short txt proto.on.quad9.net.

On a Mac or iPhone, dig and nslookup skip the encrypted DNS profile by design, so use the browser check there.

DNS leak test: Use dnsleaktest.com to verify that your DNS is not leaking through your ISP, including when using a VPN.


Next step

Go further

Reviews