Common Network Port Numbers Flashcards: Protocols, TCP/UDP & Uses
Study 88 cards on common network ports, TCP/UDP transports, service uses, port ranges, and practical protocol distinctions.
Kuhusu fungu hili
Build a practical map of common network service ports with 88 independently authored cards. Twelve foundation and distinction cards cover port roles, IANA ranges, independent TCP and UDP namespaces, assignment limits, conventional versus configured ports, client source ports, DNS transport behavior, DHCP endpoints, FTP channels, and common implicit-TLS pairs.
The remaining 76 cards practice 38 mappings in both useful directions: service → conventional or registered port, transport, and concise use; and port/transport → service and concise use. Coverage includes FTP control and active-mode data, SSH/SFTP, Telnet, SMTP relay, DNS, DHCPv4 server and client endpoints, TFTP, HTTP, Kerberos, POP3, NTP, the three NetBIOS services, IMAP, SNMP queries and notifications, BGP, LDAP, HTTPS including HTTP/3, direct-hosted SMB, IKE, syslog, SMTP submission, LDAPS, IMAPS, POP3S, Microsoft SQL Server, L2TP, PPTP, RADIUS authentication, MySQL, RDP, IPsec NAT Traversal, SIP, and PostgreSQL.
This is a focused recall deck, not a copy of the full IANA registry. It excludes exhaustive assignments, port-scanning or attack instructions, firewall policy, every vendor-specific alternate, dynamic service-discovery inventories, and the claim that a port number proves which application produced observed traffic. Registered, default, conventional, and common-use wording stays explicit because services can be reconfigured or negotiated elsewhere.
The sequence establishes the port model first, then mixes web, email, infrastructure, remote-access, file-transfer, network-management, directory, VPN, voice, Windows, and database families. Opposite directions for the same mapping stay at least 38 intervening cards apart. Near-duplicate DNS, DHCP, FTP, SNMP, NetBIOS, and IPsec cues keep at least three unrelated cards between them, and the TLS-pair distinction stays at least three unrelated cards from its closest overlapping mapping. The review scheduler handles continued spacing after installation.
Open Study Contributor independently authored the prompts, answers, mapping choices, organization, metadata, and cover from common networking knowledge checked against the current IANA Service Name and Transport Protocol Port Number Registry, relevant RFCs, and official vendor documentation. Organization and product names identify protocols, services, or sources only; no affiliation or endorsement is claimed. No competitor card text, certification questions, answer keys, course text, or source prose was copied.
The CC0 label applies to the original prompts, answers, organization, metadata, and generated cover to the extent applicable rights exist. It does not claim ownership of protocol facts, standards, organization names, product names, or third-party source material.
Kadi za fungu hili
Kadi namba 1
Swali
What does a transport-layer port number identify?
Jibu
An application endpoint within a host for one transport protocol. The IP addresses, transport protocol, and source and destination ports together identify a communication flow.
Kadi namba 2
Swali
Are TCP port 53 and UDP port 53 the same port?
Jibu
No. TCP and UDP have independent 16-bit port namespaces, so 53/TCP and 53/UDP are separate transport endpoints.
Kadi namba 3
Swali
What is the IANA System Port range?
Jibu
0–1023. These are also called Well-Known Ports and are assigned by IANA under the stricter System Port procedures.
Kadi namba 4
Swali
What is the IANA User Port range?
Jibu
1024–49151. These are also called Registered Ports and may be assigned by IANA to services.
Kadi namba 5
Swali
What is the IANA Dynamic or Private Port range?
Jibu
49152–65535. IANA does not assign ports in this range; systems commonly use it for temporary or private endpoints.
Kadi namba 6
Swali
Does an IANA port assignment prove what observed traffic is—or that it is safe?
Jibu
No. A registration is a naming convention, not traffic identification, authorization, or a security verdict. Verify the actual protocol and context.
Kadi namba 7
Swali
Must a service use its registered or conventional port?
Jibu
No. Administrators and applications can choose another port, negotiate one dynamically, or discover it through mechanisms such as DNS SRV records.
Kadi namba 8
Swali
What port roles are typical in a client-server connection?
Jibu
The server usually listens on a known destination port, while the client uses a temporary source port. Either side can be configured differently.
Kadi namba 9
Swali
SSH and SFTP — common server port and transport?
Jibu
TCP 22. SSH provides encrypted remote access, and SFTP normally runs as a subsystem inside the same SSH connection.
Kadi namba 10
Swali
53/UDP or 53/TCP — which service?
Jibu
DNS. Routine queries often use UDP, while full DNS implementations also support TCP; zone transfers use TCP.
Kadi namba 11
Swali
SMTP relay between mail servers — common port and transport?
Jibu
TCP 25. SMTP uses it for server-to-server mail transfer; user mail submission normally uses port 587 or implicit TLS on 465.
Kadi namba 12
Swali
HTTP without TLS — conventional port and transport?
Jibu
TCP 80 for conventional HTTP/1.1 and HTTP/2 connections. The service can be configured on another port.
Kadi namba 13
Swali
67/UDP — which DHCPv4 endpoint?
Jibu
The DHCPv4 server endpoint. Clients send server-directed DHCP messages to UDP port 67.
Kadi namba 14
Swali
21/TCP — which service and channel?
Jibu
FTP control. It carries commands and replies; file data uses a separate connection.
Kadi namba 15
Swali
SNMP requests and responses — common agent port and transport?
Jibu
UDP 161. Managers commonly send queries to an SNMP agent there; other SNMP transports exist.
Kadi namba 16
Swali
1433/TCP — which database service?
Jibu
Microsoft SQL Server's default instance. TCP 1433 is the default Database Engine port, but named or custom instances may use another port.
Kadi namba 17
Swali
23/TCP — which remote-access protocol?
Jibu
Telnet. It provides a plaintext remote terminal session and does not protect credentials or traffic with encryption.
Kadi namba 18
Swali
NTP — usual port and transport?
Jibu
UDP 123. NTP normally uses UDP for time synchronization; IANA also has a TCP 123 registration, but that is not the usual NTP transport.
Kadi namba 19
Swali
Why must a general-purpose DNS implementation support both UDP and TCP?
Jibu
UDP handles most routine queries efficiently, while TCP handles cases such as zone transfers and responses that do not fit the chosen UDP path. Both use port 53.
Kadi namba 20
Swali
POP3 — conventional port and transport?
Jibu
TCP 110. POP3 retrieves mail; it can upgrade with STLS, while implicit TLS uses TCP 995.
Kadi namba 21
Swali
443/TCP or 443/UDP — which web service?
Jibu
HTTPS. HTTP/1.1 and HTTP/2 normally use TLS over TCP 443; HTTP/3 uses QUIC over UDP 443.
Kadi namba 22
Swali
DHCPv4 client endpoint — port and transport?
Jibu
UDP 68. Servers send client-directed DHCPv4 messages to port 68.
Kadi namba 23
Swali
69/UDP — which file-transfer protocol?
Jibu
TFTP. A client sends the initial read or write request to UDP 69; the transfer then continues with a server-selected UDP transfer identifier.
Kadi namba 24
Swali
162/UDP — which network-management traffic?
Jibu
SNMP notifications, traditionally called traps. Notification receivers commonly listen on UDP 162.
Kadi namba 25
Swali
MySQL classic protocol — default port and transport?
Jibu
TCP 3306. It is the default for classic MySQL client-server connections and can be reconfigured.
Kadi namba 26
Swali
How do FTP control, active-mode data, and passive-mode data ports differ?
Jibu
Control uses TCP 21. The server side of the default active-mode data connection uses TCP 20, while passive mode negotiates another server port.
Kadi namba 27
Swali
3389/TCP or 3389/UDP — which remote-desktop service?
Jibu
Microsoft Remote Desktop Protocol (RDP). TCP and UDP 3389 are the standard defaults, and the listening port can be changed.
Kadi namba 28
Swali
Syslog's conventional UDP transport — port?
Jibu
UDP 514. Classic syslog over UDP has no delivery guarantee; TCP 514 is registered to the shell service, not syslog.
Kadi namba 29
Swali
How do DHCPv4 server and client ports pair up?
Jibu
UDP 67 is the server port, and UDP 68 is the client port. Client-to-server messages target 67; server-to-client messages target 68.
Kadi namba 30
Swali
IMAP — conventional port and transport?
Jibu
TCP 143. IMAP accesses and manages mail on a server; implicit TLS uses TCP 993.
Kadi namba 31
Swali
445/TCP — which file-sharing service?
Jibu
Direct-hosted SMB. Modern SMB servers commonly listen on TCP 445 without the older NetBIOS session layer.
Kadi namba 32
Swali
88/UDP or 88/TCP — which authentication protocol?
Jibu
Kerberos. Clients and Key Distribution Centers support both transports; TCP also handles requests or replies too large for UDP.
Kadi namba 33
Swali
FTP's default active-mode data connection — server-side port and transport?
Jibu
TCP 20. This is the server's default source port for active-mode data; passive FTP negotiates another server port.
Kadi namba 34
Swali
BGP — standard operational port and transport?
Jibu
TCP 179. RFC 4271 defines BGP peer sessions over TCP; IANA separately retains a UDP 179 registry entry.
Kadi namba 35
Swali
5432/TCP — which database service?
Jibu
PostgreSQL. TCP 5432 is the customary default server port, but an installation can choose another port.
Kadi namba 36
Swali
IKE for IPsec — initial port and transport?
Jibu
UDP 500. IKE normally begins there; NAT traversal commonly moves subsequent IKE and encapsulated ESP traffic to UDP 4500.
Kadi namba 37
Swali
NetBIOS Name Service — common port and transport?
Jibu
UDP 137. It supports NetBIOS name registration and lookup; direct-hosted modern SMB does not require it.
Kadi namba 38
Swali
587/TCP — which email role?
Jibu
SMTP message submission. Mail clients normally submit outgoing mail to a submission server there, often with STARTTLS; server relay remains on TCP 25.
Kadi namba 39
Swali
389/TCP — which directory protocol?
Jibu
LDAP. Ordinary connection-oriented LDAP commonly uses TCP 389; IANA also registers UDP 389 for connectionless LDAP.
Kadi namba 40
Swali
L2TP — common port and transport?
Jibu
UDP 1701. L2TP carries tunnel control and data but does not provide encryption by itself; deployments often pair it with IPsec.
Kadi namba 41
Swali
138/UDP — which NetBIOS service?
Jibu
NetBIOS Datagram Service. It carries connectionless NetBIOS datagrams, historically used in NetBIOS over TCP/IP environments.
Kadi namba 42
Swali
IMAPS — default port and transport?
Jibu
TCP 993. It starts IMAP with an immediate TLS handshake for encrypted mail access.
Kadi namba 43
Swali
636/TCP — which directory-service convention?
Jibu
LDAPS, the commonly used implicit-TLS port for LDAP. LDAP can also negotiate TLS on TCP 389.
Kadi namba 44
Swali
1723/TCP — which VPN control protocol?
Jibu
PPTP control. PPTP uses TCP 1723 for control, while tunneled PPP data travels in GRE—not on TCP or UDP port 47.
Kadi namba 45
Swali
NetBIOS Session Service — common port and transport?
Jibu
TCP 139. It provides connection-oriented NetBIOS sessions and historically carried SMB before direct-hosted SMB on TCP 445.
Kadi namba 46
Swali
995/TCP — which mail-access service?
Jibu
POP3S. It starts POP3 with an immediate TLS handshake for encrypted mail retrieval.
Kadi namba 47
Swali
RADIUS authentication and authorization — standard port and transport?
Jibu
UDP 1812. RADIUS accounting normally uses the separate UDP port 1813.
Kadi namba 48
Swali
IPsec NAT Traversal — port and transport?
Jibu
UDP 4500. It carries IKE and UDP-encapsulated ESP when NAT traversal is in use.
Kadi namba 49
Swali
5060/UDP or 5060/TCP — which signaling protocol?
Jibu
SIP. It commonly uses UDP or TCP 5060 for session signaling; SIP over TLS conventionally uses TCP 5061.
Kadi namba 50
Swali
Which common dedicated ports distinguish plaintext or STARTTLS-capable services from implicit-TLS variants?
Jibu
HTTP 80 ↔ HTTPS 443; IMAP 143 ↔ IMAPS 993; POP3 110 ↔ POP3S 995; LDAP 389 ↔ LDAPS 636. A port alone does not prove that TLS is configured correctly.
Kadi namba 51
Swali
22/TCP — which secure remote-access service?
Jibu
SSH. It supports encrypted remote login, command execution, tunneling, and file-transfer tools such as SFTP.
Kadi namba 52
Swali
DNS — registered port and required general-purpose transports?
Jibu
Port 53 over UDP and TCP. Most ordinary queries start with UDP, while TCP is required for full implementations and used for zone transfers and other larger exchanges.
Kadi namba 53
Swali
25/TCP — which email function?
Jibu
SMTP mail relay and delivery between servers. End-user clients normally submit new mail on TCP 587 or TCP 465 instead.
Kadi namba 54
Swali
80/TCP — which conventional web service?
Jibu
HTTP without TLS. It is the conventional port for HTTP/1.1 and HTTP/2, although servers can listen elsewhere.
Kadi namba 55
Swali
DHCPv4 server endpoint — port and transport?
Jibu
UDP 67. DHCPv4 clients direct server-bound messages to that port.
Kadi namba 56
Swali
FTP control — server port and transport?
Jibu
TCP 21. Commands and replies use the persistent control connection; data travels on a separate connection.
Kadi namba 57
Swali
161/UDP — which network-management traffic?
Jibu
SNMP requests and responses. Managed agents commonly listen on UDP 161 for manager queries.
Kadi namba 58
Swali
Microsoft SQL Server default instance — default port and transport?
Jibu
TCP 1433. Named instances may use dynamic or custom ports, with SQL Server Browser commonly using UDP 1434 for discovery.
Kadi namba 59
Swali
Telnet — conventional port and transport?
Jibu
TCP 23. Telnet carries terminal traffic in plaintext, so SSH is the usual secure replacement.
Kadi namba 60
Swali
123/UDP — which time service?
Jibu
NTP. Network Time Protocol commonly synchronizes clocks over UDP 123.
Kadi namba 61
Swali
110/TCP — which mail-access protocol?
Jibu
POP3. It downloads or retrieves mail from a server; implicit TLS uses TCP 995.
Kadi namba 62
Swali
HTTPS — common port and transports?
Jibu
Port 443: TCP for HTTP/1.1 and HTTP/2 over TLS, and UDP for HTTP/3 over QUIC.
Kadi namba 63
Swali
68/UDP — which DHCPv4 endpoint?
Jibu
The DHCPv4 client endpoint. Servers direct client-bound DHCP messages to UDP 68.
Kadi namba 64
Swali
TFTP — initial request port and transport?
Jibu
UDP 69. Only the initial request targets 69; the server chooses another UDP transfer identifier for the data exchange.
Kadi namba 65
Swali
SNMP traps and other notifications — common receiver port and transport?
Jibu
UDP 162. SNMP notification receivers commonly listen there.
Kadi namba 66
Swali
3306/TCP — which database protocol?
Jibu
The classic MySQL protocol. TCP 3306 is its default client-server port and is configurable.
Kadi namba 67
Swali
RDP — standard port and transports?
Jibu
TCP and UDP 3389. Microsoft Remote Desktop uses them by default, though administrators can change the listening port.
Kadi namba 68
Swali
514/UDP — which logging protocol?
Jibu
Syslog over UDP. It is a conventional lightweight transport without delivery guarantees; secure syslog commonly uses another transport and port.
Kadi namba 69
Swali
143/TCP — which mail-access protocol?
Jibu
IMAP. It manages mail on the server; implicit TLS uses TCP 993.
Kadi namba 70
Swali
Direct-hosted SMB — common server port and transport?
Jibu
TCP 445. It carries SMB directly over TCP without the legacy NetBIOS Session Service on TCP 139.
Kadi namba 71
Swali
Kerberos KDC traffic — port and transports?
Jibu
UDP and TCP 88. Conforming clients and Key Distribution Centers support both, with TCP available for larger exchanges.
Kadi namba 72
Swali
20/TCP — which FTP role?
Jibu
The server side of FTP's default active-mode data connection. Passive mode negotiates a different server port.
Kadi namba 73
Swali
179/TCP — which routing protocol?
Jibu
BGP. Border Gateway Protocol peers use a TCP session to exchange routing information.
Kadi namba 74
Swali
PostgreSQL — customary default port and transport?
Jibu
TCP 5432. PostgreSQL servers normally use it unless configured or compiled with another default.
Kadi namba 75
Swali
500/UDP — which IPsec setup protocol?
Jibu
IKE, the Internet Key Exchange protocol. It negotiates IPsec security associations and commonly moves to UDP 4500 when NAT traversal is used.
Kadi namba 76
Swali
137/UDP — which NetBIOS service?
Jibu
NetBIOS Name Service. It handles name registration and lookup in legacy NetBIOS over TCP/IP environments.
Kadi namba 77
Swali
SMTP message submission — normal port and transport?
Jibu
TCP 587. It separates authenticated client submission from server-to-server SMTP relay on TCP 25; STARTTLS is commonly used.
Kadi namba 78
Swali
LDAP — conventional connection-oriented port and transport?
Jibu
TCP 389. Connectionless LDAP can use UDP 389, and implicit-TLS LDAP commonly uses TCP 636.
Kadi namba 79
Swali
1701/UDP — which tunneling protocol?
Jibu
L2TP. It tunnels Layer 2 traffic but needs a separate security layer such as IPsec when confidentiality is required.
Kadi namba 80
Swali
NetBIOS Datagram Service — common port and transport?
Jibu
UDP 138. It provides connectionless NetBIOS datagram delivery.
Kadi namba 81
Swali
993/TCP — which mail-access service?
Jibu
IMAPS. It begins IMAP with implicit TLS for encrypted access to mail stored on a server.
Kadi namba 82
Swali
LDAPS — commonly used implicit-TLS port and transport?
Jibu
TCP 636. LDAP can instead use TCP 389 and negotiate TLS with StartTLS.
Kadi namba 83
Swali
PPTP control — port and transport?
Jibu
TCP 1723. The control channel uses that port; PPP payloads travel through GRE, which is IP protocol 47 rather than port 47.
Kadi namba 84
Swali
139/TCP — which NetBIOS service?
Jibu
NetBIOS Session Service. It historically carried SMB sessions; direct-hosted SMB commonly uses TCP 445 instead.
Kadi namba 85
Swali
POP3S — default port and transport?
Jibu
TCP 995. It uses implicit TLS for encrypted POP3 mail retrieval.
Kadi namba 86
Swali
1812/UDP — which AAA service?
Jibu
RADIUS authentication and authorization. RADIUS accounting normally uses UDP 1813.
Kadi namba 87
Swali
4500/UDP — which IPsec function?
Jibu
IPsec NAT Traversal. It carries IKE and UDP-encapsulated ESP across network address translation.
Kadi namba 88
Swali
SIP signaling without implicit TLS — common port and transports?
Jibu
UDP or TCP 5060. SIP over TLS conventionally uses TCP 5061, and media streams use separately negotiated ports.
kadi 88
Common Network Port Numbers Flashcards: Protocols, TCP/UDP & Uses
Nibomo itafunguka ili uanze kusoma.