Which port is used for encrypted communication?

Port 22 is widely known for facilitating encrypted communication, primarily through the Secure Shell (SSH) protocol. SSH provides a secure channel over an unsecured network, allowing users to access and manage systems with confidentiality and integrity. It is often used for secure remote logins and executing commands on remote machines, making it essential for network security practices.

In contrast, port 80 is designated for HTTP (Hypertext Transfer Protocol), which transmits data in plain text. This means that data exchanged over port 80 is not encrypted and can be intercepted, making it less secure. Port 389 is used for LDAP (Lightweight Directory Access Protocol), which, like HTTP, generally does not provide encryption unless specifically configured to use LDAPS (LDAP over SSL). Port 25 is utilized for SMTP (Simple Mail Transfer Protocol), which is responsible for sending emails but does not inherently encrypt the email content unless additional security measures are taken, such as using STARTTLS.

Overall, port 22's association with SSH establishes it as the go-to choice for secure and encrypted communication across networks.