DNS privacy paths between a browser, HTTPS resolver, proxy, and authoritative DNS infrastructure

DNS over HTTPS (DoH) encrypts DNS queries and responses between your device and an HTTPS resolver. To enable it, turn on secure DNS in your browser or configure DoH in your operating system, choose a resolver, and set the fallback behavior. It does not make browsing anonymous or hide queries from that resolver.

This guide explains those choices, public resolver endpoints, and DNS routing with proxies and VPNs.

Last updated and official documentation checked: November 10, 2026.


Key Facts

  • DoH encrypts DNS exchanges between a client and an HTTPS resolver.
  • The selected resolver can read the DNS questions it answers.
  • DNSSEC authenticates DNS data without encrypting queries.
  • Plaintext fallback can allow unencrypted DNS when DoH fails.
  • Browser DNS settings and operating-system DNS settings can cover different lookups.
  • In curl, socks5h delegates destination-hostname resolution to the proxy.

What is dns over https, and how does it work?

The Resolver Path framework is a four-part check: which resolver answers, which protocol carries the query (plain DNS, DoT or DoH), where the query leaves your device, and whether a proxy resolves names for you (socks5h).

DoH carries DNS messages inside HTTPS exchanges instead of sending them over an unencrypted DNS connection. Its protection covers the client-to-resolver connection.

The basic path is client, HTTPS resolver, then DNS infrastructure as needed. The resolver answers from its cache or obtains the answer through further DNS lookups; the client’s encrypted connection does not automatically protect those subsequent exchanges.

RFC 8484 defines DNS over HTTPS using binary DNS messages. GET requests encode the message in a query parameter; POST requests carry it in the request body. A vendor’s JSON lookup interface is a separate interface, so it is not interchangeable with every browser’s DoH endpoint field.

Enabling HTTPS for a website and enabling DoH are separate actions. A secure website connection does not establish how its hostname was resolved.

DNS over HTTPS vs DNS over TLS vs plain DNS


Should you enable dns over https? Privacy benefits and limits

Enable DoH when you trust the selected resolver and it preserves the DNS behavior your network requires. Its main privacy benefit is protecting DNS contents from passive observation along the client-to-resolver path.

The resolver remains a trust boundary. DoH cannot hide your questions from that resolver, and direct website connections can still expose destination IP addresses and traffic patterns. These limits follow from the DoH standard’s privacy considerations.

Before changing DNS, identify which application resolves names, check whether your network requires internal DNS or filtering, and choose whether failed encrypted lookups should stop or fall back.

Mozilla’s protection-level guidance explains why VPNs, parental controls, and enterprise policies affect automatic activation. DNS privacy also leaves other tracking mechanisms untouched; review browser fingerprinting separately.


How to enable DoH in Chrome, Firefox and Windows 11

Enable DoH in the component that performs the lookups you want to protect. Browser settings configure browser behavior; operating-system settings apply to applications using that system resolver.

Chrome

Step 1: Open Settings, then Privacy and security, then Security.

Step 2: Under Advanced, turn on Use secure DNS.

Step 3: Keep the current service provider or select a custom provider. Automatic mode can fall back to unencrypted DNS; a custom provider does not use that fallback. See Chrome’s secure DNS instructions.

Firefox

Step 1: Open Settings, then Privacy & Security.

Step 2: Find DNS over HTTPS and open Advanced settings.

Step 3: Select a protection level and review its status. Default Protection can use ordinary resolvers when necessary and respond to network policies. Max Protection displays a warning when secure resolution is unavailable; an explicit exception can use system DNS. Follow Firefox’s protection-level instructions.

Microsoft Edge

Step 1: Open Settings, then Privacy, search, and services.

Step 2: Select Security and enable Use secure DNS to specify how to lookup the network address for websites. See Microsoft’s Edge security instructions.

Step 3: Check any managed policy before relying on strict behavior. Microsoft’s DnsOverHttpsMode policy distinguishes automatic mode, which permits insecure fallback, from secure mode, which fails resolution on error.

Windows 11

Step 1: Open Settings, then Network & internet, and select the active Wi-Fi or Ethernet connection.

Step 2: Open its DNS configuration for editing, choose Manual, and enter your chosen DNS server addresses for IPv4 and IPv6 as applicable.

Step 3: For DNS over HTTPS, select On (automatic template) or On (manual template). With a manual template, enter the resolver’s documented HTTPS template.

Step 4: Choose Fallback to plaintext on or off, check both preferred and alternate servers, and save. Review both address families so one configuration does not undermine the other.

Microsoft’s Windows network settings guide documents these choices and states that this DoH setting is unavailable in Windows 10.

macOS and iOS profiles

Step 1: Obtain a DNS configuration profile from your chosen resolver or administrator. Apple’s DNS Settings payload documentation describes encrypted DNS configuration. Confirm that DNSProtocol is HTTPS and ServerURL identifies your intended resolver. On iOS, iPadOS, and macOS 26 or later, also check AllowFailover: true permits fallback to the default system DNS resolver; the default is false. Review SupplementalMatchDomains and any on-demand rules to determine which lookups the profile covers. See Apple’s DNSSettings dictionary documentation.

