PracticeBlogFlashcardsEspañol

Ports and Protocol Decision Table

Key Takeaways

  • Port knowledge is most useful when tied to use case, transport, and secure alternatives.
  • TCP is connection-oriented; UDP is connectionless and common for low-latency or query-response services.
  • Secure protocol choices often replace cleartext management or transfer protocols.
  • Network+ scenarios may ask which port to allow, which service is failing, or which protocol best fits a requirement.
  • Do not memorize ports in isolation; connect them to symptoms and design decisions.
Last updated: April 2026

Ports Become Useful in Context

Port questions are rarely just flashcards. You may need to choose a secure management protocol, identify a blocked service, or decide which firewall rule supports a requirement.

ProtocolPort(s)TransportCommon useExam decision clue
FTP data/control20/21TCPFile transferLegacy and cleartext; prefer SFTP/FTPS when security matters
SSH/SFTP22TCPSecure shell and secure file transferSecure remote administration
Telnet23TCPRemote terminalInsecure cleartext; avoid for management
SMTP25TCPMail transfer between serversMail relay traffic
DNS53UDP/TCPName resolution and zone transfersUDP for typical queries, TCP for zone transfers or large responses
DHCP67/68UDPDynamic client addressingClient cannot obtain lease
TFTP69UDPSimple file transferLightweight, no authentication, often network boot/device files
HTTP80TCPWeb trafficCleartext web
Kerberos88TCP/UDPAuthenticationTime-sensitive authentication in directory environments
POP3110TCPMail retrievalOlder mailbox download protocol
NTP123UDPTime synchronizationClock drift affects logs, certificates, Kerberos
IMAP143TCPMail accessMail stays on server
SNMP161/162UDPMonitoring and trapsDevice monitoring; prefer SNMPv3
LDAP389TCP/UDPDirectory accessDirectory queries; LDAPS is encrypted
HTTPS443TCPEncrypted webSecure web applications
SMB445TCPWindows file sharingFile shares and domain-related access
Syslog514UDP/TCPLog forwardingCentral logging; secure variants may use TLS
LDAPS636TCPEncrypted directory accessSecure LDAP
SQL Server1433TCPMicrosoft SQL ServerDatabase access
RDP3389TCP/UDPRemote desktopRemote GUI administration; restrict and protect
SIP5060/5061UDP/TCP/TLSVoIP signaling5061 commonly indicates TLS-secured SIP

Secure Replacement Table

Insecure or weaker choiceBetter choice when supportedWhy
TelnetSSHEncrypts remote administration
FTPSFTP or FTPSProtects credentials and file contents
HTTPHTTPSUses TLS for web confidentiality and integrity
SNMPv1/v2cSNMPv3Adds stronger authentication and encryption options
LDAPLDAPS or LDAP with StartTLSProtects directory queries and credentials

TCP or UDP Decision Cues

NeedOften fits
Reliable ordered delivery and session controlTCP
Low overhead query/response or real-time trafficUDP
Name lookupDNS over UDP for typical queries, TCP in specific cases
Address leaseDHCP over UDP
Time syncNTP over UDP
Web sessionHTTP/HTTPS over TCP

Scenario Decisions

ScenarioBest protocol or port focus
Secure CLI administration of a switchSSH TCP 22
Users cannot receive DHCP leasesUDP 67/68 and DHCP relay/scope
Monitoring system cannot poll router interface counters securelySNMPv3, typically UDP 161
Internal site must protect credentials in transitHTTPS TCP 443
Directory bind exposes credentialsLDAPS TCP 636 or StartTLS

Memorize the core ports, but always attach them to an operational story. That is how they appear in troubleshooting and firewall-rule questions.

Test Your Knowledge

Which protocol is the best secure replacement for Telnet when administering a router CLI?

A
B
C
D
Test Your KnowledgeMulti-Select

Which protocol and port pairings are correct? Select all that apply.

Select all that apply

DNS: port 53
HTTPS: port 443
DHCP: UDP ports 67 and 68
RDP: port 25
SSH: port 22
Test Your KnowledgeMatching

Match each requirement to the best protocol choice.

Match each item on the left with the correct item on the right

1
Encrypted web application access
2
Secure remote CLI administration
3
Dynamic IP address leasing
4
Network time synchronization
5
Secure directory access