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