Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
DoT encrypts DNS queries inside a TLS session on port 853. It gives the same confidentiality as DoH while remaining visible to network operators as a distinct protocol.

What Is DNS over TLS?
DNS over TLS, defined in RFC 7858 in May 2016, does one thing: it carries ordinary DNS messages inside a TLS session rather than over plaintext UDP. The query format is unchanged, the resolver behaviour is unchanged, and the only visible difference is the destination port — 853 instead of 53 — and the fact that nobody on the path can read or alter the exchange.
The client opens a TCP connection to port 853 on the resolver, completes a TLS handshake, and then sends standard DNS messages prefixed with a two-byte length field, exactly as DNS over TCP has always worked. The connection is kept open and reused for subsequent queries, which removes most of the handshake cost after the first lookup. RFC 7858 recommends an idle timeout on the order of ten seconds, with both ends free to negotiate longer.
Authentication comes in two profiles. In the opportunistic profile the client encrypts if it can and falls back to plaintext if it cannot, which protects against passive observation but not against an active attacker who blocks port 853. In the strict profile the client is configured with the resolver’s name and validates the certificate against it, refusing to resolve at all if validation fails. Strict is the only profile that resists an on-path attacker, and it is what Android’s Private DNS setting uses when you enter a hostname.
The cryptographic protection is equivalent. The difference is entirely about who can see and control the traffic.
| DNS over TLS | DNS over HTTPS | |
|---|---|---|
| Port | 853, dedicated | 443, shared with all web traffic |
| Network visibility | Identifiable as DNS | Indistinguishable from HTTPS |
| Blocking by an operator | Straightforward | Requires endpoint lists |
| Typical implementer | Operating systems, resolvers | Browsers, applications |
| Overhead | Lower; no HTTP layer | Slightly higher |
That visibility is why many network and security teams prefer DoT inside a managed estate. An operator can permit port 853 to the corporate resolver and deny it elsewhere, producing encrypted resolution that is still enforceable. With DoH the same enforcement requires maintaining a list of public endpoints that will always be incomplete. The flip side is that on a censoring network DoT is trivially blocked, which is exactly why privacy-focused browsers chose HTTPS instead.
Android has supported DoT as Private DNS since Android 9 in 2018, and it is enabled in automatic mode by default, meaning phones silently upgrade to encrypted resolution when the configured resolver supports it. Linux systems using systemd-resolved support it through DNSOverTLS=. Resolver software including Unbound, Knot Resolver, BIND, and dnsdist all terminate DoT, as do the major public resolvers. On Windows, the operating system has favoured DoH, so a mixed estate typically ends up running both.
The pattern that works is simple to state. Run your own resolver, terminate DoT on it with a certificate whose name matches what clients are configured to expect, and keep full query logging there. Configure managed devices with the resolver hostname in strict mode so that a downgrade attempt fails loudly. Then block outbound 853 and 53 to everything except that resolver, and apply the browser policies that prevent applications choosing their own DoH provider.
Two operational details are easy to miss. Certificate renewal on the resolver now matters for name resolution itself, so an expired certificate in strict mode means clients cannot resolve anything — automate it and monitor expiry. And because DoT is TCP-based with long-lived connections, a resolver that previously handled stateless UDP needs sizing for concurrent connections and file descriptors rather than packets per second.
DoT protects the query in transit. It does not authenticate the answer the resolver received from upstream, which is what DNSSEC is for, and the two are complementary rather than alternatives. Our Infrastructure and Architecture Review Services cover resolver architecture, logging, and the policy that keeps clients using it.
Inside a managed estate, DoT is usually easier to govern because it runs on a dedicated port you can permit to your own resolver and deny elsewhere. DoH is harder to control but is what browsers implement. Most organisations end up supporting both on their resolver and enforcing destination through device policy rather than protocol choice.
No, they protect different things. DoT encrypts and authenticates the link between the client and its resolver, so nobody on that path can read or alter queries. DNSSEC lets the resolver verify that the data it received from authoritative servers is genuine. Running both gives you a private channel carrying verified answers.
It is Android’s DoT implementation, available since Android 9. In automatic mode the device opportunistically tries port 853 against its configured resolver. If you enter a hostname instead, it uses the strict profile, validating the resolver’s certificate and refusing to resolve if validation fails. Entering your corporate resolver hostname is a simple way to enforce encrypted resolution on mobile devices.
It changes the shape of the load. TLS handshakes cost CPU, and persistent TCP connections consume memory and file descriptors in a way that stateless UDP does not. Connection reuse keeps the per-query cost low once established. Size for concurrent connections rather than packets per second, and enable session resumption to reduce handshake overhead.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.