Step 2: On macOS, open the downloaded profile, then System Settings, General, Device Management. Open the profile in Downloaded, review its contents, and follow the installation prompts, as described in Apple’s Mac profile instructions.

Step 3: On iOS, open Settings after downloading the profile, tap Profile Downloaded, then Install and follow the prompts. See Apple’s iPhone profile instructions. Review the profile’s scope before assuming every application uses it.

Android Private DNS

Android Private DNS accepts a provider hostname, not a DoH URL. It supports DoT; Android 11 and later with the relevant Google Play system update can upgrade supported providers to DNS over HTTP/3 (DoH3). The hostname setting alone does not identify the transport in use. Google’s DNS-over-HTTP/3 announcement explains this transport upgrade. Open Settings, Network & internet, Private DNS, select Private DNS provider hostname, enter a compatible hostname, and save. Google’s Android setup instructions document this route. Do not paste an HTTPS URL into the hostname field.


Fallback to plain text DNS: on or off?

Windows DoH plaintext fallback allows unencrypted queries when HTTPS resolution fails. Turning fallback off prevents that fallback but can leave lookups unanswered. Microsoft documents this behavior in its DNS configuration instructions.

Choose fallback on when continuity matters more than requiring encrypted DNS for every affected lookup. Choose fallback off when your policy requires encryption, accepting that resolver outages or blocked connections can interrupt browsing.

Chrome’s automatic mode similarly permits an unencrypted retry, while its custom-provider mode does not, according to Google’s secure DNS guidance. A browser toggle alone therefore does not answer whether plaintext fallback is possible.

Distinguish a backup encrypted resolver from an unencrypted fallback. Record the actual failure destination and transport instead of treating every successful retry as equivalent. Test this deliberately with fresh names and the chosen encrypted endpoint temporarily blocked on a network you control.


DoH vs DoT and DNSSEC: what is the difference?

DoH and DoT encrypt DNS transport; DNSSEC authenticates signed DNS data. DNSSEC can complement encrypted transport, but it does not conceal DNS questions.

Technology Primary function Transport or mechanism Important boundary
DoH Encrypt DNS exchanges HTTPS, normally port 443 Protects the connection to the HTTPS resolver
DoT Encrypt DNS exchanges TLS, normally TCP port 853 Protects the connection to the TLS resolver
DNSSEC Validate DNS data authenticity and integrity Digital signatures and a chain of trust Does not encrypt queries or responses

Protocol sources: RFC 8484 for DoH, RFC 7858 for DoT, and RFC 4033 for DNSSEC.

Choose a transport your client and network support. Neither encrypted transport establishes that the returned records were DNSSEC-validated; that is a separate validation question.


Which public DoH resolver should you choose?

Choose a public DoH resolver by its privacy policy, required filtering, and compatibility with your client. Use its documented endpoint format rather than guessing a URL.

Resolver Standard DNS wire-format endpoint JSON lookup interface
Cloudflare documentation https://cloudflare-dns.com/dns-query GET https://cloudflare-dns.com/dns-query?name=example.com&type=A with Accept: application/dns-json; name is required.
Google Public DNS documentation https://dns.google/dns-query https://dns.google/resolve

Competitor data: taken from each provider’s official pricing and documentation pages linked in this article, collected on November 10, 2026.

Resolver endpoints were checked against the providers’ official API documentation on November 10, 2026. Cloudflare’s JSON interface documentation specifies its GET parameters and Accept header.

The JSON interfaces are useful for inspecting answers. Browser and operating-system DoH configuration generally needs the standard endpoint or the documented URI template, not a JSON lookup URL.

Before switching, test one public hostname and any internal hostname you need. If latency matters, compare repeated lookups through your current resolver and the candidate resolver on the same connection.


Does DoH work with proxies and VPNs?

DoH can operate alongside proxies and VPNs, but hostname resolution and traffic routing are separate decisions. Identify who resolves the destination before deciding whether DNS follows your intended path.

In curl, socks5h:// delegates destination-hostname resolution to the proxy. It does not establish that the proxy uses DoH upstream. By contrast, socks5:// uses client-side destination resolution. These behaviors are documented in the curl proxy options.

Example: With a SOCKS5 proxy already listening on 127.0.0.1:1080, compare the two resolution choices:

curl --noproxy "" --proxy socks5://127.0.0.1:1080 https://example.com/
curl --noproxy "" --proxy socks5h://127.0.0.1:1080 https://example.com/

The example uses an IP literal for the proxy, avoiding a separate proxy-hostname lookup. Successful page retrieval alone does not reveal the proxy’s upstream DNS transport.

Do not transfer curl’s URL semantics directly to a browser. Chromium’s proxy documentation specifies proxy-side target resolution for SOCKS5 and HTTP proxies. Check bypass rules and direct connections separately. Our SOCKS versus HTTP proxy guide explains the connection models; the SSH SOCKS proxy guide covers a local forwarding setup.

