DNS over HTTPS: Should You Turn It On, and How to Check It Works
DNS over HTTPS explained from RFC 8484: what it hides and what it does not, when to leave it off, how to enable it per platform, and how to verify it.
In this guide
DNS over HTTPS (DoH) encrypts your device's name lookups inside ordinary HTTPS on port 443, so your Wi-Fi network and ISP cannot read or alter them. Turn it on for personal devices on networks you do not control. Leave it off where a work policy, parental filter or local DNS must see your queries, then verify with a resolver check.
Test it now
Cloudflare edgeRead at the Cloudflare edge from this request. The homepage adds your provider, network type and the VPN, DNS and WebRTC checks.
Show detailsWhat is DNS over HTTPS?
DNS over HTTPS is the protocol defined in RFC 8484 (October 2018) for carrying DNS queries and responses as HTTPS requests to a resolver. The DNS message is unchanged. The client sends the same wire-format packet it would send on port 53, as an HTTP POST body or base64url-encoded in a dns parameter of a GET, with the media type application/dns-message. RFC 8484 requires servers to support both methods and names HTTP/2 as the minimum recommended version.
Sharing port 443 with every website is the practical point: a network that wants to block DoH has to identify the resolver, not close a port.
DNS over HTTPS vs DNS over TLS vs DNS over QUIC vs plain DNS
The four transports differ in port, blockability and built-in support.
| Transport | Standard | Port and carrier | What the local network sees | Where it is built in |
|---|---|---|---|---|
| Plain DNS | RFC 1035 (1987) | UDP 53, TCP 53 | Every name and every answer, readable and rewritable | Every operating system; the default everywhere |
| DNS over TLS (DoT) | RFC 7858 (2016) | TCP 853 | Encrypted DNS to a named server; not the names | Android 9+ Private DNS; iOS and macOS via profile or app |
| DNS over HTTPS (DoH) | RFC 8484 (2018) | 443: TCP for HTTP/2, UDP (QUIC) for HTTP/3 | HTTPS to a server, indistinguishable by port from browsing | Windows 11 Settings; Chrome, Edge, Firefox, Brave; iOS and macOS via profile or app |
| DNS over QUIC (DoQ) | RFC 9250 (2022) | UDP 853 | Encrypted QUIC to a named server; not the names | Resolver and client software; no mainstream OS setting yet |
RFC 7858 defines two DoT client profiles: opportunistic privacy, which encrypts when possible but does not authenticate the server and so holds only "when there are no on-path active attackers," and out-of-band key-pinned privacy, which accepts only servers the client already knows. Android's Private DNS modes map onto that distinction, which is why https://checkmyip.com/learn/what-is-private-dns tells you to enter a hostname rather than leave it on Automatic. RFC 9250 gives DoQ the privacy of DoT over QUIC, with each query on its own stream.
Between DoH and DoT, the difference is blockability. Quad9's setup guides recommend DoH for devices that roam onto guest or corporate Wi-Fi because it "is not as commonly blocked on firewalls," and DoT for devices that stay on networks you control. For the resolvers themselves, see https://checkmyip.com/learn/which-dns-server-should-i-use.
What DoH protects, and what it does not
DoH protects the path between your device and the resolver. Three things stay visible.
The resolver still sees every query. RFC 8484 says the privacy considerations of DoH "are incremental to those of DNS over TLS": you have moved the record of your lookups from the local network and your ISP to the resolver you chose. The RFC lists HTTPS-specific ways that resolver can correlate requests, including cookies (which DoH clients "SHOULD NOT" accept) and the User-Agent header, and notes that "the client address provides obvious correlation information." DoH is a choice of whom to trust, not an escape from trust.
The server you connect to next is still visible. The destination IP address is not hidden, and in most TLS connections the server name still travels in the clear in the ClientHello. RFC 9849 (TLS Encrypted Client Hello, March 2026) encrypts the ClientHello and is advertised through DNS HTTPS records, so it relies on encrypted DNS; the RFC itself warns that "ECH is not in itself sufficient to protect the identity of the server."
DoH does not prove the answer is correct. RFC 8484 states that the HTTPS connection "does not provide the response integrity of DNS data provided by DNSSEC." A validating resolver (Google and Quad9 both document that they validate) guards against forged records upstream; DoH guards the last hop.
The flip side: anything on your network that relied on reading DNS stops working. RFC 8484 says filtering or inspection systems "that rely on unsecured transport of DNS will not function in a DNS over HTTPS environment."
DNS over HTTPS on or off: when to turn it on
Turn DoH on when the device is yours, you choose the resolver, and you regularly use networks whose DNS you have no reason to trust. Public Wi-Fi, hotel and airport networks, any network that redirects lookups to its own resolver, and an ISP whose logging policy you dislike are the cases DoH was written for. On those networks a plain-DNS resolver can read every name and hand back any answer it likes; DoH takes both abilities away from everyone except the resolver you picked.
When to leave DNS over HTTPS off
A managed work computer. Microsoft's DoH documentation warns, "Don't enable the Require DoH option for domain joined computers," because Active Directory depends on DNS and the Windows Server DNS service does not answer DoH queries; a Group Policy offers Allow, Prohibit and Require DoH. Microsoft's Edge policy DnsOverHttpsMode says that on managed devices where it is not configured, "DNS-over-HTTPS queries aren't sent." Chrome's help says, "If your device is managed or parental controls are turned on, you can't use Chrome's secure DNS feature." If your employer manages the device, the decision has been made.
Parental controls or a home DNS filter. A Pi-hole, a filtering router or a filtered resolver only works if it sees the queries; a child's device with its own DoH setting bypasses all of it. Firefox's default mode exists for this reason. Mozilla says Default protection "disables DoH when VPN, parental control or enterprise policies are active," and Firefox also resolves a canary domain, use-application-dns.net, through the operating system: an NXDOMAIN, SERVFAIL or empty NOERROR answer turns default DoH off.
The canary "does not apply for users who have made the choice to turn on DoH by themselves." If you run the filter, keep devices on plain DNS to it and encrypt from the filter upstream; https://checkmyip.com/learn/network-is-blocking-encrypted-dns-traffic covers what happens when a filter and an encrypted-DNS device collide.
Split-horizon names. Office VPNs and home labs serve names that exist only on a local resolver, which a public DoH resolver cannot answer. Windows's Name Resolution Policy Table and the Matching domains list in Apple's DNS Settings payload exist to route only chosen domains to a given server.
Captive portals. A hotel login page answers DNS itself until you accept its terms, so with strict DoH and no fallback the portal never appears. Firefox keeps the native resolver for "portal detection" even in DoH-only mode; Windows 11 offers a Fallback to plaintext switch, which Quad9's guide suggests for laptops that roam. The cost is silent downgrade: Microsoft says "you won't be provided with any notification if DNS queries are switched from DoH to plain text."
Does DNS over HTTPS slow things down?
Not measurably once a connection is up, and in Google's field data the HTTP/3 variant beat DNS over TLS. Google's security blog (July 19, 2022) reported that replacing DoT with DNS over HTTP/3 on Android cut median query time by 24 percent and 95th-percentile query time by 44 percent for successful queries, with both encrypted transports completing 97 percent of queries against 83 percent for plain UDP. The reasons it gives match RFC 9250: no head-of-line blocking, and a connection that resumes in one round trip after a network change.
How to enable DNS over HTTPS on each platform
Windows 11
Windows applies DoH only when the DNS server address matches a known template. Microsoft's built-in list holds Cloudflare (1.1.1.1, 1.0.0.1), Google (8.8.8.8, 8.8.4.4) and Quad9 (9.9.9.9, 149.112.112.112) with their IPv6 addresses; Add-DnsClientDohServerAddress in PowerShell adds another resolver. The steps, as Quad9 documents them for Windows 11:
- Right-click the network icon in the system tray, choose Network and Internet Settings, then Ethernet or Wi-Fi.
- Next to DNS server assignment, click Edit and change Automatic (DHCP) to Manual.
- Turn on IPv4, enter the preferred and alternate DNS addresses, and set DNS over HTTPS to On (automatic template) for each.
- On a laptop that roams, consider Fallback to plaintext; otherwise leave it off so a blocked network fails loudly rather than leaking.
- Repeat under IPv6 only if your connection has IPv6, then Save.
Microsoft documents the same control as Preferred DNS encryption: Encrypted only, Encrypted preferred (unencrypted allowed), or Unencrypted only.
Android
Android's system-wide setting is Private DNS, which uses DNS over TLS. Google's Android Help gives the path Settings, Network & internet, Private DNS, with the options Off, Automatic and Private DNS provider hostname. Since the Google Play system update described in Google's July 2022 post, devices on Android 11 and later upgrade well-known servers that support it to DNS over HTTP/3 automatically, so no further setting is needed. Hostnames and the "Private DNS server cannot be accessed" error are covered in https://checkmyip.com/learn/what-is-private-dns.
iPhone, iPad and Mac
Apple documented two ways to turn on encrypted DNS when it added native DoT and DoH support in 2020: an app using the NetworkExtension DNS settings API, or a configuration profile with a DNS Settings payload. Apple's Platform Deployment guide lists the payload's fields: Protocol (HTTPS or TLS), Server addresses, a Server URL that is required for HTTPS, and optional Matching domains. There is no toggle in Settings; once a profile or app is installed, its configuration appears in the Settings app (Apple's 2020 session shows it under General, VPN & Network) where you enable it.
Quad9's iOS guide, for example, has you download the profile in Safari, open Settings, Profile Downloaded, tap Install and enter your passcode; it notes that the profile expires on a printed date. On a network that blocks encrypted DNS, Apple says, "Connections in apps will fail rather than compromise your privacy."
Chrome and Edge
In Chrome, open Settings, Privacy and security, Security, and turn on Use secure DNS; then keep your current provider or pick one from the list. The choice matters: in the automatic mode, if a lookup fails, "it'll look up the site in the unencrypted mode", whereas with a chosen provider "Chrome won't default to unencrypted mode." In Edge the switch is under Settings, Privacy, search, and services, Security, Use secure DNS, then Choose a service provider; Edge's policy documents the modes as off, automatic (insecure fallback on error) and secure (DoH only).
Firefox
Firefox offers four levels under Settings, Privacy & Security, DNS over HTTPS: Default protection (on in available regions, off when a VPN, parental controls or enterprise policies are detected), Increased protection (always DoH with your provider, backup only on failure), Max protection (DoH only, no backup, per-domain exceptions) and Off. These set the network.trr.mode preference: 0 (off), 2 (DoH first, native fallback), 3 (DoH only) and 5 (off by choice). Mozilla says not to edit it by hand.
Public DoH endpoints
From the providers' own documentation:
- Cloudflare:
https://cloudflare-dns.com/dns-query(GET or POST,application/dns-message). - Google:
https://dns.google/dns-queryfor RFC 8484 andhttps://dns.google/resolvefor Google's JSON API, TLS 1.2 and 1.3 only. - Quad9:
https://dns.quad9.net/dns-query(malware blocking and DNSSEC),https://dns10.quad9.net/dns-query(unfiltered),https://dns11.quad9.net/dns-query(with EDNS Client Subnet).
How to check DNS over HTTPS is working
Turning the setting on is not the same as it being used: a VPN client, a filtering app, a browser with its own DoH or a blocking network can all change which server answers.
- Open https://checkmyip.com/my-dns-server on the device you configured. The page has your device look up a unique hostname that exists only on CheckMyIP's nameserver, so the resolver that fetches it is the one your device really uses. You see the resolver's address and network, its operator (Cloudflare, Google, Quad9, OpenDNS and ISPs are named from ASN data), its country, and status cards for encrypted DNS (DoH/DoT), where that can be inferred from the resolver that answered, client subnet forwarding and DNSSEC.
- Read the operator line. If you configured Cloudflare, Google or Quad9 and the resolver shown belongs to your ISP or is your router's address, DoH is not in effect: a VPN, a filter or a fallback has taken over. The tool cannot watch the hop between your device and the resolver, so the proof is that the resolver you chose, and only that resolver, is answering.
- Run https://checkmyip.com/dns-leak-test for a longer test. It fires a series of lookups at the site's own authoritative test zone and lists every resolver that answered, with ASN, location and whether EDNS Client Subnet was forwarded. A resolver outside the network you expected, such as your ISP's beside Cloudflare, is the leak the test is named for.
Repeat the first check on each network you use; a result that is right at home and wrong at the office means a policy or a block is in play there.
Sources
- RFC 8484, DNS Queries over HTTPS (DoH), IETF, October 2018
- RFC 7858, Specification for DNS over Transport Layer Security (TLS), IETF, May 2016
- RFC 9250, DNS over Dedicated QUIC Connections, IETF, May 2022
- RFC 1035, Domain Names, Implementation and Specification, IETF, November 1987
- RFC 9849, TLS Encrypted Client Hello, IETF, March 2026
- Microsoft Learn: DNS client over HTTPS (DoH) support (last updated 2023-12-03)
- Quad9 Documentation: Windows 11 (Encrypted) setup guide
- Quad9 Documentation: iOS 14 and later (Encrypted) setup guide
- Quad9 Documentation: macOS Big Sur and later (Encrypted) setup guide
- Quad9: Service addresses and features
- Apple Platform Deployment: DNS Settings payload settings (published March 7, 2024)
- Apple WWDC20 session 10047, Enable encrypted DNS (transcript)
- Android Help: Manage advanced network settings on your Android phone (Private DNS)
- Google Security Blog: DNS-over-HTTP/3 in Android (July 19, 2022)
- Google Public DNS: DNS-over-HTTPS (DoH) (last updated 2024-09-03)
- Google Public DNS: Secure transports (last updated 2024-09-03)
- Google Public DNS: DNS-over-TLS (last updated 2024-09-03)
- Cloudflare Docs: 1.1.1.1 DNS over HTTPS (last updated May 5, 2026)
- Cloudflare Docs: Make API requests, DNS wireformat (last updated May 5, 2026)
- Cloudflare Docs: Configure encrypted DNS on your browser (last updated May 5, 2026)
- Mozilla Support: DNS over HTTPS in Firefox
- Mozilla Support: Canary domain, use-application-dns.net
- Mozilla Wiki: Trusted Recursive Resolver (network.trr.mode values)
- Google Chrome Help: Manage Chrome safety and security (Use secure DNS)
- Microsoft Learn: Microsoft Edge policy DnsOverHttpsMode (ms.date 2026-05-20)
Questions
What is DNS over HTTPS?
DNS over HTTPS is the protocol in RFC 8484 that sends DNS queries and answers as HTTPS requests to a resolver, using the application/dns-message format over port 443. Because the traffic looks like any other web request, networks between you and the resolver cannot read the names you look up or rewrite the answers.
Does 8.8.8.8 support DNS over TLS?
Yes. Google Public DNS documents DNS over TLS on port 853 and DNS over HTTPS on port 443, both under the hostname dns.google, with TLS 1.2 and 1.3 only. On Android, enter dns.google as the Private DNS hostname; in a browser or on Windows, Google is one of the built-in secure DNS providers.
Is 9.9.9.9 good for gaming?
Quad9 (9.9.9.9) validates DNSSEC and blocks domains from threat feeds, but no resolver changes your game's ping, because DNS is used only to find the server before the match starts. If you want it, pick 9.9.9.11, Quad9's variant that passes EDNS Client Subnet so content servers are chosen near you.
Should I enable DNS over HTTPS, on or off?
On, if the device is yours and you often use networks you do not manage, such as public Wi-Fi: it stops the network from reading or redirecting your lookups. Off, or leave the default, on a managed work computer, a child's device under parental controls, or a network whose own DNS filter you rely on.
Back to your own address: check my IP

