Port 53: DNS
Port 53 is used by DNS over TCP and UDP. Port 53 is DNS. It appears in the study tables for 200-301, 220-1201, N10-009, SY0-701.
What runs on port 53
Domain Name System (DNS) uses TCP/UDP at the application layer. Name resolution queries and replies, with TCP 53 for large responses and zone transfers. It starts unencrypted and can be upgraded with TLS.
Port 53 is DNS. Ordinary lookups use UDP because the answer fits in one small packet, and the protocol falls back to TCP for large answers and for zone transfers between name servers.
Secure alternative and common mix-ups
The study tables do not list a separate secure replacement for DNS. Where it has to cross a network you do not control, restrict who can reach it and carry it inside a VPN.
Blocking TCP 53 breaks zone transfers and some large responses, such as those from signed zones, even though most lookups keep working. DNS over TLS and DNS over HTTPS are separate, encrypted transports with their own ports.
Check port 53 on your own network
To test a remote host from Windows, run Test-NetConnection with the host name and -Port 53. From Linux or macOS, run nc -vz host 53. To see what is listening on the machine itself, use ss -tulpn on Linux or netstat -ano on Windows and look for :53.
UDP has no handshake, so a silent probe does not prove the port is closed. No reply can mean the port is open and the service ignored the probe, or that a firewall dropped it. A scanner such as nmap with -sU reports that state as open or filtered.
Exam objectives that include it
These are the objectives whose tables list port 53. The same row appears in the cheat sheet for each exam.
Related ports
Learn 53 together with these. They are its pair, its secure counterpart or a service that sits under the same objective.
Questions
The port number does not decide that. DNS on port 53 is only as safe as its configuration, how far it is exposed and how current the software is.
Keep going with the ports quiz and the cheat sheets.
Free plan, no card.