What Is a Port?

Acutis · plain-English network help · updated June 2026

What is a port, in plain English?

A port is a numbered doorway on a device's IP address. If an IP address is the street address of a building, a port is the specific door or apartment number inside it. One device has a single IP address but thousands of possible ports, and each running program listens on its own port so incoming data reaches the right place.

This is what lets a single server do many jobs at once. A computer at 203.0.113.5 can host a website, run an email service, and accept remote logins all at the same time — because each of those services answers on a different port number. When your traffic arrives, the device looks at the port to decide which program should handle it.

Well-known ports you'll see

Port numbers run from 0 to 65535. The lowest range, 0 to 1023, is reserved for "well-known" services that almost everyone uses. A few worth recognizing:

• Port 80 — HTTP, the original unencrypted web traffic.
• Port 443 — HTTPS, the encrypted web. This is where nearly all modern browsing happens.
• Port 22 — SSH, used for secure remote logins and command-line access to servers.
• Port 25 — SMTP, the protocol mail servers use to send email between each other.
• Port 53 — DNS, the lookups that turn names like example.com into IP addresses.

Because these assignments are standard, your browser knows to try port 443 when you type https:// without you ever specifying it. The convention is what makes the internet "just work."

TCP and UDP — two ways to use a port

Ports come in two flavors, and the same number can mean different things depending on which is used.

• TCP is the reliable, ordered delivery method. It sets up a connection, confirms every packet arrived, and resends anything lost. Web pages, email, and file transfers use TCP because correctness matters more than raw speed.
• UDP is the fast, fire-and-forget method. It sends data without confirming receipt, which is ideal for live video, voice calls, and online games where a dropped packet is better than a delayed one.

So "port 443/TCP" and "port 443/UDP" are technically separate channels. Most services pick one, and the firmware on your router treats them independently.

What port forwarding does

By default, your router blocks unsolicited traffic coming in from the internet. That's a good thing — it means a stranger can't reach the devices inside your home. But sometimes you want the outside world to reach a specific device, and that's exactly what port forwarding sets up.

Port forwarding tells your router: "when traffic arrives on this port, send it to this specific device inside the network." You're punching a deliberate, named hole through the router's default wall. Common reasons people do it:

• Hosting a game server. Friends connecting to a Minecraft or other self-hosted server need a forwarded port to reach the machine running it.
• Remote access. Reaching a home computer, NAS, or security-camera system from outside the house.
• Self-hosting a service. Running your own website, file server, or VPN endpoint at home.

The security trade-off

Port forwarding is powerful, but every forwarded port is a door you've deliberately left open. Anything on the internet can now knock on it, and automated scanners knock constantly. If the service behind that port has a weak password or an unpatched flaw, you've handed attackers a direct route in.

The safer approach is to forward only the ports you truly need, use strong credentials on whatever is listening, keep that software updated, and close the forward as soon as you stop using it. For remote access, many people now prefer a VPN over an open forwarded port — it gives one strongly protected entry point instead of several exposed ones.