Browser DoH can select a different resolver while its HTTPS traffic still travels through a VPN tunnel. Verify resolver choice and tunnel routing separately. A different resolver name in a leak-check result is insufficient evidence that traffic escaped the tunnel.

Mullvad’s encrypted DNS guidance distinguishes DNS encryption from VPN protection. The practical implication is to inspect the route to the resolver, especially with split tunneling, instead of inferring the route from resolver ownership.


How to test DoH, fallback and DNS leaks

Check resolver answers, application settings, fallback behavior, and network routing separately. A successful HTTPS request to a DNS service proves only that the particular request worked.

Example: Query Google’s documented JSON interface:

curl --fail --silent --show-error 'https://dns.google/resolve?name=example.com&type=A'

The Google Public DNS interface documentation distinguishes this JSON API from standard wire-format DoH. Check Status in the JSON response: 0 means NOERROR, but does not guarantee an A record. For this query, inspect Answer for a record with type 1 and its data value, as documented in Google’s JSON API reference. curl –fail detects HTTP errors, not DNS errors returned in an HTTP 200 response. This command does not enable DoH in your browser.

For a controlled routing check, use this procedure:

  • Record configuration: Note application and OS versions, resolver endpoint, proxy settings, VPN routes, and fallback choices.
  • Use fresh names: Generate each lookup in the application you are testing. For browser DoH, open a URL with a unique hostname under a domain you control in that browser. A lookup from another tool may use a different resolver path.
  • Observe normal operation: Correlate client captures with authoritative DNS logs. Inspect both IPv4 and IPv6 traffic.
  • Introduce an endpoint failure: Temporarily block the configured DoH endpoint on your own test network, including its applicable addresses, and repeat with fresh names.
  • Check the outcome: Record answers, failures, plaintext port-53 traffic, and any alternate resolver connections.
  • Repeat through the proxy or VPN: Compare destination resolution and physical-interface routing separately, then restore the original configuration.

No visible port-53 traffic alone proves neither DoH nor the intended resolver: caching, DoT, and tunneling can also explain its absence. Authoritative logs reveal the recursive service contacting your domain, but not necessarily the transport between your client and that service.

Keep DNS leak checks separate from other browser exposure checks, including WebRTC privacy settings.


Why does DoH fail or conflict with network controls?

DoH can fail because the endpoint is unreachable, its configuration is wrong, or the selected resolver cannot answer names required by your network. Strict failure behavior makes these problems visible as lookup errors.

  • Public sites fail: Verify the endpoint or template, certificate validation, and HTTPS connectivity before changing unrelated settings.
  • Only internal names fail: Check whether those names require an organization’s resolver or split DNS configuration.
  • Filtering changes: Confirm that the selected resolver implements the filtering policy you intend to retain.
  • A captive portal will not open: Complete the network’s sign-in process and then recheck encrypted resolution.
  • The setting is unavailable: Review device management and parental-control policies.

Mozilla documents network-aware protection behavior, while Chrome’s help page describes managed-device and parental-control restrictions. On an administered network, use the approved resolver configuration and explicit policies.

After a change, verify a public hostname, a required internal hostname, and the chosen failure behavior. Fixing ordinary browsing alone does not establish that the full DNS policy is working.


Frequently Asked Questions

What is DNS over HTTPS?

DNS over HTTPS sends DNS questions and answers through an encrypted HTTPS connection. The protection ends at the selected resolver, which still processes the questions.

Should I turn DNS over HTTPS on or off?

Turn it on when the resolver and failure behavior fit your needs. On a managed network, check internal-name resolution and filtering requirements before selecting an independent service.

Does DoH hide browsing from my ISP?

It protects the contents of the encrypted DNS exchange from passive observation. It does not hide all destination addresses or traffic patterns when your website connections travel directly.

Should plaintext DNS fallback be enabled?

Enable it if continued resolution is more important than requiring encrypted DNS during an outage. Disable it if plaintext queries are unacceptable, while accepting that affected lookups may fail.

Is Android Private DNS the same as DoH?

Android Private DNS accepts a provider hostname, not a DoH URL. It supports DoT; Android 11 and later with the relevant Google Play system update can upgrade supported providers to DNS over HTTP/3 (DoH3). The hostname setting alone does not identify the transport in use.

Does socks5h guarantee encrypted DNS?

No. In curl it sends the destination hostname to the SOCKS5 proxy for resolution. The proxy’s upstream DNS transport requires separate verification.

Does a different DNS resolver mean my VPN is leaking?

Not necessarily. An application can contact another resolver through the VPN tunnel. Check the network route as well as the resolver identity.

Does a browser padlock prove DoH is enabled?

No. The website’s TLS connection and its DNS lookup are separate exchanges. Inspect DNS settings and resolution traffic to determine how the lookup occurred.


Check DNS routing alongside your proxy setup

If your workflow needs a proxy, DataImpulse residential proxies are our product and support HTTP, HTTPS, and SOCKS5. Choose the protocol your application needs, then verify destination resolution, traffic routing, and fallback as separate checks.

Last updated: November 10, 2026.


Share article: