How to Find a FiveM Server's IP Address

Paste the server's join code or cfx.re link into CFXR's resolver and it resolves the underlying connect endpoint, looks up the IP address behind it, and shows the ASN, ISP and hosting provider alongside it — no game client required.

FiveM servers aren't addressed by IP in the way older game servers were. Every public server is registered with Cfx.re under a short join code (like b578o4), and that code is what gets shared in Discord invites, server browsers and cfx.re/join/ links. The join code is a layer of indirection: it points at a live connect endpoint on Cfx.re's matchmaking service, and that endpoint is what actually resolves to an IP address and port.

That indirection is deliberate — it lets a server owner move hosts, change IPs or sit behind a proxy without breaking every link that has ever been shared for their server. It also means the IP isn't something you can read off a join code by eye; it has to be resolved.

1. Get the server's join code or link. Any of these forms work: a bare code like b578o4, a full cfx.re/join/b578o4 URL, or a fivem://connect/b578o4 link from a Discord invite.

2. Paste it into the input on the CFXR homepage and submit. CFXR normalises whichever format you used down to the bare code automatically.

3. CFXR queries the public Cfx.re server API for that code, reads the endpoint it returns, and resolves that endpoint's hostname to an IPv4/IPv6 address over DNS.

4. The resolved IP is enriched with ASN, ISP/hosting provider name, region and country from IP geolocation data, and shown alongside the server's name, resources and current player count.

Server owners typically use this to confirm which host or datacenter a server actually runs on (useful when troubleshooting a supposed downtime report), to verify a server hasn't silently moved to different infrastructure, or to check whether a competing or copycat server is hosted by the same provider. Players occasionally use it to sanity-check that a server they're about to join is really operated by who it claims to be, based on hosting history.

For playing, the join code remains the better thing to share: it keeps working when the server moves, while an IP address goes stale the moment the owner changes host.

A CFX IP resolver can only return the endpoint a server publishes to Cfx.re. Many larger communities route players through a reverse proxy or a DDoS-protection network, and in that case the address you get — and the ASN and ISP next to it — belong to the protection provider rather than the machine the server runs on. That is expected and correct: CFXR shows what is public and does not try to uncover an origin address that the owner has chosen to hide. The DDoS-protection guide explains how to recognise these networks, and reading ASN and ISP data covers what the network fields mean.

A lookup fails when Cfx.re has no live record for the code: the server is offline, private, was shut down, or re-registered under a new code. Typos are the other common cause — codes are short, so one wrong character points at nothing. If a server you expected to find is missing, check it again in a few minutes before assuming it is gone; see how to check if a FiveM server is online.

If you need to check more than one server, the bulk resolver handles up to 25 join codes in one request and exports the results as JSON or CSV. For anything you need to automate, the same resolution is available as a plain HTTP call — see the API-based bulk monitoring guide.