What is a network port? TCP, UDP and open ports

A network port is a number used by transport protocols such as TCP and UDP to direct traffic to the right service. Together, a protocol, IP address and port form a practical endpoint for a connection. A port is a logical identifier, not a physical socket on a router.

Numbers and common uses

Port numbers are 16-bit values from 0 to 65535. IANA groups them into system ports 0–1023, user ports 1024–49151 and dynamic or private ports 49152–65535. HTTP commonly uses TCP 80 and HTTPS TCP 443, but a service can be configured on another number.

TCP and UDP have separate port spaces. The same numeric port can therefore serve different purposes for each protocol. A client usually chooses a temporary source port when connecting to a server’s listening destination port. Seeing a high-numbered client port is normal and does not imply a public service is open.

What “open” means

For TCP, an external test may call a port open when it can complete a connection to a listener. A closed response, dropped packets or a timeout have different meanings, and a firewall can make them hard to distinguish. UDP testing is less conclusive because a silent service may simply not respond to the probe.

A program listening on a local address is not automatically reachable from the Internet. The host firewall, router port forwarding, provider filtering and carrier-grade NAT all affect the result. Check the listening address and protocol first, then test from outside the local network.

Opening ports responsibly

Expose only services you need. Configure authentication, keep software updated and restrict source addresses where practical. A successful connection test says nothing about whether the application is secure or correctly configured. Conversely, a failed test does not identify the precise blocking layer by itself.

If a service is intended only for local use, bind it to loopback or a private interface and avoid unnecessary forwarding. Record the expected protocol and destination port before changing firewall rules. Recheck after the change from a separate network and remove obsolete rules when the service is retired.

When documenting an issue, record the service name, transport protocol, destination port and test location. A result obtained inside the home network may differ from a test over mobile data because the router can handle its own public address differently. Repeat from a genuinely external network before requesting a provider change.