Minecraft 26.3 Turned the Whitelist On. Your Server Probably Didn't Notice.
A fresh Minecraft 26.3 server now ships with white-list=true, so new servers are closed to strangers from the first start. Existing servers that upgraded kept their old value, which for most of them means still open.
For as long as Minecraft has had a dedicated server, a fresh install has been open to anyone who knows the address. The whitelist existed, but it was off unless you turned it on. Scanners that sweep the internet for port 25565 have always found plenty of servers that never did.
Minecraft 26.3 changed that. The second 26.3 snapshot's changelog has one line under server properties: "The white-list property is now true by default." It shipped in the 26.3 release on September 15, 2026. It's the most useful security change Mojang has made to the dedicated server in years, and most existing servers won't get it.
What Changed in Minecraft 26.3
To see exactly what changed, I downloaded six official server JARs, started each once in an empty folder, and compared the server.properties files they generated. The whitelist line:
| Version | white-list default |
|---|---|
| 1.21.4 | false |
| 1.21.8 | false |
| 1.21.11 | false |
| 26.1 | false |
| 26.2 | false |
| 26.3 | true |
enforce-whitelist is still false by default. It controls a narrower case: whether players already online get kicked when they're removed from the list or the whitelist is switched on while they're connected. With it off, a player removed while online stays until they disconnect.
A whitelist that starts on and empty also locks out the owner. On a fresh 26.3 server, add yourself before anyone tries to join:
whitelist add YourName
Run it in the server console. Players who aren't on the list see "You are not white-listed on this server!" instead of joining.
Upgraded Servers Keep the Old Value
This is the part that matters for anyone not starting from scratch. The new default only applies when the server writes a fresh server.properties. If the file already exists, the server reads your values and keeps them.
I tested it: I took a server.properties generated by 26.2, put it next to the 26.3 JAR, and started the server. It came up normally, and the file still said white-list=false.
So the servers that most needed the change, the ones that have been open for years, didn't get it. If your server predates 26.3, check the line yourself:
grep -E '^(white-list|enforce-whitelist)=' server.properties
If you want a private server, set both to true and restart, or run whitelist on in the console.
We recommend reading Hardening the Box: Minecraft Server Security Below the Game to continue reading our selection of content. A whitelist decides who can join the game, and that piece covers the host underneath it: SSH, exposed ports, and the debug flag that hands out code execution.
Hardening the Box: Minecraft Server Security Below the Game Minecraft host hardening: the JDWP flag that grants remote code execution, why RCON leaks its password, SSH defaults, and BMC exposure. SudoSecurity · Santhdium
The Other Defaults That Matter
The whitelist is one line in a file of about seventy. These are the ones with a security effect, with the 26.3 default from the generated file:
| Setting | 26.3 default | What it does |
|---|---|---|
online-mode |
true |
Checks every player's account with Mojang. Turn it off only behind a properly secured proxy. |
white-list |
true |
Only listed players can join. New in 26.3. |
enforce-whitelist |
false |
Kicks online players who aren't on the list when it changes. |
enable-rcon |
false |
Remote console. Its protocol sends the password unencrypted. |
enable-query |
false |
UDP query protocol that reports players and plugins. |
management-server-enabled |
false |
The JSON-RPC management API added in 1.21.9. |
management-server-host |
localhost |
Where that API listens. |
management-server-tls-enabled |
true |
The API requires TLS unless you turn it off. |
enforce-secure-profile |
true |
Requires Mojang-signed chat keys. |
op-permission-level |
4 |
What /op grants. Level 4 is every command, including /stop. |
log-ips |
true |
Writes player IP addresses to the log. |
hide-online-players |
false |
Shows player names in the server list ping. |
enable-status |
true |
Answers server list pings at all. |
The pattern is good. Everything that opens a new way in, RCON, query, and the management API, is off by default, and the management API binds to localhost and insists on TLS when you turn it on. The whitelist was the odd one out, and 26.3 fixed it.
Two defaults are worth changing on a private server. hide-online-players=true stops the server list from telling scanners who plays on it. enforce-whitelist=true makes removing someone take effect immediately.
What Else the Defaults Did Since 1.21
The same comparison shows the rest of what moved:
| Release | Change to the generated file |
|---|---|
| 1.21.8 → 1.21.11 | Added the management-server-* settings and status-heartbeat-interval (Mojang's notes put these in 1.21.9). Removed allow-nether, enable-command-block, pvp, and spawn-monsters, which became game rules. Added enable-code-of-conduct. |
| 26.2 | Added chat-spam-threshold-seconds and command-spam-threshold-seconds, both 10 |
| 26.3 | white-list defaults to true |
The game-rule move catches people out. Those four settings still work, but they're game rules now and live in the world, not the properties file. Editing pvp=false into a 26.3 server.properties does nothing. Use /gamerule in the console instead.
We recommend reading How to Debug Minecraft Server Lag with Spark Profiler (2026 Guide) to continue reading our selection of content. Once the server is locked down, performance is the next thing players notice, and that piece covers finding what's actually slowing it down.
How to Debug Minecraft Server Lag with Spark Profiler (2026 Guide) Your server dropped to 12 TPS. You copied Aikar's flags. You upgraded Java. Nothing changed. That's because JVM flags don't fix plugin bugs. SudoSecurity · Santhdium
What This Doesn't Cover
This covers the vanilla Java Edition server. Paper, Spigot, and other server software read server.properties too, but they add their own config files with their own defaults. I didn't test whether each one picks up the 26.3 whitelist default on a fresh install, so check yours.
A whitelist controls who can log in. It doesn't protect against vulnerabilities in the server or plugins that don't need a login, and it isn't a substitute for a firewall or a secured proxy. Bedrock Edition uses a different server and config and isn't covered.
The Actual Point
Mojang changed one default, and new servers are now private unless the owner opens them. Existing servers stay exactly as open as they were, because the server never overwrites your settings.
Check white-list in your server.properties today. If your server predates 26.3 and you didn't mean for it to be public, it still is.
The defaults and the upgrade test are from my own runs on November 15, 2026: each official server JAR (1.21.4, 1.21.8, 1.21.11, 26.1, 26.2 and 26.3) was downloaded from Mojang's version manifest and started once in an empty folder, and 26.3 was started a second time with a 26.2-generated server.properties. The quote is from Mojang's 26.3 Snapshot 2 changelog. The console command and grep line are standard.
$ tail -f /forums
Discussion
Comments live on the community forums — sign in there to reply.