What is DNS over HTTPS?
DNS over HTTPS (DoH) transports domain-name queries to a DNS resolver over HTTPS.
How it works and where it is used
Plain DNS queries can be observed on a network; DoH encrypts transit between client and chosen resolver. It does not hide every aspect of browsing: destination IPs, browser behavior and resolver logs are separate issues. The chosen provider can depend on OS and browser settings.
Limits, safety and selection criteria
Enterprise filtering and internal domains can require special configuration. Resolver trust, logging policy and failure fallback matter. DoH is not DNSSEC: the former protects transport privacy, while the latter authenticates particular DNS answers. On café Wi-Fi, ordinary DNS domain queries may be observable, while DoH hides query contents on that network link. The chosen resolver may then see more of a user’s queries, so its privacy and retention policies matter. A browser might use a resolver different from the operating system, unexpectedly affecting parental filters or corporate internal names. During troubleshooting, identify whether the browser, OS or network resolver answered. HTTPS for a website and DoH for name lookup protect different communication stages; neither is an anonymity service.