Port22— SSH / SFTP
OpenSSH listens on TCP 22 by default. Its SFTP subsystem transfers files over SSH, not the historical protocol assigned port 115.
Registry assignments, software defaults and local listeners are different things. A port number alone does not identify or secure a service.
Configuration and troubleshooting
Inspect Port and ListenAddress in sshd_config. Keep your current session and console access while validating a change, then test a second connection before disconnecting.
Important limitations
Changing the port is not a substitute for authentication or access control. Do not disable host-key verification to work around connection failures.
Read-only checks: run on the server host
Choose the commands for your OS. Check TCP and UDP separately. No result is not a lasting availability guarantee; inspect host and container separately.
Linux
sudo ss -ltnp 'sport = :22'macOS
sudo lsof -nP -iTCP:22 -sTCP:LISTENWindows PowerShell
Get-NetTCPConnection -LocalPort 22 -State ListenSources and review
Sources checked on:
This review covers the explanations and sources on this page, not your device or every community software entry below.
Related troubleshooting guides
Software Using This Port (3 software)
Community software entries: links are references, not individual verification.
Usage Suggestions
- Before using port 22, please confirm it is not occupied by other services
- If you encounter port conflicts, consider using other ports or stopping the occupying service
Frequently asked questions
What is port 22 used for?
Port 22 sits in the File Sharing category. This page lists the registered purpose and the software commonly associated with it; to see what is actually listening on a specific machine, check the process with ss/netstat.
Is port 22 TCP or UDP?
The registered protocol on this page is TCP. The same number behaves independently on each protocol: TCP may be listening while UDP is idle, so check them separately.
How do I check if port 22 is in use?
On Linux: sudo ss -tlnp 'sport = :22' for an exact port match. On macOS: sudo lsof -nP -iTCP:22 -sTCP:LISTEN. On Windows PowerShell: Get-NetTCPConnection -LocalPort 22 -State Listen. A listener counts as confirmed only when you can see the bind address and process name; without root/admin you will not see other users' processes.
Is port 22 secure? Should I open it in my firewall?
A port number has no inherent security — it depends on whether the listening service is correctly configured and whether it needs exposure at all. Keep loopback/internal-only services firewalled; where public access is required, pair it with source restrictions, VPN or authentication. The caution section on this page lists port-specific risks.
Quick Info
- Port
- 22
- Protocol
- TCP
- Categories
- File Sharing
- Usage Status
- 3 software in use
Related Ports
Need Help?
If you find incorrect information or need to add more, please submit correction information.
Submit Correction