port 22

Port 22 — SSH

SSH is essential for remote administration, but exposing port 22 requires strong authentication, firewalling and logs.

Approved intentUnderstand the default SSH/SFTP port.

Open in the catalogThe Port Finder below already opens searching for `22`, with the SSH/SFTP entry loaded and ready for comparison.

portFinder.searchLabel

portFinder.protocolportFinder.rangeportFinder.categoryportFinder.security

portFinder.resultsCount

22TCPportFinder.securities.secureportFinder.encrypted
SSH — Secure Shell / SFTP
SSH remote shell and SFTP file transfer with end-to-end encryption.
portFinder.categories.remote-accessportFinder.categories.file-transferRFC 4251
20TCPportFinder.securities.insecure
FTP-DATA — File Transfer Protocol — Data
FTP data channel (active mode). Cleartext — prefer SFTP (22) or FTPS (990).
portFinder.categories.file-transferRFC 959portFinder.secureAlternative
21TCPportFinder.securities.insecure
FTP — File Transfer Protocol — Control
FTP control channel. Cleartext. Prefer SFTP (22) or FTPS (990).
portFinder.categories.file-transferRFC 959portFinder.secureAlternative
23TCPportFinder.securities.insecure
TELNET — Telnet
Legacy cleartext remote shell. Replaced by SSH (22).
portFinder.categories.remote-accessRFC 854portFinder.secureAlternative
990TCPportFinder.securities.secureportFinder.encrypted
FTPS — FTPS over TLS — Control
FTPS with implicit TLS. SFTP (22) is usually simpler to operate.
portFinder.categories.file-transfer

portFinder.privacyNote

Common use of port 22

TCP port 22 is used by SSH for remote shells and by SFTP for encrypted file transfer.
Changing the port reduces bot noise, but does not replace strong keys, MFA and fail2ban/rate limiting.

Use keys instead of passwords when possible.

Different from FTP/FTPS.

It can reduce automated attempts, but real security comes from keys, IP blocking/rate limits and keeping the server updated.

Yes, SFTP runs over SSH and normally uses port 22.