Join our Newsletter — 33% off our NHI Course
Architecture & Implementation

Doh And Dot

← Back to Glossary
By NHI Mgmt Group Updated October 30, 2026 Domain: Architecture & Implementation

DoH and DoT are encrypted DNS transport methods. DoH hides DNS inside regular HTTPS traffic, while DoT uses a dedicated TLS channel for queries. Both improve privacy, but each changes how defenders inspect, block, and govern resolution traffic.

What encrypted DNS transport changes

DoH and DoT both protect DNS queries in transit, but they change the control points defenders rely on. Instead of cleartext queries that are easy to inspect on the wire, the resolver relationship is wrapped in HTTPS or TLS, which improves privacy while reducing passive visibility for filtering, logging, and policy enforcement.

That shift matters because DNS is not just a naming utility, it is also a security signal. When the transport is encrypted, organisations need to decide whether to trust endpoint controls, resolver controls, or both, and how much inspection they are willing to lose in exchange for confidentiality.

How DoH and DoT differ operationally

DoH carries DNS inside standard HTTPS sessions, which makes it blend into web traffic and can make simple port-based blocking less effective. DoT uses a dedicated TLS channel for DNS, so it is easier to identify as DNS traffic, but it still removes query contents from passive inspection.

That difference affects governance. DoH can be harder to distinguish from ordinary browser traffic, while DoT usually preserves a clearer protocol boundary. In both cases, the resolver path, client policy, and any enterprise filtering strategy become more important than packet inspection alone.

For organisations standardising encrypted DNS, NHIMG’s Encrypted DNS Enterprise Guide is the best companion for resolver policy, browser handling, and bypass detection.

Why encrypted DNS matters for privacy and control

The privacy benefit is straightforward: observers on the network learn less about the domains a user or device is resolving. That reduces passive surveillance and limits opportunistic collection of browsing metadata, especially on untrusted networks.

The control trade-off is equally important: encrypted DNS can weaken upstream content filtering, malware interdiction, and some forms of network-based detection if the enterprise has not moved those controls elsewhere. The practical question is not whether encrypted DNS is good or bad, but whether the organisation has an intentional policy for where DNS trust is anchored.

Where defenders need to pay attention

Defenders should care about resolver choice, endpoint policy, and the possibility of DNS bypass. A device that uses an approved encrypted resolver is very different from one that tunnels DNS to an external provider the organisation does not monitor or trust.

That is why encrypted DNS programs usually need allowlists, managed browser settings, and visibility into resolver discovery. Without those, DoH and DoT can become shadow pathways that bypass logging or content controls even when the network appears healthy.

Good baselines for those controls are reinforced by NIST SP 800-53 Rev 5 Security and Privacy Controls, especially its access control, audit, and configuration management families.

For a broader control framework view, NIST Cybersecurity Framework 2.0 helps map encrypted DNS decisions to governance, protect, detect, and recover outcomes.

Risk and Threat Considerations

Encrypted DNS can hide resolver abuse as easily as it protects legitimate privacy. If an organisation does not govern which resolvers are allowed, attackers and users alike can route queries around inspection, making command-and-control look like ordinary encrypted web or TLS traffic.

Failure mechanism: The organisation loses cleartext DNS visibility but does not replace it with endpoint policy, resolver controls, or compensating detection, so DNS-based filtering and monitoring become porous.

Impact: Malware, data exfiltration, policy bypass, and unmanaged external resolution paths become harder to spot, investigate, and contain.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5AC-4 — Information Flow EnforcementEncrypted DNS changes where DNS traffic can be permitted or constrained.
AU-2 — Event LoggingDoH and DoT reduce passive DNS visibility, increasing the need for deliberate logging.
CM-7 — Least FunctionalityApproved DNS transports should be limited to what the environment explicitly permits.
Recommendation — Enforce approved DNS flows to known resolvers and deny unsanctioned resolution paths. Log resolver use and DNS policy events so encrypted lookups remain observable. Restrict clients to the minimum DNS transport options required by policy.
NIST CSF 2.0PR.AA-05 — Network Access ControlEncrypted DNS requires governance over which resolvers devices may use.
DE.CM-09 — Network MonitoringDoH and DoT affect what network monitoring can see and validate.
Recommendation — Control resolver access so endpoints use only sanctioned DNS services. Monitor DNS-related network behaviour for bypass, misuse, and policy drift.

Practitioner Guidance

Why practitioners should care: DoH and DoT are not just transport choices, they are trust decisions about where DNS visibility and enforcement will live. Treat them as part of endpoint, resolver, and network policy together rather than as an isolated browser or OS setting.

What to watch for: Watch for unmanaged resolvers, inconsistent browser defaults, and devices that quietly fall back to external DNS paths. Those are the conditions that most often turn encrypted DNS from a privacy feature into a governance gap.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org