How to Find a FiveM Server IP from a cfx.re Link

Every FiveM server has a join link that looks like https://cfx.re/join/abc123. That short code is not the server's address — it is an identifier that Cfx.re resolves on your behalf. This article explains what is behind it and how to look up the details yourself.

What a cfx.re join code actually is

When a server registers with the Cfx.re platform, it receives a short alphanumeric code. The code is a pointer in Cfx.re's directory, not a hostname. When you click a join link, the FiveM client asks Cfx.re what that code maps to and connects to whatever address comes back.

This indirection is deliberate. It lets a server change its IP, move host, or sit behind a proxy without every player needing a new link.

What you can find out from a join code

The Cfx.re directory exposes a server's public data, which is more than most people expect:

• Server name and description, including the colour-coded name shown in the browser
• Current and maximum players, often with the player list
• Connection endpoints — usually ip:port, sometimes a hostname
• Resources — every script and framework the server is running
• Server variables — locale, tags, the framework in use, banner URLs

The resource list is the interesting part if you are researching. It tells you whether a server runs QBCore, ESX, QBox or something custom, and which public scripts it has loaded.

You can look all of this up with our CFX Finder — paste the link or just the code.

Why some servers do not show a real IP

If you resolve a code and get something like https://xxxx.cdn-playflare.net/ instead of an ip:port pair, that server is using Cfx.re's enhanced hosting / proxy routing. Traffic is routed through Cfx.re's infrastructure and the origin address is never published.

This is the same idea as putting a website behind a CDN: the published endpoint is the proxy, not the machine. In that case there is no "real IP" to find in the public data, and any tool claiming to reveal one is guessing.

Some servers also publish a domain with a real port, like play.example.com:30120. That resolves normally through DNS.

Doing it yourself

The directory is a public HTTP API. A join code resolves through a single request, and the response is JSON containing the fields above. Any tool that offers this — including ours — is reading that same public endpoint.

Two things worth knowing:

• The API host has changed over time. Older guides and tools point at servers-frontend.fivem.net, which no longer resolves codes. Tools that were not updated return "not found" for every code, including valid ones.
• Only running servers appear. A server that is offline is not in the directory, so a valid code can legitimately return nothing.

What this does not let you do

Being direct about the limits, because these questions come up constantly:

• It does not let you join a server you were banned from. The ban lives on the server, not in the link.
• It does not reveal anything private. Everything here is data the server chooses to publish to the server browser.
• It does not give you a way to attack a server. If you are looking up an address to send traffic at it, that is illegal in most jurisdictions and we are not going to help with it.

The legitimate uses are ordinary: checking whether a server is online before telling your players, seeing which framework a server runs before joining a development team, or confirming your own server is publishing the right data.

Check your own server

If you run a server, resolving your own code is a quick sanity check: it shows exactly what players see in the browser — name, player count, tags and resources. If something looks wrong there, it is wrong in the server list too.

Look up a cfx.re code — no account needed.