Live lookups by the free mcstatus.io API - nothing about your query is stored on our side.
Minecraft servers answer a lightweight status handshake - the same one the in-game multiplayer list uses. The response carries the MOTD, the player count and cap, the version, and (for Java) the server icon. This page renders that response as the game would, including the MOTD's color codes. A response proves players can reach the server from the internet; a timeout usually means a port, firewall or DNS problem rather than a crashed server process.
Version mismatches explain most "can't join" reports - a 1.21 client on a 1.20 server needs ViaVersion or an update. A full player list explains queue kicks. And if the checker says online but a specific friend can't connect, the problem is on their side (client version, region blocks or their network), not the server's.
Enter the server address (the same thing you type in the game's server list) and pick Java or Bedrock. The checker pings the server and shows its online state, player count, version and MOTD within a few seconds.
Java Edition uses 25565 (TCP), Bedrock uses 19132 (UDP). If a server runs on the default port you can omit it; otherwise write address:port, for example play.example.com:25566.
The most common causes: the server is still starting up, the port isn't forwarded or is blocked by a firewall, the server is bound to the wrong network interface, or the address/port you entered doesn't match the server's. If you host with a provider, the panel shows the exact address to use.
Yes - switch the edition to Bedrock before checking. Bedrock servers answer on UDP 19132 and report their own version and player counts.