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.
Sobre aquesta baralla
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.
Targetes d'aquesta baralla
Targeta 1
Pregunta
What does a transport-layer port number identify?
Resposta
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.
Targeta 2
Pregunta
Are TCP port 53 and UDP port 53 the same port?
Resposta
No. TCP and UDP have independent 16-bit port namespaces, so 53/TCP and 53/UDP are separate transport endpoints.
Targeta 3
Pregunta
What is the IANA System Port range?
Resposta
0–1023. These are also called Well-Known Ports and are assigned by IANA under the stricter System Port procedures.
Targeta 4
Pregunta
What is the IANA User Port range?
Resposta
1024–49151. These are also called Registered Ports and may be assigned by IANA to services.
Targeta 5
Pregunta
What is the IANA Dynamic or Private Port range?
Resposta
49152–65535. IANA does not assign ports in this range; systems commonly use it for temporary or private endpoints.
Targeta 6
Pregunta
Does an IANA port assignment prove what observed traffic is—or that it is safe?
Resposta
No. A registration is a naming convention, not traffic identification, authorization, or a security verdict. Verify the actual protocol and context.
Targeta 7
Pregunta
Must a service use its registered or conventional port?
Resposta
No. Administrators and applications can choose another port, negotiate one dynamically, or discover it through mechanisms such as DNS SRV records.
Targeta 8
Pregunta
What port roles are typical in a client-server connection?
Resposta
The server usually listens on a known destination port, while the client uses a temporary source port. Either side can be configured differently.
Targeta 9
Pregunta
SSH and SFTP — common server port and transport?
Resposta
TCP 22. SSH provides encrypted remote access, and SFTP normally runs as a subsystem inside the same SSH connection.
Targeta 10
Pregunta
53/UDP or 53/TCP — which service?
Resposta
DNS. Routine queries often use UDP, while full DNS implementations also support TCP; zone transfers use TCP.
Targeta 11
Pregunta
SMTP relay between mail servers — common port and transport?
Resposta
TCP 25. SMTP uses it for server-to-server mail transfer; user mail submission normally uses port 587 or implicit TLS on 465.
Targeta 12
Pregunta
HTTP without TLS — conventional port and transport?
Resposta
TCP 80 for conventional HTTP/1.1 and HTTP/2 connections. The service can be configured on another port.
Targeta 13
Pregunta
67/UDP — which DHCPv4 endpoint?
Resposta
The DHCPv4 server endpoint. Clients send server-directed DHCP messages to UDP port 67.
Targeta 14
Pregunta
21/TCP — which service and channel?
Resposta
FTP control. It carries commands and replies; file data uses a separate connection.
Targeta 15
Pregunta
SNMP requests and responses — common agent port and transport?
Resposta
UDP 161. Managers commonly send queries to an SNMP agent there; other SNMP transports exist.
Targeta 16
Pregunta
1433/TCP — which database service?
Resposta
Microsoft SQL Server's default instance. TCP 1433 is the default Database Engine port, but named or custom instances may use another port.
Targeta 17
Pregunta
23/TCP — which remote-access protocol?
Resposta
Telnet. It provides a plaintext remote terminal session and does not protect credentials or traffic with encryption.
Targeta 18
Pregunta
NTP — usual port and transport?
Resposta
UDP 123. NTP normally uses UDP for time synchronization; IANA also has a TCP 123 registration, but that is not the usual NTP transport.
Targeta 19
Pregunta
Why must a general-purpose DNS implementation support both UDP and TCP?
Resposta
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.
Targeta 20
Pregunta
POP3 — conventional port and transport?
Resposta
TCP 110. POP3 retrieves mail; it can upgrade with STLS, while implicit TLS uses TCP 995.
Targeta 21
Pregunta
443/TCP or 443/UDP — which web service?
Resposta
HTTPS. HTTP/1.1 and HTTP/2 normally use TLS over TCP 443; HTTP/3 uses QUIC over UDP 443.
Targeta 22
Pregunta
DHCPv4 client endpoint — port and transport?
Resposta
UDP 68. Servers send client-directed DHCPv4 messages to port 68.
Targeta 23
Pregunta
69/UDP — which file-transfer protocol?
Resposta
TFTP. A client sends the initial read or write request to UDP 69; the transfer then continues with a server-selected UDP transfer identifier.
Targeta 24
Pregunta
162/UDP — which network-management traffic?
Resposta
SNMP notifications, traditionally called traps. Notification receivers commonly listen on UDP 162.
Targeta 25
Pregunta
MySQL classic protocol — default port and transport?
Resposta
TCP 3306. It is the default for classic MySQL client-server connections and can be reconfigured.
Targeta 26
Pregunta
How do FTP control, active-mode data, and passive-mode data ports differ?
Resposta
Control uses TCP 21. The server side of the default active-mode data connection uses TCP 20, while passive mode negotiates another server port.
Targeta 27
Pregunta
3389/TCP or 3389/UDP — which remote-desktop service?
Resposta
Microsoft Remote Desktop Protocol (RDP). TCP and UDP 3389 are the standard defaults, and the listening port can be changed.
Targeta 28
Pregunta
Syslog's conventional UDP transport — port?
Resposta
UDP 514. Classic syslog over UDP has no delivery guarantee; TCP 514 is registered to the shell service, not syslog.
Targeta 29
Pregunta
How do DHCPv4 server and client ports pair up?
Resposta
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.
Targeta 30
Pregunta
IMAP — conventional port and transport?
Resposta
TCP 143. IMAP accesses and manages mail on a server; implicit TLS uses TCP 993.
Targeta 31
Pregunta
445/TCP — which file-sharing service?
Resposta
Direct-hosted SMB. Modern SMB servers commonly listen on TCP 445 without the older NetBIOS session layer.
Targeta 32
Pregunta
88/UDP or 88/TCP — which authentication protocol?
Resposta
Kerberos. Clients and Key Distribution Centers support both transports; TCP also handles requests or replies too large for UDP.
Targeta 33
Pregunta
FTP's default active-mode data connection — server-side port and transport?
Resposta
TCP 20. This is the server's default source port for active-mode data; passive FTP negotiates another server port.
Targeta 34
Pregunta
BGP — standard operational port and transport?
Resposta
TCP 179. RFC 4271 defines BGP peer sessions over TCP; IANA separately retains a UDP 179 registry entry.
Targeta 35
Pregunta
5432/TCP — which database service?
Resposta
PostgreSQL. TCP 5432 is the customary default server port, but an installation can choose another port.
Targeta 36
Pregunta
IKE for IPsec — initial port and transport?
Resposta
UDP 500. IKE normally begins there; NAT traversal commonly moves subsequent IKE and encapsulated ESP traffic to UDP 4500.
Targeta 37
Pregunta
NetBIOS Name Service — common port and transport?
Resposta
UDP 137. It supports NetBIOS name registration and lookup; direct-hosted modern SMB does not require it.
Targeta 38
Pregunta
587/TCP — which email role?
Resposta
SMTP message submission. Mail clients normally submit outgoing mail to a submission server there, often with STARTTLS; server relay remains on TCP 25.
Targeta 39
Pregunta
389/TCP — which directory protocol?
Resposta
LDAP. Ordinary connection-oriented LDAP commonly uses TCP 389; IANA also registers UDP 389 for connectionless LDAP.
Targeta 40
Pregunta
L2TP — common port and transport?
Resposta
UDP 1701. L2TP carries tunnel control and data but does not provide encryption by itself; deployments often pair it with IPsec.
Targeta 41
Pregunta
138/UDP — which NetBIOS service?
Resposta
NetBIOS Datagram Service. It carries connectionless NetBIOS datagrams, historically used in NetBIOS over TCP/IP environments.
Targeta 42
Pregunta
IMAPS — default port and transport?
Resposta
TCP 993. It starts IMAP with an immediate TLS handshake for encrypted mail access.
Targeta 43
Pregunta
636/TCP — which directory-service convention?
Resposta
LDAPS, the commonly used implicit-TLS port for LDAP. LDAP can also negotiate TLS on TCP 389.
Targeta 44
Pregunta
1723/TCP — which VPN control protocol?
Resposta
PPTP control. PPTP uses TCP 1723 for control, while tunneled PPP data travels in GRE—not on TCP or UDP port 47.
Targeta 45
Pregunta
NetBIOS Session Service — common port and transport?
Resposta
TCP 139. It provides connection-oriented NetBIOS sessions and historically carried SMB before direct-hosted SMB on TCP 445.
Targeta 46
Pregunta
995/TCP — which mail-access service?
Resposta
POP3S. It starts POP3 with an immediate TLS handshake for encrypted mail retrieval.
Targeta 47
Pregunta
RADIUS authentication and authorization — standard port and transport?
Resposta
UDP 1812. RADIUS accounting normally uses the separate UDP port 1813.
Targeta 48
Pregunta
IPsec NAT Traversal — port and transport?
Resposta
UDP 4500. It carries IKE and UDP-encapsulated ESP when NAT traversal is in use.
Targeta 49
Pregunta
5060/UDP or 5060/TCP — which signaling protocol?
Resposta
SIP. It commonly uses UDP or TCP 5060 for session signaling; SIP over TLS conventionally uses TCP 5061.
Targeta 50
Pregunta
Which common dedicated ports distinguish plaintext or STARTTLS-capable services from implicit-TLS variants?
Resposta
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.
Targeta 51
Pregunta
22/TCP — which secure remote-access service?
Resposta
SSH. It supports encrypted remote login, command execution, tunneling, and file-transfer tools such as SFTP.
Targeta 52
Pregunta
DNS — registered port and required general-purpose transports?
Resposta
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.
Targeta 53
Pregunta
25/TCP — which email function?
Resposta
SMTP mail relay and delivery between servers. End-user clients normally submit new mail on TCP 587 or TCP 465 instead.
Targeta 54
Pregunta
80/TCP — which conventional web service?
Resposta
HTTP without TLS. It is the conventional port for HTTP/1.1 and HTTP/2, although servers can listen elsewhere.
Targeta 55
Pregunta
DHCPv4 server endpoint — port and transport?
Resposta
UDP 67. DHCPv4 clients direct server-bound messages to that port.
Targeta 56
Pregunta
FTP control — server port and transport?
Resposta
TCP 21. Commands and replies use the persistent control connection; data travels on a separate connection.
Targeta 57
Pregunta
161/UDP — which network-management traffic?
Resposta
SNMP requests and responses. Managed agents commonly listen on UDP 161 for manager queries.
Targeta 58
Pregunta
Microsoft SQL Server default instance — default port and transport?
Resposta
TCP 1433. Named instances may use dynamic or custom ports, with SQL Server Browser commonly using UDP 1434 for discovery.
Targeta 59
Pregunta
Telnet — conventional port and transport?
Resposta
TCP 23. Telnet carries terminal traffic in plaintext, so SSH is the usual secure replacement.
Targeta 60
Pregunta
123/UDP — which time service?
Resposta
NTP. Network Time Protocol commonly synchronizes clocks over UDP 123.
Targeta 61
Pregunta
110/TCP — which mail-access protocol?
Resposta
POP3. It downloads or retrieves mail from a server; implicit TLS uses TCP 995.
Targeta 62
Pregunta
HTTPS — common port and transports?
Resposta
Port 443: TCP for HTTP/1.1 and HTTP/2 over TLS, and UDP for HTTP/3 over QUIC.
Targeta 63
Pregunta
68/UDP — which DHCPv4 endpoint?
Resposta
The DHCPv4 client endpoint. Servers direct client-bound DHCP messages to UDP 68.
Targeta 64
Pregunta
TFTP — initial request port and transport?
Resposta
UDP 69. Only the initial request targets 69; the server chooses another UDP transfer identifier for the data exchange.
Targeta 65
Pregunta
SNMP traps and other notifications — common receiver port and transport?
Resposta
UDP 162. SNMP notification receivers commonly listen there.
Targeta 66
Pregunta
3306/TCP — which database protocol?
Resposta
The classic MySQL protocol. TCP 3306 is its default client-server port and is configurable.
Targeta 67
Pregunta
RDP — standard port and transports?
Resposta
TCP and UDP 3389. Microsoft Remote Desktop uses them by default, though administrators can change the listening port.
Targeta 68
Pregunta
514/UDP — which logging protocol?
Resposta
Syslog over UDP. It is a conventional lightweight transport without delivery guarantees; secure syslog commonly uses another transport and port.
Targeta 69
Pregunta
143/TCP — which mail-access protocol?
Resposta
IMAP. It manages mail on the server; implicit TLS uses TCP 993.
Targeta 70
Pregunta
Direct-hosted SMB — common server port and transport?
Resposta
TCP 445. It carries SMB directly over TCP without the legacy NetBIOS Session Service on TCP 139.
Targeta 71
Pregunta
Kerberos KDC traffic — port and transports?
Resposta
UDP and TCP 88. Conforming clients and Key Distribution Centers support both, with TCP available for larger exchanges.
Targeta 72
Pregunta
20/TCP — which FTP role?
Resposta
The server side of FTP's default active-mode data connection. Passive mode negotiates a different server port.
Targeta 73
Pregunta
179/TCP — which routing protocol?
Resposta
BGP. Border Gateway Protocol peers use a TCP session to exchange routing information.
Targeta 74
Pregunta
PostgreSQL — customary default port and transport?
Resposta
TCP 5432. PostgreSQL servers normally use it unless configured or compiled with another default.
Targeta 75
Pregunta
500/UDP — which IPsec setup protocol?
Resposta
IKE, the Internet Key Exchange protocol. It negotiates IPsec security associations and commonly moves to UDP 4500 when NAT traversal is used.
Targeta 76
Pregunta
137/UDP — which NetBIOS service?
Resposta
NetBIOS Name Service. It handles name registration and lookup in legacy NetBIOS over TCP/IP environments.
Targeta 77
Pregunta
SMTP message submission — normal port and transport?
Resposta
TCP 587. It separates authenticated client submission from server-to-server SMTP relay on TCP 25; STARTTLS is commonly used.
Targeta 78
Pregunta
LDAP — conventional connection-oriented port and transport?
Resposta
TCP 389. Connectionless LDAP can use UDP 389, and implicit-TLS LDAP commonly uses TCP 636.
Targeta 79
Pregunta
1701/UDP — which tunneling protocol?
Resposta
L2TP. It tunnels Layer 2 traffic but needs a separate security layer such as IPsec when confidentiality is required.
Targeta 80
Pregunta
NetBIOS Datagram Service — common port and transport?
Resposta
UDP 138. It provides connectionless NetBIOS datagram delivery.
Targeta 81
Pregunta
993/TCP — which mail-access service?
Resposta
IMAPS. It begins IMAP with implicit TLS for encrypted access to mail stored on a server.
Targeta 82
Pregunta
LDAPS — commonly used implicit-TLS port and transport?
Resposta
TCP 636. LDAP can instead use TCP 389 and negotiate TLS with StartTLS.
Targeta 83
Pregunta
PPTP control — port and transport?
Resposta
TCP 1723. The control channel uses that port; PPP payloads travel through GRE, which is IP protocol 47 rather than port 47.
Targeta 84
Pregunta
139/TCP — which NetBIOS service?
Resposta
NetBIOS Session Service. It historically carried SMB sessions; direct-hosted SMB commonly uses TCP 445 instead.
Targeta 85
Pregunta
POP3S — default port and transport?
Resposta
TCP 995. It uses implicit TLS for encrypted POP3 mail retrieval.
Targeta 86
Pregunta
1812/UDP — which AAA service?
Resposta
RADIUS authentication and authorization. RADIUS accounting normally uses UDP 1813.
Targeta 87
Pregunta
4500/UDP — which IPsec function?
Resposta
IPsec NAT Traversal. It carries IKE and UDP-encapsulated ESP across network address translation.
Targeta 88
Pregunta
SIP signaling without implicit TLS — common port and transports?
Resposta
UDP or TCP 5060. SIP over TLS conventionally uses TCP 5061, and media streams use separately negotiated ports.
88 targetes
Common Network Port Numbers Flashcards: Protocols, TCP/UDP & Uses
Nibomo s'obre perquè puguis començar a estudiar.