How CFXR Works
CFXR is a CFX resolver: it reads what a FiveM or RedM server already publishes about itself and presents it in one place. This page lists every source, every limit and everything that is stored.
The lookup, step by step
- Normalise the input. Whatever you paste —
b578o4,cfx.re/join/b578o4, afivem://connect/link or a servers.fivem.net URL — is reduced to one lowercase join code. Anything else is rejected before a request is made. - Ask Cfx.re. CFXR requests that code from Cfx.re's public server-list API, the same data the in-game server browser shows.
- Resolve the endpoint. The connect endpoint in that record is resolved over public DNS to an IPv4 or IPv6 address.
- Describe the network. The address is looked up in public IP-information services to get its ASN, ISP and country.
What CFXR resolves
- Server name, project name, owner name, game type, map, locale and tags
- Current and maximum player counts, and whether the server is online
- The published connect endpoint and the IP address it resolves to
- ASN, ISP and country of that IP address
- The resource list the server advertises
- For servers CFXR has seen before: player-count history, uptime and a change log
What CFXR does not resolve
- A server's hidden origin IP. If players are routed through a proxy or DDoS-protection provider, CFXR shows that provider's address — it makes no attempt to get around it.
- Anything not already public. CFXR never connects to the game server, never logs in anywhere and never reads data the server does not publish to Cfx.re.
- Private or offline servers. Without a live Cfx.re record there is nothing to resolve.
- The code inside resources. A resource name tells you nothing about whether the script is safe.
Freshness and caching
A successful lookup is cached for about 60 seconds and a "not found" result for about 30 seconds. Player counts are therefore near-live, not real-time. Servers that are tracked are sampled periodically to build the player-history charts.
What is stored about you
Lookups need no account. CFXR never stores a raw visitor IP address: rate limiting and abuse prevention use a keyed hash of it, and lookup logs are deleted after 90 days. Server records — public infrastructure data about the server, not about you — are kept because the directory and change history are the product. Full details, including retention periods for every table, are in the privacy policy and the cookie list.
Limitations
- Every field is self-reported by the server owner (name, tags, owner, resources) or derived from public registries (ASN, ISP). CFXR does not verify them.
- IP geolocation is approximate; a country is where the network is registered, not necessarily where the machine is.
- If Cfx.re's API is unavailable, CFXR cannot resolve anything until it returns.
- Lookups are rate-limited per client to keep the service fair and to avoid putting load on Cfx.re.
Who runs CFXR
CFXR is a free tool operated by Titan Software z.s., a registered association (z.s.) based in the Czech Republic that also builds FXScan and Titan AntiCheat. Security issues can be reported through responsible disclosure. For the bigger picture on keeping a server safe, read the FiveM server security guide.
Ready to try it? Resolve a CFX join code or read the supported input formats.