Port
NetworkingPort is a numbered endpoint on a device that identifies which network service or application should receive incoming traffic. Used with IP addresses and transport protocols like TCP or UDP, ports let many services share one server while staying logically separated. Common examples include HTTP on 80, HTTPS on 443, and SSH on 22, which are essential for hosting access and web delivery.
How It Works
A port is part of the transport-layer addressing used by TCP and UDP. When a client connects to a server, it targets an IP address plus a port number (for example, 203.0.113.10:443). The server OS uses that port to route the connection to the correct process that is listening, such as a web server (Apache or Nginx), a database service, or an SSH daemon. This is how one machine can host multiple networked services at the same time without confusion.
Ports range from 0 to 65535. Many well-known services conventionally use specific ports (like 80/443 for web traffic), but administrators can run services on alternative ports when needed. Firewalls and security groups control which ports are reachable from the internet, while local binding rules determine whether a service listens on all interfaces or only on localhost. In hosting, port exposure is often limited to reduce attack surface.
Why It Matters for Web Hosting
Port availability affects what you can run and how users reach it. Shared hosting typically exposes only web ports (80/443) and a few management ports, while VPS and dedicated servers usually let you open custom ports for apps, APIs, game servers, or mail services. When comparing plans, check whether you can manage firewall rules, whether inbound ports are restricted, and whether control panels or managed services require specific ports to function.
Common Use Cases
- Serving websites over HTTP (port 80) and HTTPS (port 443)
- Remote administration via SSH (port 22) or SFTP over SSH
- Email delivery and retrieval using SMTP, IMAP, or POP3 (often with TLS variants)
- Database access for internal services (commonly restricted to private networks)
- Running custom applications or APIs on nonstandard ports behind a reverse proxy
- Controlling exposure with firewalls, security groups, and port forwarding
Port vs Protocol
A port is a numeric destination used by a transport protocol, while a protocol defines the rules for communication. For example, HTTPS is an application protocol typically carried over TCP and commonly reached on port 443. The same port number can be used by different protocols (TCP 443 vs UDP 443), and changing a port does not change the protocol itself, only where the service is reachable.