Blog

When it comes to securely transferring files over the internet, the SSH File Transfer Protocol (SFTP) stands out as one of the most trusted and reliable solutions available. Its core security features make it extremely popular among organizations that handle sensitive data. Many of our customers, spanning diverse sectors such as financial services, healthcare, retail, manufacturing, logistics, defense, research, aerospace and e-commerce, rely on SFTP to ensure the confidentiality and integrity of their data transfers.

The SSH File Transfer Protocol (SFTP) uses TCP port 22 as its default port number. However, if you or your server administrator wishes to assign a different port number for your SFTP service, the protocol allows it. In this post, we’ll take a closer look at the default SFTP port number and tackle some key considerations when choosing alternate port numbers for your SFTP server.

When users attempt to connect to your Secure File Transfer Protocol (SFTP) server for the first time, they’ll see an alert indicating that their client doesn’t recognize the host it’s connecting to. The warning usually includes a line that shows a key fingerprint and a prompt that asks the user whether to proceed with the connection attempt or not. Here are two examples illustrating what we’re referring to.

Overview

Windows, including Windows 10, lacks a built-in SFTP client, making it challenging for users to securely transfer files to an SFTP server. This post guides Windows users on setting up an alternative solution for secure file transfers.