DNS
Domain Name SystemBest for: Managed and local networks
- example.com?, from You
- 203.0.113.10, from Resolver
Compare protocols
Best for: Managed and local networks
Best for: Public Wi-Fi and private lookups
Classic DNS sends name lookups as plain text on UDP port 53, so the network you are on can read and even change them. DNS over HTTPS (DoH) puts the same question and answer inside an HTTPS connection on port 443, so they are encrypted and look like normal web traffic. The resolver you pick can still see your lookups.
Tick everything that is true for you.
Your pick shows here
Tick one or more lines and we weigh them for you.
| What differs | DNS | DNS over HTTPS |
|---|---|---|
| Port | 53 (UDP, TCP for large answers) | 443 (TCP, or QUIC with HTTP/3) |
| Encrypted | No | Yes |
| Who can read lookups | Anyone on the path and the resolver | Only the resolver |
| Can be changed on the way | Yes | No, protected by TLS |
| First lookup | One quick round trip | Needs an HTTPS connection first, then reuses it |
| Network filters | Easy for a school or office to apply | Can bypass local filters, which some admins block |
| Standard | RFC 1034, RFC 1035 | RFC 8484 |
Each page plays the real packets on a map, step by step, with every header explained.
Each line describes one of the two. Which one?
Question 1 of 7
Port
53 (UDP, TCP for large answers)
Both encrypt DNS. DNS over TLS (DoT, RFC 7858) uses its own port, 853, so networks can spot and block it. DoH uses 443 and blends in with web traffic.
It hides the lookups. The provider can still see the IP addresses you connect to and often the site name in the TLS handshake, unless Encrypted Client Hello is in use.
No. DNSSEC signs answers so you can tell they are genuine, but does not hide them. DoH hides lookups but does not prove the answers came from the domain owner. They work well together.
The first lookup can be a little slower while the HTTPS connection opens. After that the connection is reused, and lookups are about as fast as classic DNS.