BRev Port 25565 — Minecraft (Java Edition)
Port 25565/TCP is the default for a Minecraft Java Edition server, and it is the port behind most home port-forwarding attempts. Bedrock Edition is different — UDP 19132 — which is why a forward that works for one platform does nothing for the other, a very common source of confusion when a household plays on both.
Forwarding it means exposing the server process, and the honest framing is that you are running a public internet service on your home network. Our reference marks it care: keep the server patched, enable the whitelist so only known accounts can join, keep online-mode on so Mojang authentication is enforced, and ideally run it on an isolated machine or VLAN rather than the box that also holds your files. Server-list scanners index public Minecraft servers continuously, so an unlisted address is not private.
The Log4Shell episode in December 2021 is why the patching line is not boilerplate: a crafted chat message could trigger remote code execution on both server and connecting clients through Log4j. Minecraft was one of the most visible affected applications, and it made the point that a game server is a program parsing hostile input from strangers, with the same requirements as any other.
Port 25565 at a glance
| Field | Value | Detail |
|---|---|---|
| Port | 25565 | Registered |
| Service | Minecraft Java | The Java-edition server port. (TCP) |
| Category | Games & voice | game servers and voice chat |
| Exposure | Care | Expose with care |
Should port 25565 face the internet? Public game server: whitelist it, keep it patched (see Log4Shell), and isolate the host.
Legitimately public in some setups, but only hardened — current version, real authentication, rate limits, and ideally an allow-list.
What commonly goes wrong
Friends cannot connect and the forward looks correct
Check CGNAT before the router. Many ISPs put homes behind carrier-grade NAT, so no port forward can work — the public address is not yours. Compare the address your router reports on its WAN interface with your public address; if they differ, you are behind CGNAT and need a tunnel or a hosted server. Also confirm server-ip in server.properties is blank rather than bound to a stale address.
It works inside the house and not from outside
Usually NAT loopback (hairpinning) making the internal test misleading — internal clients reach the server directly regardless of the forward. Test from a phone on mobile data, not from the same network. If the internal test also fails, the server is not listening where you think it is.
Check port 25565 yourself
No browser can open a raw TCP socket, so no web page can honestly tell you whether this port is open on a remote host. These are the real commands, generated for port 25565 — swap example.com for the host you are actually testing.
Is port 25565 reachable on another host?
nc -vz example.com 25565"succeeded!" means the TCP handshake completed — the port is open. "Connection refused" is closed; a hang until timeout means filtered (a firewall dropped it silently).
nmap -Pn -p 25565 example.comThe only common tool that distinguishes open / closed / filtered. -Pn skips the ping sweep, so it still works against hosts that ignore ICMP.
Test-NetConnection example.com -Port 25565Read TcpTestSucceeded: True = open. It is built in — nothing to install.
telnet example.com 25565A blank screen or a banner means it connected. "Connection refused" means closed. Quit with Ctrl-] then `quit`.
curl -v --max-time 5 telnet://example.com:25565Handy when telnet is not installed: "Connected to …" proves the TCP handshake, without curl trying to speak HTTP.
What on this machine is holding port 25565?
sudo ss -tlnp | grep :25565Lists the listening socket and the PID/program holding it. Drop sudo and you get the socket but not the process name.
sudo lsof -i :25565The macOS answer to "address already in use". Kill it with `kill -9 <PID>` once you are sure what it is.
netstat -ano | findstr :25565The last column is the PID. Match it in Task Manager’s Details tab, or `taskkill /PID <pid> /F`.
No web page can tell you whether a port is open on a remote host
A browser cannot open a raw TCP socket — there is no API for it, by design. So a site that reports “port 3389 is OPEN on 203.0.113.10” is not checking from your browser; it is asking its own server to scan on your behalf. That works, but it means their server sees the host you asked about, scans from their address rather than yours, and answers a question about their network path, not yours.
We don't have a server here and won't pretend to. So this page does three honest things instead:
| Port | Proto | Service | What it is | Exposure | |
|---|---|---|---|---|---|
| 25565 | tcp | Minecraft Java | The Java-edition server port.Public game server: whitelist it, keep it patched (see Log4Shell), and isolate the host. | Care |
http://host:port/ and times it. A connection that is established proves a socket is open; an instant refusal usually means nothing is listening; anything else is honestly reported as “can't tell”. Each attempt gives up after 2.5s.nc -vz example.com 443
nmap -Pn -p 443 example.com
telnet example.com 443
curl -v --max-time 5 telnet://example.com:443
This page cannot answer that, and neither can any other page — from your browser. Opening a TCP connection to an arbitrary host and port is not something JavaScript is allowed to do. Every “open port checker” that gives you a green tick is running the scan on their server. Which is fine, as long as you know what you are agreeing to: they learn which host and port you were worried about, and the answer they give you is about the route from their data centre — not from the internet as your users see it.
What to do instead
Run the check from outside your own network. Copy an nmap or nc line from the card above and run it from a machine that is not behind the same router — a phone on mobile data with a terminal app, a cheap VPS, a colleague's laptop. Running it from inside the LAN tests the LAN, not the internet, and will happily say “open” while the world sees nothing.
Then check the thing that is actually blocking it, in this order: the service is bound to0.0.0.0 and not 127.0.0.1 · the host firewall (ufw, firewalld, Windows Defender Firewall) · the cloud security group or the router's port-forward rule · and finally your ISP, which commonly blocks 25, 80 and 445 on residential lines whatever you configure.
What a browser genuinely can verify
One thing: that an HTTPS service answers. If what you actually want to know is “is my site up and how fast is it”, the latency test measures real round trips to a CORS-open URL. If the name doesn't resolve, or resolves somewhere unexpected, that is a DNS problem, not a port problem — and it is the more common cause of “my port is closed” than an actual firewall.
An IP address finds the machine; a port picks which program on it gets the traffic. TCP sets up a connection first — a handshake, ordered delivery, retransmission — which is why the web, email and SSH use it. UDP just sends the packet with no handshake and no guarantee it arrives, which is why DNS, video calls and games use it: late data is worse than lost data.
That difference is why a UDP port is so much harder to test. TCP either completes a handshake or it doesn't, so a tool can tell you. A UDP service that has nothing to say to an unexpected packet stays silent — and silence looks identical to a firewall dropping it.
The three ranges
0–1023Assigned by IANA to core services. On Unix, binding one needs root (or CAP_NET_BIND_SERVICE).1024–49151Registered by vendors for their applications. Any user can bind these — which is why every dev server lives here.49152–65535Never assigned. The OS hands these out as the SOURCE port of your outgoing connections. (Linux actually uses 32768–60999 by default.)Closed is not the same as filtered
Closed means the host answered: the packet arrived, nothing is listening, and you got an immediate refusal (a TCP RST). Filtered means nothing answered at all — a firewall dropped your packet in silence, so you wait for a timeout and learn nothing. The difference matters: closed proves the host is reachable and the port is free; filtered tells you only that something between you and it is discarding traffic.nmap reports the two separately. A browser cannot distinguish them, which is why this page reports a timeout as “can't tell” rather than guessing.
The one habit worth keeping
Bind services to 127.0.0.1 instead of 0.0.0.0 unless something outside the machine genuinely needs them, and reach them over SSH or a VPN. Every database on the never-expose list above ships with that advice, and the leaks all begin the same way: a default bind address, a cloud instance with a public IP, and a scanner that found it within the hour.
The blocked-port list this page uses is the WHATWG Fetch Standard's “bad port” table — the ports every browser refuses to connect to (Chrome calls it ERR_UNSAFE_PORT). Local probing is additionally gated by Chrome's Local Network Access permission, which replaced Private Network Access and ships in Chrome 142.
FAQ
Is it safe to port forward 25565?
It is a normal thing to do for a game server, with the usual conditions: keep the server and its plugins patched, use the whitelist, keep online-mode enabled, and isolate the host from the rest of your network. You are running a public service.
Why does Bedrock not connect to my server?
Bedrock Edition uses UDP 19132 and a different protocol entirely; 25565 is Java Edition only. Cross-play needs a proxy such as Geyser, plus the corresponding UDP forward.
Can players join without typing the port?
Yes — publish an SRV record (_minecraft._tcp) pointing at the host and port, and the client resolves it automatically. That also lets you move the server or change the port without telling anyone.