Read FiveM server diagnostics without false offline claims
Interpret complete, partial, unavailable, timeout, DNS, RDAP, and runtime signals as bounded evidence.
Diagnostics are strongest when they explain what was checked instead of reducing many systems to a green or red badge. A join service, public server JSON, DNS resolver, and RDAP registry can fail independently. cfxfind shows those boundaries so a reader can act on evidence without overstating it.
Complete versus partial
A complete result means every source attempted for that lookup returned an acceptable response. A partial result means at least one useful fact exists while another source timed out, failed validation, or was unavailable. Neither label alone measures gameplay quality or process uptime. cfxfind resolves only public evidence. A CFX code is checked through the public join service; a server endpoint is then queried through its published JSON routes, while DNS and RDAP describe the public network. Each source keeps its own status, so one successful source never hides a timeout elsewhere.
Follow the source trail
Start with the source status and stable error code, then compare the normalized fragment with the overview. DNS success plus JSON timeout suggests a different investigation from join failure, and RDAP failure affects ownership context rather than proving the game port is closed. Every result is a live snapshot, not a stored server history. Values can change immediately after the check, and a timeout means that a source could not be verified within the deadline. It does not establish that the game server is offline, empty, misconfigured, or permanently unreachable.
Turn evidence into a next check
Repeat the lookup after a short interval, test the advertised connection from an appropriate client, and consult your own hosting logs if you administer the server. Preserve checked times when comparing observations, because changing builds, DNS, players, and resources are expected. The lookup never needs a player account, server password, RCON credential, or private address. Restricted targets are blocked, sensitive convars are redacted, and only server-local player IDs may appear. Use the evidence for diagnosis, then confirm administrative conclusions with systems you control.
FAQ
Does a missing value prove that the server is offline?
No. Missing data can result from a timeout, a disabled public route, a changed endpoint, or a temporary upstream failure. Read the source status and checked time before drawing a conclusion.
Does cfxfind keep a history of these results?
No. The service returns a current public snapshot and briefly caches successful lookups for performance. It creates no account and stores no lookup history for later profiling.