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