FTP is the oldest and best-known way to upload website files. Many developers and site owners still use it out of habit: it is simple, every host offers it, and FileZilla connects in a couple of clicks. The trouble is that FTP was designed in the 1970s and 80s, when nobody worried much about someone watching network traffic. Today plain FTP is one of the most common weak spots in website security.
Why plain FTP is dangerous
Plain FTP sends your username, password and files unencrypted. When connecting, the client sends USER and PASS commands as plain text. On public Wi-Fi in a café, hotel or airport, another device on the network or a badly configured router can capture that traffic and read the password directly; a free analyser like Wireshark shows it at a glance. With the password, an attacker can inject code into index.php, hide a web shell or add redirects, often without the owner noticing for weeks. The site keeps loading normally while search engines flag it as dangerous or the server starts sending spam.
FTPS and SFTP are different things
FTPS is the same old FTP wrapped in TLS, usually on port 21 (explicit TLS) or 990 (implicit TLS). It protects your data but opens extra data ports, which can cause trouble behind firewalls and NAT. SFTP has nothing to do with FTP: it is file transfer inside SSH, normally over a single encrypted connection on port 22, and it supports key-based login. Prefer SFTP, fall back to FTPS, and avoid plain FTP entirely.
| Protocol | Encryption | Typical port | Key login |
|---|---|---|---|
| FTP | None | 21 | No |
| FTPS | TLS | 21 or 990 | No (client certs possible) |
| SFTP | SSH | 22 | Yes |
Example: a school website in Namangan
A computer-science teacher maintains a school site in Namangan and uploads timetables from a café's Wi-Fi using FileZilla set to plain FTP. One day casino ads appear and homepage links start redirecting elsewhere. The investigation shows the FTP password was sniffed and the files were changed through that account. Over SFTP the captured traffic would have been useless.
Switching to SFTP in FileZilla
Open the Site Manager, pick the site and set Protocol to "SFTP - SSH File Transfer Protocol". Leave the port empty for 22 or enter the one your host gives you. On first connect FileZilla shows the server key fingerprint; if it ever changes, you will be warned, which protects against fake servers. FileZilla stores passwords locally, so enable a master password or do not save them. WinSCP is a good alternative on Windows.
SFTP, SCP and rsync from the command line
# interactive SFTP session
sftp deploy@example.uz
sftp> cd public_html
sftp> put index.php
# copy one file
scp style.css deploy@example.uz:public_html/assets/
# sync only changed files over SSH
rsync -avz -e ssh ./site/ deploy@example.uz:public_html/
For a non-standard port use -P 2222 with sftp and scp, and -e "ssh -p 2222" with rsync. Because rsync only transfers files that differ, it is the fastest way to update a large site, and adding --dry-run first shows exactly what would change before anything is copied.
Cleaning up afterwards
Review old FTP accounts: hosts often keep users created years ago for a contractor. Delete them or at least change their passwords. If some legacy device or accounting tool only speaks FTP, give it a separate account limited to one folder and enable FTPS. On shared hosting, SFTP and SSH availability can depend on the plan and account settings; for sayt.uz hosting you can check your connection details in the cabinet or ask support. Whatever you choose, the rule is the same: your password should never cross the network in plain text.