UDP Ports - Source Port, Destination Port, and Common Services
UDP ports are 16-bit numbers that identify applications or services on each endpoint. They make it possible for many UDP-based services to share the same IP address.
Key Takeaways
UDP source and destination ports are each 16 bits.
Destination ports usually identify the service being contacted.
Source ports usually identify the client-side conversation.
UDP port numbers are useful for recognizing DNS, DHCP, NTP, and other traffic.
How UDP ports work
A UDP header begins with source port and destination port. Together with source IP, destination IP, and protocol, these ports identify a flow or conversation at the transport layer.
Common UDP services
DNS commonly uses UDP port 53, DHCP uses ports 67 and 68, NTP uses port 123, and many real-time applications choose UDP to reduce transport overhead and latency.
How to analyze UDP ports
Check the destination port first to infer the service. Then use the source port and payload structure to decide whether the packet is a client request, server response, broadcast, multicast, or application-specific datagram.
Practical Reference
| Item | Value | Analysis Note |
|---|---|---|
| Port size | 16 bits | Range is 0 through 65535. |
| Destination port | Service identifier | Often the first clue for payload protocol. |
| Source port | Sender endpoint | Often ephemeral for client traffic. |
| No connection state | UDP is connectionless | Ports do not imply a TCP-like session. |
FAQ
Are UDP and TCP port numbers the same namespace?
They use the same numeric range but belong to different transport protocols. UDP port 53 and TCP port 53 are separate transport endpoints.
Can a UDP source port be zero?
UDP source port can be zero in IPv4 to indicate no reply port, though it is uncommon in ordinary application traffic.