Chapters0/30 ▾
Chapter 3 · Lesson 1 of 5
Well-known ports: secure and cleartext pairs
1 min read
| Job | Cleartext or basic | Secure or preferred |
|---|---|---|
| Remote command line | Telnet TCP 23 | SSH TCP 22 |
| File transfer | FTP TCP 21, TFTP UDP 69 | SFTP inside SSH on TCP 22; FTPS is FTP over TLS (AUTH TLS on 21, or implicit on 990) |
| Directory | LDAP TCP 389 (TLS only via StartTLS) | LDAPS TCP 636 |
| Sending mail | SMTP TCP 25, server to server | Submission TCP 587, client with login |
| Reading mail | POP3 TCP 110, downloads to one device | IMAP TCP 143, synced on the server |
| Logging | Syslog UDP 514 | TCP 514 is the old remote shell, not syslog |
Read each scenario for the deciding word. A request for LDAP that is wrapped in TLS from the first byte means 636, because 389 carries TLS only when the client upgrades with StartTLS.
A user who reads mail on a laptop and a phone and wants folders and read status to match needs IMAP. An admin who wants encrypted file copies over the port already open for management needs SFTP on 22.
Check yourself
1. A firewall change request asks you to permit directory service lookups between an application server and a domain controller over a session that is wrapped in TLS from the moment it opens, not upgraded in band with StartTLS. Which destination port must the rule allow?
2. An administrator must copy configuration files to a server over an encrypted channel and wants the transfer to reuse the same service and port already open for command-line administration. Which protocol and port meet this requirement?
Facts checked 2026-11-16 · Sources: CompTIA Network+ certification overview, IANA Service Name and Transport Protocol Port Number Registry, RFC 7766: DNS Transport over TCP
CompTIA Network+ cheat sheet: every key fact on one page →