FiveM vs. RedM Server Resolving — What's the Difference?

Almost nothing changes. RedM runs on the same Cfx.re infrastructure as FiveM — the same join codes, the same matchmaking and the same endpoint resolution — so resolving a RedM server's IP, ASN and hosting details works exactly the same way as it does for FiveM.

RedM is Cfx.re's multiplayer platform for Red Dead Redemption 2, built by the same team behind FiveM and running on the same underlying framework. Where FiveM adds multiplayer and custom scripting to GTA V, RedM does the equivalent for RDR2 — and it reuses essentially all of Cfx.re's server infrastructure to do it, rather than standing up a parallel system.

A RedM server is registered with Cfx.re and assigned a join code the same way a FiveM server is — a short code like b578o4, shareable as a bare code, a cfx.re/join/ link or a fivem://connect/-style deep link. Resolving that code works through the same matchmaking lookup: Cfx.re returns the server's current connect endpoint, that endpoint resolves to an IP address over DNS, and the IP can be enriched with ASN, ISP and hosting provider data exactly as it can for a FiveM server.

That means a resolver doesn't need to know or care which game a join code belongs to in order to resolve it. The lookup path — code to endpoint to IP to hosting data — is identical, because it's Cfx.re's infrastructure doing the work in both cases, not something game-specific.

The differences show up in the data returned about the server itself, not in how it's resolved. A RedM server's resource list reflects RedM-specific frameworks and gamemode conventions rather than FiveM ones — different naming patterns for the roleplay frameworks and core resources in common use, and different default game metadata (build, game name) reported alongside the player list. None of that changes the resolution mechanics; it only changes what you see once the server has been resolved.

Player counts and tags work the same way in both games too, since they come from the same Cfx.re server-browser metadata rather than anything game-specific. The practical difference you notice as an outside observer is mostly cosmetic: RedM communities tend to use Western-themed naming for their roleplay frameworks and resources, where FiveM communities lean on modern-day naming — but structurally, both are just resources listed against a server record.

If you're building or using a tool that resolves join codes — whether that's checking uptime, pulling IP and hosting data, or monitoring player counts — the same logic handles RedM and FiveM servers without special-casing either one. CFXR resolves both through the same input box, and the API exposes the same fields regardless of which game a given join code belongs to.