DNS-over-TLS vs DNS-over-HTTPS on Android: DoT vs DoH

Compare DNS-over-TLS and DNS-over-HTTPS on Android: Private DNS behavior, ports, browser overrides, VPN interactions and which format to use.

Server room network infrastructure illustrating DNS-over-TLS and DNS-over-HTTPS
Featured image for SSM APP Android DNS guide. Source: PDC server room.jpg by Johan Fredriksson / Esquilo; license: CC BY-SA 3.0; Wikimedia Commons: https://commons.wikimedia.org/wiki/File:PDC_server_room.jpg

DNS-over-TLS (DoT) and DNS-over-HTTPS (DoH) both encrypt DNS traffic between your device or app and a DNS resolver, but they use different transports and are configured differently. On Android, the system Private DNS screen normally asks for a provider hostname, while browsers and specialist apps may expose their own DoH controls.

The important distinction is scope: Android Private DNS can protect lookups made through the system resolver, while an app with its own secure-DNS implementation may use a different path. Neither DoT nor DoH is a VPN, and neither by itself encrypts all of your internet traffic.

What is DNS-over-TLS?

DoT carries DNS inside a dedicated TLS connection and is commonly associated with TCP port 853. Android introduced user-facing Private DNS in Android 9. Public resolvers such as Google and Quad9 publish hostnames that can be used for encrypted system DNS.

Examples include dns.google and dns.quad9.net. The exact hostname matters because Android must authenticate the TLS connection to the resolver.

What is DNS-over-HTTPS?

DoH sends DNS messages over HTTPS, normally on port 443. A DoH configuration is commonly represented as a URL endpoint such as https://dns.quad9.net/dns-query. Browsers, security tools and other applications can implement DoH independently of Android’s normal system resolver.

This is why two apps on the same phone can sometimes report different DNS resolvers: one may follow Android’s system configuration while another sends its own DoH requests.

DoT vs DoH on Android: the practical differences

  • Transport: DoT uses TLS specifically for DNS; DoH carries DNS through HTTPS.
  • Typical port: DoT commonly uses 853; DoH normally uses HTTPS port 443.
  • Android system UI: the Private DNS provider field expects a hostname, not a full https:// DoH URL.
  • App behavior: browsers and other apps can implement secure DNS independently of Android’s system resolver.
  • Troubleshooting: a working browser does not prove that every app is using the same DNS path.

Which protocol does Android Private DNS use?

For manual Private DNS configuration, provider documentation generally instructs Android users to enter a provider hostname. Quad9, for example, documents Android 9+ Private DNS as DNS-over-TLS and uses dns.quad9.net.

Provider implementations can evolve, so use the Android-specific setup instructions published by the resolver rather than copying an endpoint intended for a browser, router or another operating system.

Do not paste a DoH URL into the Private DNS field

If a provider gives you both a Private DNS hostname and a DoH URL, use the Android-specific hostname in Settings. A value such as https://dns.example/dns-query belongs in software that explicitly asks for a DoH endpoint.

If Android reports that the Private DNS server cannot be accessed, verify the hostname first. Then test without a VPN, restrictive firewall or captive-portal Wi-Fi. Our Private DNS server cannot be accessed guide covers that failure separately.

Does encrypted DNS hide the websites you visit?

DoT and DoH protect DNS queries from straightforward observation while those queries travel to the chosen resolver. They do not make the resolver unable to process the domains you ask it to resolve, and they should not be treated as complete traffic-anonymity tools.

DNS encryption is also separate from HTTPS protection for the website connection itself. Android 17 continues tightening network security in other areas: Google says apps targeting Android 17 that rely on cleartext traffic must use Network Security Configuration rather than assuming the older usesCleartextTraffic="true" behavior is sufficient. That change concerns application traffic security, not a replacement for DoT or DoH.

Which is more private: DoT or DoH?

Both can provide encrypted transport to the selected DNS resolver. In practice, privacy depends on more than the protocol name: the resolver’s retention policy, account or IP handling, app-specific DNS settings, VPN configuration and whether multiple DNS paths are active can all matter.

Choose a resolver whose published privacy and security policy fits your requirements rather than assuming that DoH is automatically more private than DoT, or vice versa.

Can browser DoH bypass Android Private DNS?

An application that implements its own resolver can make DNS requests independently of the normal system path. This is one reason a browser DNS test may disagree with another app or with a system-level diagnostic.

When troubleshooting, temporarily disable app-specific secure DNS or verify each layer separately. If you need to confirm the active resolver, see how to check which DNS server Android is using.

What happens when a VPN is active?

A VPN can route DNS through its tunnel and may supply its own resolver. The exact behavior depends on the VPN implementation. If you require a particular DNS provider while connected, check whether the VPN exposes custom DNS controls and whether it documents interaction with Android Private DNS.

For the broader distinction, read Private DNS vs VPN on Android.

Which should an Android user choose?

For a simple system-level configuration, use the provider’s documented Android Private DNS hostname. If you are configuring a browser or specialist app that explicitly supports DoH, use the provider’s DoH endpoint in that app.

If your goal is choosing a resolver rather than choosing a protocol, compare Google, Cloudflare, Quad9 and AdGuard for Android. If Private DNS itself keeps switching off or failing, use our Private DNS troubleshooting checklist.

Official references


Featured image credit: PDC server room.jpg by Johan Fredriksson / Esquilo, licensed under CC BY-SA 3.0, via Wikimedia Commons.

COMMUNITY

Start the conversation

Corrections, useful experiences and focused questions are welcome. Keep discussion respectful and on topic.