What does a server status check do?
A status check for Minecraft servers sends a very short request to the server, exactly the same one the game client sends when displaying the server list. The server replies with a JSON-like dataset containing version, MOTD, player count, max slots and protocol version. No login takes place, no slot is occupied, and ongoing gameplay is not affected.
- Java Edition: TCP on port 25565 (default), Server List Ping protocol
- Bedrock Edition: UDP on port 19132 (default), Unconnected Pong over RakNet
- SRV records are resolved automatically; you can enter the hostname without a port
- IPv4 and IPv6 are supported, provided the server is reachable accordingly
MOTD, SRV and protocol versions explained
MOTD stands for Message of the Day. It's the text shown beneath the server name in the in-game server list. Server operators use this area for slogans, IPs, Discord links or colored status messages. Color and formatting codes (section sign codes) are shown here in cleaned plain text form so the result stays readable.
SRV-Records are special DNS entries that map a service (here: Minecraft) to an actual hostname plus port. Example: a player types play.example.com into the client. The client queries _minecraft._tcp.play.example.com, gets back mc01.hoster.net:25577 and connects there. This lets servers move internally without players having to update the address.
The protocol version (e.g. 765 for Java 1.20.4) decides which client versions a server can talk to. Plugins like ViaVersion widen the range so a server can accept multiple client versions at once.
Why my server shows as offline
If your server is actually running but shows up as offline here, these are the typical causes you can check in this order:
- Firewall: Port 25565 (Java) or 19132 (Bedrock) is blocked from outside. Check UFW, iptables, Hetzner firewall, Windows Firewall as applicable.
- Bind address: the server binds to
127.0.0.1 instead of 0.0.0.0, so it's only reachable locally.
- Wrong DNS record: the A or AAAA record points to a different IP than the server's.
- SRV record broken: if you're using a non-default port, you must set an SRV record, otherwise the client looks for the default port.
- Server properties:
enable-status=true must be set, otherwise the server doesn't respond to pings.
- Bedrock and UDP: in home network setups people often forget the UDP port forward (not TCP).
- CGNAT at the ISP: connections behind Carrier-Grade NAT often aren't reachable from outside; you'll need a VPS or tunnel.
Privacy and limits
The status check runs through the public API of mcstatus.io. We only forward the server address you entered. No cookies are set, there is no tracking, and requests are not stored long-term. Web server logs (for security and rate limiting) are deleted after a short period.
- 30 requests per minute per IP address
- hCaptcha protects the form against automated abuse
- Private and reserved IP ranges are blocked server-side (anti-SSRF)
- No tracking, no analytics script, no third-party cookies