Port 67 — DHCPv4 server

UDPSystem

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:67

Windows PowerShell

Get-NetUDPEndpoint -LocalPort 67

Sources 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.

ISC DHCP

Internet Systems Consortium DHCP server

Reference link ↗

Windows DHCP Server

Windows built-in DHCP server

Reference link ↗

DHCP Server

DHCPServer

Reference link ↗

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

Quick Info

Port
67
Protocol
UDP
Categories
System
Usage Status
3 software in use

Related Ports

Port 68UDP
→
Port 53TCP/UDP
→

Need Help?

If you find incorrect information or need to add more, please submit correction information.

Submit Correction