| Port | 65535 |
|---|---|
| Transport | TCP and UDP |
| Service | Highest port — End of the ephemeral range |
| Category | Infrastructure |
| Range | dynamic / private (49152–65535) |
| Encrypted | Not applicable |
| Exposure | Private network or VPN only |
Port 65535 Highest port · TCP and UDP
The highest possible port number (2¹⁶ − 1) and the end of the ephemeral range.
What runs on port 65535
The highest possible port number (2¹⁶ − 1) and the end of the ephemeral range. Nothing standard listens here; it appears in firewall rules as the upper bound of ranges and occasionally as a "hidden" port chosen by someone who thought scanners stop earlier (they do not).
Software that uses it: none by convention
Should port 65535 be open?
Private network or VPN only. Nothing good comes from this port being reachable from the internet. Keep it on an internal network, reach it over a VPN or an SSH tunnel, and firewall it from everything that does not need it.
- Port numbers are 16-bit unsigned: 0–65535. Port 0 is reserved and means "pick one for me" in socket APIs.
Check port 65535
# on the host: is anything listening, and which process? ss -ltnp 'sport = :65535' ss -lunp 'sport = :65535' sudo lsof -i :65535 # from another machine: is it reachable? nc -zv host 65535 nmap -p 65535 host nc -zuv host 65535 sudo nmap -sU -p 65535 host curl -v telnet://host:65535 # 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 65535
# ufw (Ubuntu/Debian)
sudo ufw allow from 10.0.0.0/8 to any port 65535 proto tcp
sudo ufw allow from 10.0.0.0/8 to any port 65535 proto udp
sudo ufw deny 65535/tcp
sudo ufw deny 65535/udp
# nftables
nft add rule inet filter input ip saddr 10.0.0.0/8 meta l4proto { tcp, udp } th dport 65535 accept
nft add rule inet filter input meta l4proto { tcp, udp } th dport 65535 drop
# iptables (legacy)
iptables -A INPUT -p tcp --dport 65535 -s 10.0.0.0/8 -j ACCEPT
iptables -A INPUT -p tcp --dport 65535 -j DROP
iptables -A INPUT -p udp --dport 65535 -s 10.0.0.0/8 -j ACCEPT
iptables -A INPUT -p udp --dport 65535 -j DROP
# firewalld
sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source address=10.0.0.0/8 port port=65535 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 65535" 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 65535 TCP or UDP?
Both. Highest port uses TCP and UDP on 65535: End of the ephemeral range.
Is port 65535 encrypted?
Not applicable. The protocol carries no application data worth encrypting, or encryption is handled at another layer.
How do I check whether port 65535 is open?
On the server, ss -ltnp (or -lunp for UDP) shows whether something listens on 65535 and which process. From another machine, nc -zv host 65535 or nmap -p 65535 host tests reachability. "Open" in a scan means something answered; a firewall usually makes the port filtered (no answer) rather than closed (RST).
Can Highest port 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.