Port67— DHCPv4 server
DHCPv4 servers use UDP 67 and clients use UDP 68. This is an address-lease protocol, not a website to open in a browser.
Registry assignments, software defaults and local listeners are different things. A port number alone does not identify or secure a service.
Configuration and troubleshooting
Check the server interface, address pool and lease logs. Across subnets, inspect the DHCP relay; a TCP connectivity test does not validate DHCP.
Important limitations
Do not start an unplanned DHCP server on a production network. Windows DHCP documentation comes from Microsoft, not the ISC project.
Read-only checks: run on the server host
Choose the commands for your OS. Check TCP and UDP separately. No result is not a lasting availability guarantee; inspect host and container separately.
Linux
sudo ss -lunp 'sport = :67'macOS
sudo lsof -nP -iUDP:67Windows PowerShell
Get-NetUDPEndpoint -LocalPort 67Sources and review
Sources checked on:
This review covers the explanations and sources on this page, not your device or every community software entry below.
Software Using This Port (3 software)
Community software entries: links are references, not individual verification.
Usage Suggestions
- Before using port 67, please confirm it is not occupied by other services
- If you encounter port conflicts, consider using other ports or stopping the occupying service
Frequently asked questions
What is port 67 used for?
Port 67 sits in the System category. This page lists the registered purpose and the software commonly associated with it; to see what is actually listening on a specific machine, check the process with ss/netstat.
Is port 67 TCP or UDP?
The registered protocol on this page is UDP. The same number behaves independently on each protocol: TCP may be listening while UDP is idle, so check them separately.
How do I check if port 67 is in use?
On Linux: sudo ss -tlnp 'sport = :67' for an exact port match. On macOS: sudo lsof -nP -iTCP:67 -sTCP:LISTEN. On Windows PowerShell: Get-NetTCPConnection -LocalPort 67 -State Listen. A listener counts as confirmed only when you can see the bind address and process name; without root/admin you will not see other users' processes.
Is port 67 secure? Should I open it in my firewall?
A port number has no inherent security — it depends on whether the listening service is correctly configured and whether it needs exposure at all. Keep loopback/internal-only services firewalled; where public access is required, pair it with source restrictions, VPN or authentication. The caution section on this page lists port-specific risks.
Quick Info
- Port
- 67
- Protocol
- UDP
- Categories
- System
- Usage Status
- 3 software in use
Related Ports
Need Help?
If you find incorrect information or need to add more, please submit correction information.
Submit Correction