What Port Numbers Are For

A single device often runs several network services at once — a web server, a mail server, and a file share. Port numbers let one IP address host many services by giving each a separate doorway.

The IP address gets the packet to the right host; the port number gets it to the right application on that host.

Combine an IP address with a port number and you get a socket, the unique endpoint of a connection. For example, 192.168.1.10:443 is a socket for HTTPS on that host.

A connection is identified by the pair of sockets — source and destination — which is how a host keeps thousands of simultaneous conversations separate.

Port numbers are 16-bit values ranging from 0 to 65535. That gives 65,536 possible ports per protocol (TCP and UDP each have their own full range).

The huge range ensures a host never runs short of ports for the many connections it may handle at the same time.

Ports 0 to 1023 are the well-known ports, reserved for common, standardized services. HTTP uses 80, HTTPS uses 443, and SSH uses 22.

These assignments are managed by IANA (Internet Assigned Numbers Authority) so that clients always know where to find a given service by default.

Ports 1024 to 49151 are registered ports, assigned to specific applications by request, such as 3306 for MySQL or 3389 for RDP (Remote Desktop Protocol).

They are less rigidly controlled than well-known ports but still help avoid clashes between widely used applications.

Ports 49152 to 65535 are dynamic or ephemeral ports. The operating system assigns one temporarily to the client side of a connection.

When your browser connects to a web server on port 443, your machine uses a random high ephemeral port as its source, which is released when the connection ends.

Every connection has two ports. The destination port identifies the service being reached (like 443 for HTTPS). The source port is the client’s ephemeral port for that conversation.

This pairing lets a host distinguish many connections to the same service, since each uses a different source port.

Default ports let clients connect without specifying a number. Typing a web address quietly uses port 80 or 443. Running a service on a non-standard port means clients must be told the number explicitly.

Some admins change defaults for mild security through obscurity, but firewalls and rules must then be updated to match.

Firewalls allow or block traffic largely by port number. A rule permitting TCP 443 lets HTTPS through while blocking other services.

Closing unused ports reduces a host’s attack surface. Understanding ports is therefore central to both connectivity and security configuration.

A service that is ready to accept connections is said to be listening on its port, and that port is then considered open. A closed port has no service waiting.

Attackers scan for open ports to find services to target, so technicians audit which ports are open and shut down any that are not needed.

Port numbers are the addressing layer above IP, directing data to the correct application. They make multiplexing many services on one host possible.

With the concept of ports clear, you are ready to learn the specific port numbers of the everyday protocols covered in the next lessons.

Recall the port ranges.

You learned what port numbers are for.

• Ports let one IP host many services; IP+port = a socket.
• Range is 0 to 65535 (16-bit), per transport protocol.
• Well-known: 0-1023; registered: 1024-49151; dynamic: 49152-65535.
• The destination port names the service; the source port is the client’s ephemeral port.
• Firewalls allow or block traffic largely by port.