bitlvl
EN

Port 465 SMTPS · TCP

SMTP submission over implicit TLS (SMTPS). It was deprecated in favour of 587 with STARTTLS, then re-standardised in RFC 8314 because implicit TLS is simpler and cannot be stripped.

Port465
TransportTCP
ServiceSMTPS — Mail submission over implicit TLS
CategoryMail
Rangewell-known (0–1023, needs root to bind on Unix)
EncryptedYes, always (TLS or equivalent)
ExposureDesigned to face the internet

What runs on port 465

SMTP submission over implicit TLS (SMTPS). It was deprecated in favour of 587 with STARTTLS, then re-standardised in RFC 8314 because implicit TLS is simpler and cannot be stripped. Mail clients and applications submit outgoing mail here with authentication; servers do not use it between themselves.

Software that uses it: Postfix (smtps in master.cf) · Exim · Exchange · Gmail/Outlook SMTP servers for clients

Should port 465 be open?

Designed to face the internet. This port exists to be reachable from anywhere, so the usual question is not whether to open it but how the service behind it is configured and patched.

Check port 465

# on the host: is anything listening, and which process?
ss -ltnp 'sport = :465'
sudo lsof -i :465

# from another machine: is it reachable?
nc -zv host 465
nmap -p 465 host
curl -v telnet://host:465      # 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 465

# ufw (Ubuntu/Debian)
sudo ufw allow from 10.0.0.0/8 to any port 465 proto tcp
sudo ufw deny 465/tcp

# nftables
nft add rule inet filter input ip saddr 10.0.0.0/8 tcp dport 465 accept
nft add rule inet filter input tcp dport 465 drop

# iptables (legacy)
iptables -A INPUT -p tcp --dport 465 -s 10.0.0.0/8 -j ACCEPT
iptables -A INPUT -p tcp --dport 465 -j DROP

# firewalld
sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source address=10.0.0.0/8 port port=465 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 465" 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 465 TCP or UDP?

TCP. SMTPS is a connection-oriented protocol; there is no UDP service on 465 by default (a scanner reporting UDP 465 open is usually seeing a filtered port).

Is port 465 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 465 is open?

On the server, ss -ltnp (or -lunp for UDP) shows whether something listens on 465 and which process. From another machine, nc -zv host 465 or nmap -p 465 host tests reachability. "Open" in a scan means something answered; a firewall usually makes the port filtered (no answer) rather than closed (RST).

Can SMTPS 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.