TCP and UDP ports are 16-bit numbers (0–65535) that identify specific processes or services on a networked device. Think of an IP address as a building's street address, and the port number as a specific apartment or office within that building. Ports allow multiple network services to run simultaneously on a single device without interfering with each other.

TCP (Transmission Control Protocol) is connection-oriented — it establishes a reliable connection, guarantees data delivery, and maintains packet order. Ideal for web browsing (HTTP/HTTPS), email, and file transfers.

UDP (User Datagram Protocol) is connectionless — it sends data without establishing a connection, offering lower latency but no delivery guarantee. Perfect for real-time applications like streaming, VoIP, DNS queries, and online gaming where speed matters more than perfect reliability.

The IANA (Internet Assigned Numbers Authority) divides ports into three ranges:
• Well-known ports (0–1023): Reserved for system services and widely-used protocols (e.g., HTTP on 80, HTTPS on 443, SSH on 22). Require root/administrator privileges on most systems.
• Registered ports (1024–49151): Assigned to user applications and services upon request (e.g., MySQL 3306, PostgreSQL 5432, Redis 6379).
• Dynamic/Private ports (49152–65535): Used for ephemeral connections, temporary client-side ports, and custom applications. Not officially registered.

On Linux/macOS: Use netstat -tuln, ss -tuln, or lsof -i :PORT to list listening ports. To test connectivity: nc -zv HOST PORT or telnet HOST PORT.
On Windows: Use netstat -an in Command Prompt, or Test-NetConnection HOST -Port PORT in PowerShell.
Online tools: Various port-checking websites can test if a port is reachable from the internet.

HTTP uses port 80 (TCP) by default for unencrypted web traffic.
HTTPS uses port 443 (TCP) for encrypted TLS/SSL web traffic.
Common alternative HTTP ports include 8080 and 8000 (often used for development servers and proxies). Alternative HTTPS ports include 8443.

Generally, only one service can bind to a specific port on a given IP address at a time. However, the same port number can be used by different services if they use different protocols (TCP vs UDP) or different IP addresses on a multi-homed system. Some advanced setups use socket sharing, but this is uncommon in standard configurations.

Some protocols require both TCP and UDP for different aspects of their operation. For example, DNS (port 53) uses UDP for standard queries (fast, low overhead) but falls back to TCP for zone transfers and large responses (over 512 bytes). Similarly, OpenVPN (1194) and SIP (5060) may use both protocols depending on the configuration.

Linux/macOS: sudo lsof -i :PORT or sudo ss -tulnp | grep :PORT — these show the PID and process name.
Windows: netstat -ano | findstr :PORT to get the PID, then tasklist | findstr PID to identify the process. Alternatively, use Resource Monitor.
Once identified, you can terminate the process if needed using kill PID (Linux/macOS) or Task Manager (Windows).