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 .
Was this tool helpful to use?
Your feedback helps us make it better
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.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
A Minecraft server status check submits a status query to the address you provide and displays the fields returned by that server. Choose Java Edition or Bedrock Edition, enter a hostname or IP address, and optionally specify a port. The result can include an online response, version, player count, message of the day (MOTD), response time, and other edition-dependent details.
A status response is a point-in-time observation from the checker. It can help you see whether a server answered and what information it reported, but it is not a guarantee that your game client can join. The client’s route, version compatibility, account access, firewall rules, server capacity, and connection conditions can differ from a status probe.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Choose the edition that matches the server endpoint you intend to check. The edition selection affects how the status request is made.
Use the server hostname or IP address. If the server requires a non-default port, enter it as a separate port value; ports must be from 1 to 65,535.
Start the check and review the status plus any reported version, players, MOTD, response time, or other available details. The checked time helps you understand when the observation was made.
If a server is shared with both editions, check the edition-specific address and port supplied by its owner. Do not assume one successful edition check covers the other endpoint.
Use cases
See how the tool fits into real work and everyday tasks.
A player can check the supplied host and edition, then compare the returned version and MOTD with the server information before opening the game.
An administrator can test a hostname after updating an address or port and inspect whether the expected server information responds.
Record the check time, selected edition, address, and returned status when reporting a connection issue. This gives support a concrete observation to compare with the player’s own client test.
Q&A
Find concise answers to common questions and confusing cases.
No. It means the status request received a response. Joining also depends on the game client, server rules, network path, edition, and other access conditions.
The hostname or port may be wrong, the selected edition may not match, or the server or network may not answer this kind of status request. Verify the connection details with the server owner.
Only when the selected endpoint returns those fields. Some servers omit or customize status details, so a missing field does not by itself explain a connection failure.
Notes
Review scope, result limitations, and important precautions before use.
Status checks report what responded to a probe at a particular time; they do not certify continuous availability or gameplay connectivity.
Related
Discover related tools, collections, and available API capabilities.