Port / TCP
25565Minecraft server
The default listener for Minecraft: Java Edition servers.
If it is internet-facing: Port 25565 is legitimate in the right place, but exposed carelessly it widens the attack surface noticeably.
Exposure
Internet-facing
Transport
Encryption optional
Risk if public
Elevated
Exposure verdict
Port 25565 normally answers from the internet, but the transport is not confidential by default. Enforce the encrypted variant before the traffic leaves your network.
Encryption is available but negotiated or configured rather than guaranteed. A client that does not insist on it will silently fall back to plaintext.
Registered with IANA on request, but bindable by any unprivileged user. Registration records intent — it does not reserve the port, so collisions between products are common.
Grouped with the other messaging & media ports so a rule written for one can be checked against its neighbours.
What actually goes wrong
2 notes- Enable online-mode so accounts are verified against Mojang; offline mode lets anyone claim any username.
- Servers are routinely scanned, catalogued, and targeted with griefing bots and DDoS.
Recommended firewall rule
Allow it, and harden the service
This port is expected to answer from anywhere, so the firewall is not where its security comes from.
ufw
sudo ufw allow 25565/tcpiptables
sudo iptables -A INPUT -p tcp --dport 25565 -j ACCEPTCheck what is really there
Listening locally
sudo ss -tlpn 'sport = :25565'The bind address is the answer that matters: 127.0.0.1 is local-only, 0.0.0.0 and :: mean every interface.
Listening (macOS)
sudo lsof -nP -iTCP:25565 -sTCP:LISTENmacOS ships lsof rather than ss; this names the owning process and user.
From outside
nmap -sV -Pn -p 25565 <host>A version probe confirms whether Minecraft server is actually what answers, rather than trusting the number. Only scan hosts you are authorised to test.
Reachability
nc -vz <host> 25565The quick yes/no when you only need to know whether a path exists through the firewall.