port 22
Port 22, reserved by IANA for SSH since RFC 4251, is the administrative port most exposed to internet scanning bots, which makes its authentication setup matter more than the number itself.
The tool marks 22 as secure because the protocol encrypts by default, unlike port 23 (Telnet), listed as insecure and legacy right next to it in the same catalog.
The `-p 22` flag is redundant because 22 is already the SSH client's default port, but it stays explicit in scripts that also support alternate ports.
SCP reuses the already-authenticated SSH session, with no new credential negotiation.
Deliberate decision: unauthorized port scanning is an abuse vector and has legal implications in several countries. We prefer a clear, safe reference.
No. Changing the port only reduces the volume of automated bots that just probe port 22 by default; any dedicated port scan finds the service on another port within minutes. The real protection comes from disabling password login and requiring a public key.
No. SFTP runs inside a regular SSH session on port 22. Traditional FTP uses port 21 for control and a separate port for data, with no encryption by default, which makes SFTP the simpler choice to operate through a firewall.
Because it is the default administrative port on practically every Linux server exposed to the internet, so mass-scanning bots continuously probe port 22 with known password lists. Servers with password login enabled see brute-force attempts within minutes of going online.
SSH remote shell and SFTP file transfer with end-to-end encryption.
Everything runs locally in your browser from an embedded catalog. This tool does not connect to IPs or ports, it is not a scanner.