Port 53: DNS
Domain name resolution.
- Port
- 53
- Protocol
- TCP/UDP
- Service
- DNS
- Exposure
- Expose only with access controls
What is port 53 used for?
Answering DNS queries (UDP) and zone transfers or large answers (TCP).
Is it safe to expose port 53 to the internet?
Public authoritative servers must listen; recursive resolvers must not be open to the world (they get used for amplification attacks). Restrict zone transfers.
If port 53 seems closed or unreachable
- Check that the DNS service is running and listening on port 53, not only on 127.0.0.1.
- Check the firewall on the host itself (Windows Defender Firewall, iptables, nftables, ufw) for a rule that allows TCP 53.
- If the host is behind a router, confirm the forwarding rule points to the correct internal address and that your internet provider does not use carrier-grade NAT.
- Test from outside your own network. A port can be open locally and blocked at the edge, or the other way round.
Using port 53 safely
Port 53 can be exposed when the host exists to provide this service, but add controls: restrict source addresses where you can, require strong authentication and encryption, and monitor the logs for repeated failures.
Check whether port 53 is open on your host
The check connects from our server, so it shows what the internet can reach.
Open the port checker