| Port | 990 |
|---|---|
| Transport | TCP |
| Service | FTPS (implicit) — FTP over TLS from the first byte |
| Category | File transfer and sharing |
| Range | well-known (0–1023, needs root to bind on Unix) |
| Encrypted | Yes, always (TLS or equivalent) |
| Exposure | Internet-facing only with authentication and care |
Port 990 FTPS (implicit) · TCP
FTPS with implicit TLS: the TLS handshake happens before any FTP command, as with HTTPS.
What runs on port 990
FTPS with implicit TLS: the TLS handshake happens before any FTP command, as with HTTPS. Explicit FTPS on port 21 (AUTH TLS) is the standardised form; implicit on 990 is older but still widely deployed by hosting panels and banks' file-exchange systems. Both still need a passive port range opened.
Software that uses it: vsftpd · ProFTPD · FileZilla Server · IIS FTP · Cerberus, Serv-U
Should port 990 be open?
Internet-facing only with authentication and care. It can be exposed when the service behind it is authenticated, rate-limited and kept up to date; most deployments are better off behind a VPN, an allow-list or a reverse proxy.
- Set pasv_min_port/pasv_max_port and open that range too, or transfers hang after login.
Check port 990
# on the host: is anything listening, and which process? ss -ltnp 'sport = :990' sudo lsof -i :990 # from another machine: is it reachable? nc -zv host 990 nmap -p 990 host curl -v telnet://host:990 # raw TCP connect test, Ctrl-C to leave
A port that answers from the internet when it should not is the finding; nmap from a machine outside your network (or a VPS) is the honest test, because scans from inside the LAN pass the firewall you are trying to verify.
Allow or block port 990
# ufw (Ubuntu/Debian) sudo ufw allow from 10.0.0.0/8 to any port 990 proto tcp sudo ufw deny 990/tcp # nftables nft add rule inet filter input ip saddr 10.0.0.0/8 tcp dport 990 accept nft add rule inet filter input tcp dport 990 drop # iptables (legacy) iptables -A INPUT -p tcp --dport 990 -s 10.0.0.0/8 -j ACCEPT iptables -A INPUT -p tcp --dport 990 -j DROP # firewalld sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source address=10.0.0.0/8 port port=990 protocol=tcp accept'
Replace 10.0.0.0/8 with the networks that need access. Allowing by source address is the rule that matters; "allow 990" with no source is just "open".
Related ports
Part of the port number reference. Ports are 16-bit numbers; see also the subnet calculator and the packet decoder, which shows ports inside TCP and UDP headers.
Questions
Is port 990 TCP or UDP?
TCP. FTPS (implicit) is a connection-oriented protocol; there is no UDP service on 990 by default (a scanner reporting UDP 990 open is usually seeing a filtered port).
Is port 990 encrypted?
Yes, always (TLS or equivalent). The port number does not make it safe by itself: certificate validation, authentication and patching still decide.
How do I check whether port 990 is open?
On the server, ss -ltnp (or -lunp for UDP) shows whether something listens on 990 and which process. From another machine, nc -zv host 990 or nmap -p 990 host tests reachability. "Open" in a scan means something answered; a firewall usually makes the port filtered (no answer) rather than closed (RST).
Can FTPS (implicit) run on a different port?
Yes; the number is a convention, not a requirement. Changing it reduces log noise from scanners but does not add security, and every client, firewall rule and monitoring check then needs the new number. Keep the default unless you have a concrete reason.