Why can't mcsrvstat.us find my Minecraft server?

Updated

mcsrvstat.us can't find your server when the address you entered doesn't match the server's actual connection address, when the server type (Java vs. Bedrock) is set wrong, when the server is offline, or when the server doesn't allow the type of query the site uses. The site states it supports "Minecraft Java (1.7+), Minecraft Bedrock or servers with enable-query=true," so a server that is online but not queryable can still fail to appear.

Check the server address first

The address field expects the hostname or IP players actually connect to, not a display name or a control-panel label.

  • Use the exact address from your server's connection info (for example play.example.com or an IP like 203.0.113.10).
  • Don't add a protocol prefix such as http:// or minecraft://.
  • Don't include a port unless your server runs on a non-default one. If it does, include it as address:port.
  • Watch for typos, extra spaces, and copy-paste artifacts from chat or web pages.

If you don't have a server to test with, the site offers sample addresses you can try, such as play.mineluxmc.com (Bedrock), performium.net (Java), and mc.manacube.net (Java). If a sample works but yours doesn't, the problem is on your server's side, not the site.

Match the server type to your server

The site distinguishes between Minecraft Java and Minecraft Bedrock, and the wrong selection produces a failed lookup even for a healthy server.

Your server What to select
Java Edition 1.7 or newer Minecraft Java
Bedrock Edition (including many console/mobile cross-play servers) Bedrock
Java server with enable-query=true Java (query is used as a fallback path)

Common mix-ups:

  • A Bedrock server checked as Java (or the reverse) will not resolve.
  • Cross-play servers often expose separate Java and Bedrock addresses. Use the address that matches the edition you selected.
  • Some hosts give you a numeric IP for Bedrock and a hostname for Java; they are not interchangeable.

Confirm the server is actually online and reachable

A lookup fails if the server is down, restarting, or unreachable from the public internet.

  • Check the server console or your host's control panel to confirm it is running.
  • If you can, join the server yourself from the same edition. If you can't connect, the status checker won't either.
  • A server that is only reachable on your local network (for example localhost or a 192.168.x.x address) can't be checked from an external service.
  • Firewalls, DDoS protection, or a proxy in front of the server can block the status request even when players can connect.

Check whether the server allows queries

For Java servers, the site notes that servers with enable-query=true are supported. If your server has query disabled and isn't answering the standard status ping, the lookup can fail.

  • In server.properties, enable-query controls the GameSpy4 query protocol; query.port sets the port it listens on.
  • If you enable query, restart the server and make sure the query port is open in your firewall and forwarded if needed.
  • If you don't want to enable query, the server still needs to respond to the normal status ping that clients use in the multiplayer server list. A server that hides itself from that list may not be checkable.

Quick troubleshooting order

  1. Re-enter the address exactly as players use it, with no prefix and the correct port if any.
  2. Switch between Java and Bedrock and try again.
  3. Test a known sample address to confirm the site itself is working.
  4. Verify the server is online and joinable from outside your network.
  5. If it's a Java server, check enable-query and the query port, then retry.

If a sample address works and your server is online, joinable, and set to the right edition, the remaining likely cause is that your server isn't answering status or query requests — which is a server configuration issue, not a problem with mcsrvstat.us.