What is a port number?
A port number is used alongside an IP address to direct network traffic to the right application or service on a device. While the IP address identifies the device itself, the port number helps identify the specific function or service that should receive the data.
For example, a server may use one port for web traffic, another for secure remote access, and another for streaming or signalling. This is why ports are a basic but important part of network design, firewall rules, and troubleshooting.
TCP vs UDP
TCP and UDP are both transport layer protocols, but they behave differently. TCP is generally used when reliable, ordered delivery matters, while UDP is often preferred when low latency is more important than guaranteed delivery.
| Feature | TCP | UDP |
|---|---|---|
| Connection type | Connection-oriented | Connectionless |
| Reliability | Reliable delivery with acknowledgements and retransmission | No guaranteed delivery |
| Order of packets | Packets arrive in order | Packets may arrive out of order |
| Speed | Usually slower due to error checking and control | Usually faster with lower overhead |
| Typical uses | Web traffic, email, file transfer, remote login | Streaming, VoIP, DNS, live media transport |
| Best suited for | When accuracy and complete delivery matter | When speed and low latency matter more |
Well-known ports and dynamic ports
Port numbers are normally grouped into ranges. Understanding these ranges is useful when working with servers, clients, media devices, managed switches, and firewall policies.
| Port range | Name | Typical purpose |
|---|---|---|
| 0–1023 | Well-known ports | Reserved for common services such as HTTP, HTTPS, DNS, SSH, SMTP, and FTP. |
| 1024–49151 | Registered ports | Often used by applications, platforms, and vendor-specific services. |
| 49152–65535 | Dynamic / private ports | Usually used for temporary client sessions, ephemeral connections, and dynamic media flows. |
Common TCP and UDP ports
The table below lists some widely used ports and the services they are commonly associated with. In practice, applications can be configured differently, but these are standard reference points.
| Port | Protocol | Service / typical use |
|---|---|---|
| 20 / 21 | TCP | FTP – file transfer |
| 22 | TCP | SSH – secure remote access |
| 23 | TCP | Telnet – legacy remote terminal access |
| 25 | TCP | SMTP – email transfer |
| 53 | UDP / TCP | DNS – name resolution |
| 67 / 68 | UDP | DHCP – automatic IP addressing |
| 80 | TCP | HTTP – web traffic |
| 110 | TCP | POP3 – email retrieval |
| 123 | UDP | NTP – time synchronisation |
| 143 | TCP | IMAP – email access and management |
| 161 / 162 | UDP | SNMP – monitoring and traps |
| 389 | TCP / UDP | LDAP – directory services |
| 443 | TCP | HTTPS – encrypted web traffic |
| 445 | TCP | SMB – file and printer sharing |
| 5060 / 5061 | UDP / TCP | SIP – signalling for voice and media sessions |
| 554 | TCP / UDP | RTSP – streaming session control |
| 1935 | TCP | RTMP – legacy streaming transport |
Ports often seen in media and streaming environments
IP-based media systems often rely on timing, signalling, control, and real-time transport protocols that go beyond standard office traffic. These are some of the ports and services commonly encountered in media, streaming, and broadcast-adjacent workflows.
| Port | Protocol | Service | Typical role in media environments |
|---|---|---|---|
| 53 | UDP / TCP | DNS | Supports name resolution for devices, controllers, and services. |
| 123 | UDP | NTP | Provides general network time synchronisation. |
| 319 | UDP | PTP Event Messages | Used by Precision Time Protocol for highly accurate timing exchange. |
| 320 | UDP | PTP General Messages | Used by Precision Time Protocol for supporting synchronisation messaging. |
| 5004 | UDP | RTP | Commonly associated with real-time audio and video transport. |
| 5005 | UDP | RTCP | Used for control data, quality feedback, and reporting. |
| 5353 | UDP | mDNS | Sometimes used for local service discovery in IP-based environments. |
| 5060 | UDP / TCP | SIP | Session signalling for voice and some media workflows. |
| 5061 | TCP | SIP TLS | Encrypted SIP signalling. |
| Dynamic range | UDP | RTP media ports | Many media systems use configurable or dynamically assigned UDP ports for actual audio and video flows. |
Why this matters in real networks
Understanding ports is helpful when planning switch policies, QoS behaviour, firewalls, VLANs, ACLs, remote contribution links, and device interoperability. Even a simple table like this can make troubleshooting much easier when you need to understand what type of traffic a system is trying to send or receive.
In media and broadcast-adjacent environments, the challenge is often not just whether traffic exists, but whether timing, delivery method, and network behaviour are appropriate for the application. That is where a practical understanding of TCP, UDP, and related ports becomes useful.