Resolve a valid alphanumeric code from a `cfx.re/join/...` link to the connect endpoint and public
metadata currently advertised by FiveM. Use the result to diagnose connection and listing problems;
this tool is not a FiveM server directory.

> The published connect endpoint is not necessarily the server's origin IP. Cfx supports hostnames,
> HTTPS connection proxies, listing overrides, and separate game endpoints. Treat the result as the
> endpoint currently advertised for connection, not proof of infrastructure ownership.

## What this resolver does

1. Accepts bounded alphanumeric server codes (5–16 characters) from a Cfx.re join link.
2. Queries FiveM's public server-list backend for the matching listing.
3. Returns the advertised endpoint plus public metadata available to the lookup.
4. Lets you compare that result with the server name or endpoint you expected.

Cfx documents that a join interaction resolves a **connect endpoint** first. That endpoint can be a
host, IP address, URL, or proxy before the client receives the actual game endpoint. See the
[Cfx proxy and connection-flow documentation](https://docs.fivem.net/docs/server-manual/proxy-setup/).

## When the result is useful

### Connection diagnostics

If a join link opens the wrong server or fails unexpectedly, resolve the code and compare the
returned name and endpoint with the server operator's current details.

FiveM also supports direct connection from the F8 console:

```text
connect cfx.re/join/j4r3p7m
connect 203.0.113.10:30120
connect "https://server.example.com/"
```

Use direct connection only with an endpoint you trust. The
[Cfx console-command reference](https://docs.fivem.net/docs/client-manual/console-commands/#connect-server)
documents the supported `connect` forms.

### Server-list registration checks

Server operators can use the resolver to confirm that the public listing currently exposes the
expected project name and connect endpoint. A mismatch is a signal to inspect the server's listing,
proxy, DNS, or endpoint configuration; it is not evidence that the origin server changed.

### Support handoff

When helping another user, the resolved endpoint can narrow the problem to the join-link/listing
layer before investigating firewall, proxy, server, or resource issues.

## What this tool does not do

The resolver does not:

- browse or rank FiveM servers,
- verify server ownership,
- reveal a protected origin IP behind a proxy,
- certify that a server is safe or trustworthy,
- continuously monitor server uptime,
- bypass allowlists, authentication, or access controls.

Looking for a server to play on instead of resolving a join code?
[Browse game servers on ServerRoam](https://serverroam.com/).

## Troubleshooting

| Result | What to check |
| --- | --- |
| **Server not found** | Re-copy the current join code and confirm the server is presently advertised through FiveM. |
| **Lookup temporarily fails** | Retry later; the public upstream service or this site's rate limit may be unavailable. |
| **Hostname instead of an IP** | This can be expected. Cfx supports hostnames and connection proxies. |
| **Endpoint differs from the origin** | This can also be expected when the operator uses a proxy or listing override. |
| **Name or endpoint is unexpected** | Stop and get the current join link from the server operator before connecting. |

Lookups are limited to 10 requests per minute per request IP to protect this site and the upstream
service.

## Privacy and data flow

The lookup is not written to an application database. The request IP is used by an in-memory rate
limiter, and the join code is sent server-side to FiveM's public server endpoint. Standard hosting
or proxy logs may still apply.

## Related guides

- [Connection troubleshooting](/docs/troubleshooting/connection-issues)
- [QBCore quickstart](/quickstart)
- [QBCore resource sources](/docs/resources)
