Insights

Encrypted DNS: what it protects and what to check

Encrypted DNS protects lookups in transit. Learn how DoH, DoT and DoQ work, what resolvers still see, and how coverage and fallback differ.

Illustration of two-ended speaking tube with opaque sleeve.
On this page

Encrypted Domain Name System (DNS) protects queries and replies between your browser or device and a DNS resolver, which turns domain names into Internet Protocol (IP) addresses. DNS over Transport Layer Security (TLS), called DoT, and DNS over Hypertext Transfer Protocol Secure (HTTPS), called DoH, encrypt that exchange so others on the path can't read its contents. Your resolver still sees the queries, and encrypted DNS alone doesn't make your browsing anonymous.

In short:

  • Protected lookups. DoT and DoH keep lookup contents private from observers on the protected path.
  • Resolver trust. Your resolver can still read your ordinary encrypted DNS queries.
  • Coverage and fallback. Your settings determine which apps use encryption and whether failures allow plaintext.

What encryption changes in a DNS lookup

A traditional DNS lookup sends the domain name in plaintext, meaning unencrypted text. Someone on the network path can read that name. Encrypted DNS protects the exchange between your device and the resolver.

Illustrative lookup for example.com:

Device -- encrypted DNS query for example.com --> Resolver
Device <-- encrypted DNS reply with an IP address -- Resolver

Your device then uses the address to connect to the website. That website connection is separate from the DNS lookup. The lookup asks about the domain name, not a complete page URL, its path or the page's contents.

The main ways to encrypt DNS

DoT uses a dedicated TLS connection. DoH carries DNS inside HTTPS traffic. DNS over QUIC (DoQ) sends queries over QUIC, a secure transport protocol.

These methods protect the device-to-resolver exchange, with default ports shown for DoT and DoH.

DNS methodTransport usedProtected traffic
DNS over TLS (DoT)Dedicated TLS, port 853Queries and replies to resolver
DNS over HTTPS (DoH)HTTPS, port 443Queries and replies to resolver
DNS over QUIC (DoQ)QUIC secure transportQueries and replies to resolver

For your privacy decision, resolver policy, app coverage and fallback behavior matter alongside the transport. DoH's use of HTTPS doesn't mean it can't be identified or blocked.

Oblivious DNS over HTTPS (ODoH) adds a proxy, an intermediary that passes on your encrypted queries. The proxy conceals your IP address from the DNS resolver. It's a privacy extension that separates your address from your queries, not an anonymity guarantee.

What encrypted DNS doesn't hide

Encryption protects a particular connection, not every part of the DNS system. It doesn't automatically encrypt the resolver's onward DNS exchanges. The resolver's ability to read your queries makes its privacy policy a separate choice from its encryption support.

Encrypted DNS also doesn't hide every website connection from your internet provider. Metadata, information about a communication instead of its contents, can still reveal details about your activity. DNS encryption isn't a complete answer to tracking.

Domain Name System Security Extensions (DNSSEC) checks that DNS data hasn't been altered and comes from an authoritative source. It doesn't encrypt lookups, so it complements encrypted DNS instead of replacing it. Domain blocking is another separate function, so encryption alone doesn't block ads, malware or unwanted domains.

What to check before you turn it on

Only change devices you own or administer, and save the original settings so you can restore them. Treat resolver choice, app coverage and fallback as separate decisions.

1. Choose a resolver by its published policies.

Check the operator's commitments about query collection, retention and use. Check its filtering policy separately from its encryption support. An encrypted connection doesn't stop the resolver from reading the queries you send it.

2. Choose browser or broader device coverage.

Browser-level and operating-system support cover different scopes. For browsing alone, consider your browser's encrypted DNS setting. For other apps, check operating-system support and whether those apps use the system's resolver service.

A browser setting covers that browser's supported lookups, not necessarily other apps. An operating-system setting can serve apps that use its resolver service. Don't assume a browser, device or router setting encrypts every app's lookups.

3. Check managed-network requirements.

On a managed network, ask the administrator before changing DNS settings. Enterprise guidance recommends using the designated network resolver. That resolver supports access to local resources and the network's security policy.

4. Choose what happens when encryption fails.

Choose strict mode if you want lookups to stop when encrypted transport isn't available. Choose opportunistic mode only if you accept fallback to unencrypted DNS. Opportunistic mode can also be forced into plaintext by an attacker on the network path.

Check your client's documented fallback behavior because exact controls and exceptions vary by client and version. Changing a resolver's IP address alone doesn't enable encrypted DNS. You need the client's encrypted DNS support configured for the chosen resolver.

A strict-mode failure means encrypted resolution wasn't available through that configuration. It doesn't identify which endpoint or intermediary caused the failure. If it fails, check the endpoint settings and network policy before making further changes.

Check your choice. You should be able to name your resolver, the apps covered and whether failed encryption stops lookups or allows plaintext. That shows you understand the configuration's scope and fallback policy, not that you've proved encryption was used on a live connection. A page loading successfully isn't proof that encrypted DNS was used. If an answer is unclear, check the client's documentation or ask your administrator before relying on it.

Where doxx.net fits. doxx.net encrypts DNS lookups and blocks unwanted domains, but DNS encryption alone doesn't make browsing anonymous. If those features fit your needs, create a doxx.net account, download the app and connect a device or agent to the private network.

Ask an AI assistant

Share this article

Private Everywhere

Stop giving the internet everything

Keep your browsing, messages, files, and agents private.