Minecraft Server Pinger

Paste the server's hostname or IP into a server-list ping tool (like this one) and hit Ping. The tool sends the same handshake packet that the in-game multiplayer browser uses, so if it succeeds, your client will be able to connect too. If the ping fails, the server is offline, the firewall is blocking the port, or the address is wrong.

Java Edition servers default to TCP 25565 — the long-standing port for the Minecraft handshake protocol. Bedrock Edition (Windows 10, mobile, console) uses UDP 19132 with a different RakNet-based protocol. The two are not interchangeable: pinging a Java server on 19132 returns nothing, and vice versa. Some hosts run both side by side via Geyser/Floodgate proxies.

Three usual culprits: (1) physical distance — every 1,000 km of fibre adds roughly 10 ms one-way; (2) overloaded server tick — if the server's TPS drops below 20, response packets queue behind game logic; (3) ISP routing — residential ISPs sometimes route Minecraft traffic through congested peering links. The latency this tool reports is the round-trip time from our prober to the server, not from your home — your real ping will differ.

Yes. A server-list ping returns the icon as a base64 PNG, which this tool decodes and offers as a download — the file is already the 64×64 server-icon.png vanilla requires. Icons are the server owner's artwork, so use someone else's only with permission.

Call the public Crafty endpoint this page uses: GET https://api.crafty.gg/api/v2/servers/ping?ip=host:port&edition=java (edition=bedrock for Bedrock). It returns JSON with status, players, version, the raw MOTD and the favicon, so you don't have to implement the handshake protocol yourself.