RFC 8484 defines DNS over HTTPS (DoH), while RFC 9076 examines DNS privacy risks. This is a briefing on established documents, not a claim that a new standard appeared today. The useful question is which part of your traffic encryption protects.

A DNS resolver translates a name into a network address. Encrypting that request limits exposure of the lookup on its path to the resolver, but the selected resolver still handles it. Moving trust to a provider is not the same as eliminating trust; inspect the provider and its privacy policy.

The protocol protects the path to the chosen resolver, not every later connection. Before adopting a service, check its logging and retention policy, who operates it, and whether the setting applies to one application or the whole device. Those are separate questions from encryption strength.

DoH does not conceal everything about a connection, protect every application on the device, or certify that a shop is honest. For a shared or managed computer, follow network policy. For a personal browser, choose a provider deliberately and verify that normal sites and local services still work.