Common Ports & Protocols

The ones that actually come up — on the exam, in the interview, and at 2am when something's down.

There are 65,535 ports. You need about forty. Every "complete" port list buries the useful ones under IANA registrations nobody has touched since 1998, so here's the short version — grouped by what you're actually doing when you need it.

Web and remote access

PortProtocolWhat it's for
22SSH / SFTPRemote shell and secure file transfer. If it's closed, you're driving to the office.
23TelnetUnencrypted remote shell. Should be off. If it's open, that's a finding.
80HTTPUnencrypted web.
443HTTPSEncrypted web. The one that must never be blocked.
3389RDPWindows remote desktop. Never expose this to the internet — it's the single most brute-forced port there is.
5900VNCCross-platform remote desktop.
8080HTTP altProxies, dev servers, app servers behind a load balancer.

Mail

PortProtocolWhat it's for
25SMTPServer-to-server mail relay. Usually blocked outbound by ISPs to fight spam.
587SMTP submissionWhat a mail client should use to send. This is the one you want.
465SMTPSImplicit-TLS submission. Still widely supported.
110 / 995POP3 / POP3SDownload-and-delete mail retrieval.
143 / 993IMAP / IMAPSServer-side mailbox sync. What everyone actually uses.

Core infrastructure

PortProtocolWhat it's for
53DNSName resolution. When "the internet is down," it's usually this.
67 / 68DHCPHanding out IP addresses (server / client).
123NTPTime sync. Bad time breaks Kerberos, certificates, and logs.
161 / 162SNMPDevice monitoring / traps.
514SyslogCentralized logging.
389 / 636LDAP / LDAPSDirectory lookups — Active Directory lives here.
445SMBWindows file sharing. Never let this cross the internet; it's how ransomware spreads laterally.
137–139NetBIOSLegacy Windows naming. Usually a leftover you should close.

Databases and services

PortProtocolWhat it's for
1433MS SQL Server
1521Oracle DB
3306MySQL / MariaDB
5432PostgreSQL
6379RedisHistorically unauthenticated by default — never expose it.
27017MongoDBSame warning. Bind to localhost.
5060 / 5061SIP / SIP-TLSVoIP call setup.
The interview trick: nobody expects you to recite all 65,535. They're checking whether you know why a port matters — that 3389 open to the internet is a real finding, that 587 is for clients and 25 is for servers, that DNS on 53 is the usual suspect when "everything's down." Learn the reasons and the numbers stick.

Fast recall, the honest way

Want this as a printable card?

The Common Ports & Protocols Reference Card — one clean page, made to print and pin above the desk. Instant download.

Get the card — $3 →

If you're studying for CompTIA or prepping interviews, the Subnetting & CIDR sheet and the IT & Security Interview Answer Bank cover the other two things you'll get asked about most.