Intro

A port number selects a service endpoint within an IP host. IANA registrations provide interoperable defaults; they do not force a deployment to listen there, prove which application owns a socket, or bypass firewall policy. Diagnose the actual listener and negotiated protocol before treating a familiar number as evidence.

ServiceRegistered/default portUsual transportOperational caveat
FTP control21TCPData uses a separate negotiated connection; prefer SSH-based or HTTPS transfer for new systems
SSH22TCPFrequently moved, but changing the port is noise reduction rather than authentication
Telnet23TCPUnencrypted; use SSH
SMTP relay25TCPClient submission normally uses 587; implicit TLS submission commonly uses 465
DNS53UDP and TCPUDP handles ordinary queries; TCP is required for zone transfer and used for truncation fallback and larger exchanges
DHCP server/client67 / 68UDPBroadcast behavior and relay agents matter across subnets
HTTP80TCPMay redirect to HTTPS; HTTP/3 is normally advertised on a secure origin instead
POP3110TCPImplicit TLS is registered on 995
NTP123UDP primarilyIANA also registers TCP; normal NTP exchanges use UDP
NetBIOS session139TCPName and datagram services use UDP 137/138; modern Windows file sharing usually uses SMB directly on 445
IMAP143TCPImplicit TLS is registered on 993
HTTPS443TCP and UDPHTTP/1.1 and HTTP/2 use TLS over TCP; HTTP/3 uses QUIC over UDP
SMB445TCPNever expose directly to the public internet without a specific protected design
Oracle listener1521TCPA common registered listener port, still configurable
MySQL3306TCPKeep database listeners on private networks and require authenticated TLS where supported
RDP3389TCP and UDPModern RDP can use both; public exposure attracts credential attacks
PostgreSQL5432TCPConfigurable; network access and pg_hba.conf are separate gates
# A port says what accepted the connection, not what protocol is safe.
nc -vz db.internal.example 5432
openssl s_client -connect api.example.com:443 -servername api.example.com

References