Common Service Ports (80, 443, 22, 25, 53)
- Networking Fundamentals & OSI Model
- TCP/IP Model
- Network Topologies
- IP Addressing & Subnetting
- Routing Algorithms & Protocols
- Switching Concepts
- Transport Layer Protocols (TCP & UDP)
- Application Layer Protocols
- Network Security & Firewalls
- Wireless Networking & Wi-Fi
- Network Address Translation (NAT)
- DNS Deep Dive
- Congestion Control & Flow Control
- Error Detection & Correction
- Network Devices
- VPN & Tunneling
- Load Balancing & CDN Networking
- Socket Programming
- Network Troubleshooting Tools
- Physical Layer & Transmission Media
- Data Link Layer & MAC Addressing
- Ethernet Protocol
- ARP (Address Resolution Protocol)
- ICMP Protocol
- Unicast, Multicast, Broadcast and Anycast
- Proxy Servers
- Port Numbers Reference
- Network Performance Metrics
- Quality of Service (QoS)
- Software-Defined Networking (SDN)
- HTTP/2 and HTTP/3 Overview
- 5G and Mobile Networks
- IoT Networking Basics
- VoIP Networking Basics
The Ports You'll Encounter Constantly
| Port | Service | What it's for |
|---|---|---|
| 80 | HTTP | Unencrypted web traffic |
| 443 | HTTPS | Encrypted web traffic - covered in detail earlier in this project |
| 22 | SSH | Secure remote command-line access to a server |
| 25 | SMTP | Sending email between mail servers |
| 53 | DNS | Domain name resolution, covered extensively earlier in this project |
Why 80 and 443 Coexist
Port 80 (plain HTTP) still exists largely to support older links and to redirect visitors to the encrypted HTTPS version on port 443 - modern websites almost universally prefer 443 for actual content delivery, using 80 mainly as a redirect stepping stone rather than for serving real traffic.
Why Port 22 (SSH) Matters So Much for Administrators
SSH is the standard way system administrators securely log into and manage remote servers - port 22 being publicly exposed on a server is extremely common, which also makes it a frequent target for automated password-guessing attacks, reinforcing why strong authentication matters (as covered in the security best practices note).
A Nuance: SMTP's Port 25 vs Port 587
While port 25 is SMTP's traditional well-known port, many mail providers today use port 587 (with authentication and encryption) specifically for mail submission from user email clients, reserving port 25 mainly for server-to-server mail delivery.
Why Understanding These Beats Pure Memorization
These five ports show up constantly in networking, security, and web development - recognizing them on sight, and understanding why each service uses its specific port, is far more useful in practice than simply memorizing a disconnected list of numbers.