Check addresses with SRV and custom ports
Use the address that players publish, then read the canonical target returned by the API. Java default-port requests may resolve an SRV record; Bedrock requests carry an explicit port.
Java SRV behavior
When a Java hostname is requested without a port, the status service starts from the default port mode and may resolve the hostname’s SRV record before connecting. The response target shows the normalized address and port used for the observation. If you need to bypass SRV, supply the custom port explicitly.
curl 'https://minecraftstatus.com/api/v1/status/java?address=play.example.net:25570'Bedrock ports
Bedrock’s RakNet ping uses an explicit UDP port. The API keeps the Bedrock port in the target identity; it does not silently treat a Java default port as a Bedrock endpoint.
curl 'https://minecraftstatus.com/api/v1/status/bedrock?address=play.example.net:19132'
curl 'https://minecraftstatus.com/api/v1/status/bedrock?address=play.example.net:19133'Resolution limits
- Address syntax is bounded before any outbound work runs.
- DNS and transport failures become canonical Unknown evidence when the bounded observation can complete.
- SRV resolution is part of Java target normalization; it is not a separate application-level promise of joinability.
Contract boundary
Use target.targetId as the stable identity returned by the contract. Do not create a second identity by concatenating an unnormalized input string.