We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Minecraft Server Status Checker
If this tool helped you, you can buy us a coffee ☕
Check a public Minecraft Java or Bedrock server for status, version, players, MOTD, resolved port, SRV routing, and response time.
Choose an edition and enter a server address to see status, version, players, and response time.
A running process in a hosting panel does not prove that players can reach the server. DNS records, SRV routing, port forwarding, firewall rules, or the selected edition may still be wrong. Enter a public hostname or IP and choose Java or Bedrock. The checker sends one Minecraft status request and reports whether it received a valid response, along with version, player count, capacity, MOTD, endpoint, and response time.
Use the result after a new launch, a host migration, a DNS change, or a port update. It can also help triage a player report by separating an invalid address from an endpoint that is not answering as expected. The check does not join the world, authenticate a player, start a process, or read account data.
Java Edition uses TCP Server List Ping. The checker opens a TCP connection, sends a handshake and status request, then parses the returned JSON. When no port is supplied for a domain, it first looks for a _minecraft._tcp SRV record. A valid record selects the actual host and port; otherwise Java uses the standard port 25565.
Bedrock Edition uses UDP RakNet Unconnected Ping and defaults to 19132. Its response commonly includes version, online players, capacity, MOTD, and game mode. The protocols are not interchangeable. If one domain fronts both editions, check each edition with the port assigned to that service.
http://, a URL path, or a port in the address field.For example, enter only play.example.com for a Java endpoint using SRV. If a Bedrock provider supplies port 19140, select Bedrock and enter 19140 explicitly.
Server online means the endpoint returned structured Minecraft status data, not merely that a socket opened. Player counts are declared by the server and can be changed by proxies, plugins, privacy settings, or caching. They are useful as a current capacity signal but are not a player-audit record. A proxy may advertise a supported version range rather than the exact version of every backend world.
Response time measures the path from the ToolKK probe to the status response and includes network and server processing. It is not the same as a player's in-game ping from another location. MOTD formatting is reduced to safe plain text, and a Java PNG favicon is displayed only after type and size checks.
A DNS failure can indicate a misspelled name or missing A, AAAA, or SRV record. A timeout can come from a dropped firewall packet, missing NAT forwarding, an unhealthy route, or a slow server. Connection refused normally means the host is reachable but nothing accepts that port. Invalid response often means the wrong edition was selected or another service is running on the port.
The page labels these outcomes as status not confirmed instead of definitely offline. Check process logs, listening interfaces, security groups, router forwarding, and proxy configuration, then repeat the test from another network. A single remote probe is evidence for troubleshooting, not a complete uptime monitor.
The API connects only to resolved public addresses. Loopback, private, link-local, multicast, reserved, and documentation ranges are rejected, including targets reached through DNS or SRV. For Java virtual-host recognition, the original hostname stays in the handshake while the TCP socket connects directly to a validated public IP. This reduces private-network scanning and DNS-rebinding risk.
Each probe has a short timeout and response-size ceiling. Identical targets are cached briefly to avoid unnecessary load. ToolLimit currently allows 2 daily checks for guests, 5 for regular users, and 20 for PRO users, subject to the allowance returned by the account service. The endpoint also applies a separate burst limit.
Why does the player count differ from the console? Proxies, plugins, hidden-player settings, and cache layers can alter the public status response.
Why did the checker use another port? A Java SRV record can route the domain to a different host and port; the result marks when SRV was used.
Does it support modded or proxy servers? Usually, if the public entry point implements standard Java Status or Bedrock RakNet Ping. Nonstandard proxies may omit fields.
Can it check a LAN server? No. Private and reserved targets are blocked; check them locally from an authorized device.
Does the server run a command? No. The implementation sends protocol packets with Node TCP or UDP sockets and never executes user input.