FTP (File Transfer Protocol)
What is FTP (File Transfer Protocol)?
FTP (RFC 959) is a decades-old protocol for transferring files between a client and server, typically on port 21, whose USER and PASS commands send a login's username and password as plain, unencrypted text. AdminKit's guide checks whether a device's FTP port is actually reachable from the public internet.
By AdminKit team, Netbase JSC · Updated
FTP (RFC 959) transfers files between a client and server over two separate TCP connections: a control connection, normally on port 21, that carries commands and replies, and a second data connection — opened by either side depending on active or passive mode — that actually moves file contents. RFC 959 defines the USER and PASS commands that authenticate a login, and the RFC itself never hides that these cross the control connection as plain text; it only asks client software to hide the password on screen, not to encrypt it on the wire. FTPS wraps the same commands in TLS, and SFTP is a different protocol entirely that runs over SSH — both exist precisely because plain FTP never gained encryption of its own. MDN Web Docs is blunt about it, calling FTP an insecure protocol that many hosting accounts no longer support and recommending SFTP or another secure transfer method instead. A reachable, unencrypted port 21 today usually means a legacy system nobody has migrated off plain FTP, the same unencrypted-protocol risk NIST’s general server security guidance calls out when recommending authenticated services run over an encrypted channel; AdminKit’s open ports check can confirm whether port 21 actually answers from the public internet before worrying about what it exposes.
FTP’s plaintext credentials put it in the same legacy-protocol category as Telnet, another decades-old protocol that sends everything, including logins, unencrypted.
AdminKit groups fTP (File Transfer Protocol) under its machine protocols cluster — browse the AdminKit glossary index for other related terms.
Frequently asked questions
Does FTP encrypt login credentials?
No -- RFC 959's USER and PASS commands send a username and password as plain, unencrypted text over the control connection; the RFC only asks client software to hide the password on screen.
What's the difference between FTP, FTPS and SFTP?
FTPS wraps the same FTP commands in TLS; SFTP is a different protocol entirely that runs over SSH -- both exist because plain FTP never gained encryption of its own.
Why does FTP use two separate connections?
A control connection, normally on port 21, carries commands and replies, while a second data connection -- opened by either side depending on active or passive mode -- actually moves file contents.
What does a reachable, unencrypted port 21 usually mean today?
Usually a legacy system nobody has migrated off plain FTP, since FTPS and SFTP have been the standard safer alternatives for years.