| Port | 22 |
|---|---|
| Transport | TCP |
| Service | SSH — SSH, SCP, SFTP, git over ssh |
| Category | Remote access |
| Range | well-known (0–1023, needs root to bind on Unix) |
| Encrypted | Yes, always (TLS or equivalent) |
| Exposure | Internet-facing only with authentication and care |
Port 22 SSH · TCP
SSH: encrypted remote shell, plus everything built on it: SCP and SFTP file transfer, git over ssh, port forwarding and tunnels, rsync over ssh, Ansible.
What runs on port 22
SSH: encrypted remote shell, plus everything built on it: SCP and SFTP file transfer, git over ssh, port forwarding and tunnels, rsync over ssh, Ansible. It is the one port most servers have open to the world, and the most brute-forced port on the internet by a wide margin.
Software that uses it: OpenSSH · Dropbear · libssh · Windows OpenSSH Server · Gitea/GitLab/GitHub (git over ssh)
Should port 22 be open?
Internet-facing only with authentication and care. It can be exposed when the service behind it is authenticated, rate-limited and kept up to date; most deployments are better off behind a VPN, an allow-list or a reverse proxy.
- Disable password authentication and use keys; brute force then becomes noise.
- Moving to another port reduces log spam but is not a security measure; fail2ban or a VPN is.
- ssh -v shows the negotiated key exchange and cipher when debugging.
Check port 22
# on the host: is anything listening, and which process? ss -ltnp 'sport = :22' sudo lsof -i :22 # from another machine: is it reachable? nc -zv host 22 nmap -p 22 host curl -v telnet://host:22 # raw TCP connect test, Ctrl-C to leave
A port that answers from the internet when it should not is the finding; nmap from a machine outside your network (or a VPS) is the honest test, because scans from inside the LAN pass the firewall you are trying to verify.
Allow or block port 22
# ufw (Ubuntu/Debian) sudo ufw allow from 10.0.0.0/8 to any port 22 proto tcp sudo ufw deny 22/tcp # nftables nft add rule inet filter input ip saddr 10.0.0.0/8 tcp dport 22 accept nft add rule inet filter input tcp dport 22 drop # iptables (legacy) iptables -A INPUT -p tcp --dport 22 -s 10.0.0.0/8 -j ACCEPT iptables -A INPUT -p tcp --dport 22 -j DROP # firewalld sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source address=10.0.0.0/8 port port=22 protocol=tcp accept'
Replace 10.0.0.0/8 with the networks that need access. Allowing by source address is the rule that matters; "allow 22" with no source is just "open".
Related ports
Part of the port number reference. Ports are 16-bit numbers; see also the subnet calculator and the packet decoder, which shows ports inside TCP and UDP headers.
Questions
Is port 22 TCP or UDP?
TCP. SSH is a connection-oriented protocol; there is no UDP service on 22 by default (a scanner reporting UDP 22 open is usually seeing a filtered port).
Is port 22 encrypted?
Yes, always (TLS or equivalent). The port number does not make it safe by itself: certificate validation, authentication and patching still decide.
How do I check whether port 22 is open?
On the server, ss -ltnp (or -lunp for UDP) shows whether something listens on 22 and which process. From another machine, nc -zv host 22 or nmap -p 22 host tests reachability. "Open" in a scan means something answered; a firewall usually makes the port filtered (no answer) rather than closed (RST).
Can SSH run on a different port?
Yes; the number is a convention, not a requirement. Changing it reduces log noise from scanners but does not add security, and every client, firewall rule and monitoring check then needs the new number. Keep the default unless you have a concrete reason.