Port 21FTP Control
Port 21 is primarily used for FTP (File Transfer Protocol) command and control communications, facilitating file transfer sessions between a client and server. It manages authentication and commands that initiate data transfers on a separate data port..
- transport
- tcp
- in transit
- cleartext
- assignment
- official
- risk
- 3/10
- lookups
- 14,302
single transport
payload readable on path
registered with iana
caution
rank 245 of 993 · top 25%
Technical Details
what runs on :21-
FTP Overview: The File Transfer Protocol (FTP) is a standard network protocol used for transferring files between a client and server over a TCP/IP network. Port 21 specifically handles the command channel, where session negotiation, user authentication, and instructions like
PUT,GET, orLISTare exchanged. -
Communication Process: When an FTP connection is established, port 21 manages the control commands which coordinate the transfer process. Actual file data is transmitted over a separate data port, typically port 20 in active mode or a dynamically allocated port in passive mode. The separation ensures command integrity while allowing flexible data conversations.
-
Operational Modes: FTP operates in two modes: active and passive. In active mode, the server initiates the data connection back to the client, which requires specific firewall configurations. Passive mode, more firewall-friendly, has the client initiating both connections, improving compatibility with NAT environments but potentially exposing dynamic high-number ports.
Security Information
exposure of :21risk score
3/ 10caution
worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.
file transfer averages 4.1 across 114 ports — this one sits 1.1 below.
in transit
cleartext
credentials and payloads are readable by anyone on path
assignment
official
registered with iana for this service — scanners fingerprint it by number
reachable over
tcp
every listening transport is another surface to filter at the edge
security overview
-
Common Vulnerabilities:
- FTP transmits data, including usernames and passwords, unencrypted, making it susceptible to eavesdropping and Man-in-the-Middle (MitM) attacks.
- Anonymous FTP access may expose sensitive directories inadvertently.
- Weak authentication or outdated software versions increase the risk of brute force attacks or exploitation.
- Open control channels can be used for command injection or session hijacking.
-
Common Mitigations:
- Replace FTP with secure alternatives like FTPS (FTP Secure) or SFTP (SSH File Transfer Protocol).
- Enforce strong authentication, disable anonymous access, and employ account lockout policies.
- Use TLS encryption to protect control and data channels.
- Implement strict firewall rules: limit access to trusted IP ranges and monitor for unusual activity.
- Regularly update FTP server software and audit logs for intrusion attempts.
Related Ports
the 8 most looked-up other ports in file transfer — 114 ports carry that label.
| port | service | risk | |||
|---|---|---|---|---|---|
| :9080 | Groove RPC | TCPUDP | Web Services | caution | 70.8k |
| :17500 | Dropbox LAN Sync | TCPUDP | File Transfer | caution | 43.7k |
| :548 | Apple Filing Protocol | TCP | File Transfer | caution | 36.8k |
| :7000 | Vuze HTTPS Tracker | TCPtls | Security | caution | 28.9k |
| :1337 | PowerFolder P2P | TCP | Security | caution | 27.1k |
| :9001 | SharePoint Authoring | Web Services | caution | 26.3k | |
| :8080 | FilePhile Relay | UDP | File Transfer | caution | 25.6k |
| :1337 | WASTE Encrypted Sharing | TCP | Security | caution | 22.9k |
risk mix of the 8 listed
- caution100%
1 of 8 encrypted