Skip to content
statance
MenuClose
← All ports

Port 67: DHCP server

Medium risk

UDP port 67 is where DHCP servers listen for address requests. Clients send from and receive replies on UDP port 68. It should not be reachable from the public internet.

Port
67
Protocol
UDP
Service
DHCP server
Expose to internet?
No
Also used by
ISC DHCP, Kea, dnsmasq, Windows DHCP Server

Is port 67 safe to open?

DHCP only makes sense on a local network, so it should never be reachable from the internet. A DHCP server answering on the wrong interface can hand out addresses to networks it does not belong to. On a LAN, a rogue DHCP server can redirect clients to an attacker’s gateway or DNS server.

How to secure DHCP server

  • Bind the DHCP server to the internal interface only (dnsmasq interface=, ISC DHCP interface list).
  • Block UDP 67 and 68 on internet-facing interfaces.
  • Enable DHCP snooping on managed switches to stop rogue servers.

Check if port 67 is open

Linux: what is listening on this port

sudo ss -ulpn | grep ':67 '

Windows (PowerShell): what is listening

Get-NetUDPEndpoint -LocalPort 67

From another machine: is it reachable

sudo nmap -sU -p 67 HOST

Restrict port 67 in the firewall

Replace 10.0.0.0/8 with the network or address that needs access. Docker publishes container ports through its own iptables rules, which bypass ufw; bind published ports to 127.0.0.1 (-p 127.0.0.1:67:67) instead of relying on the host firewall.

ufw: allow only your private network, deny everyone else

sudo ufw allow from 10.0.0.0/8 to any port 67 proto udp sudo ufw deny 67/udp

firewalld: allow one source network only

sudo firewall-cmd --permanent --remove-port=67/udp sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="10.0.0.0/8" port port="67" protocol="udp" accept' sudo firewall-cmd --reload

iptables

sudo iptables -A INPUT -p udp --dport 67 -s 10.0.0.0/8 -j ACCEPT sudo iptables -A INPUT -p udp --dport 67 -j DROP

Windows Firewall (PowerShell, as Administrator)

New-NetFirewallRule -DisplayName "Block 67 from internet" -Direction Inbound -Protocol UDP -LocalPort 67 -RemoteAddress Internet -Action Block

Monitor port 67

Run a TCP port monitor against your public IP on port 67: here, a failed connection is the healthy result, so you know the firewall is still doing its job. On Linux, the Statance agent also reports every listening port on the server. TCP port monitoring.

Related ports

Port 53DNSMedium risk
Port 69TFTPHigh risk

FAQ

What is the difference between port 67 and 68?

The DHCP server listens on UDP 67 and the client listens on UDP 68. Both are needed on the local network for DHCP to work.

What is port 67 used for?

UDP port 67 is where DHCP servers listen for address requests. Clients send from and receive replies on UDP port 68. It is also used by ISC DHCP, Kea, dnsmasq, Windows DHCP Server.

Is it safe to open port 67?

Not to the public internet. DHCP only makes sense on a local network, so it should never be reachable from the internet. A DHCP server answering on the wrong interface can hand out addresses to networks it does not belong to. On a LAN, a rogue DHCP server can redirect clients to an attacker’s gateway or DNS server.

Is port 67 TCP or UDP?

DHCP server uses UDP on port 67.

How do I check if port 67 is open?

On the server, run sudo ss -tulpn | grep ':67 ' (Linux) or Get-NetTCPConnection -LocalPort 67 (Windows) to see what is listening. From another machine, run nc -zv HOST 67 or Test-NetConnection HOST -Port 67.

All ports →

Know the moment a port stops answering.

TCP, HTTP, DNS and SSL checks from six regions, plus server metrics from a one-line agent.