y4lg95, or the whole cfx.re/join/y4lg95 link. The public list entry is the only public surface where a platform action appears, so this is the input that makes the check worth running at all.
FREE TOOL · SERVER
Cfx blacklist check for a FiveM server
Somebody says your FiveM server is banned and you want to know whether that is true. The honest starting point is that Cfx.re publishes no blacklist anybody can query — so this page checks what is genuinely observable, tells you exactly what each answer is evidence of, and sends you to the one place that can give you a definitive answer. A tool that returned a confident green tick here would cost you days.
Before you press it, what this is. Cfx.re does not publish a blacklist you can query. There is no endpoint, public or documented, that answers "is this IP blocked". Anything that claims to query one is guessing, and a wrong green tick here costs you days.
So this checks the things that can be established, and labels each one with what it proves. The useful part is real: the platform removes a blocked server from the public server list, and the list entry carries Cfx.re's own suspendedTill field. A join code that resolves, is in live contact with the list and carries no suspension is genuine evidence that nothing is blocking it right now.
HOW TO USE IT
Put the join code in, not the IP
Both work, but only one of them can be checked against anything the platform publishes.
51.83.12.9:30120 tells you the machine is up and the port is open, which is worth knowing and is not a blacklist check. The public list cannot be searched by address without downloading the whole thing — roughly nineteen megabytes — so we do not pretend to.
This is the step the tool cannot do for you, and it is the one that actually answers the question. Restart the server and read the first few hundred lines. A block is printed there in plain language, with the stated reason.
BEING STRAIGHT ABOUT IT
What this check does and does not prove
Written out here as well as on every result, because it is the part that matters.
What it can establish
- Your join code resolves on the public cfx.re server list. A server the platform has blocked is taken off that list, so an entry being there is real evidence against a block.
- The list backend is in live contact with your server, from its last-seen time and a current player count. That is the same infrastructure that would be refusing you.
- Whether Cfx.re publishes a suspension on the entry. The suspendedTill field is set by the platform, not by you, so a value in it is authoritative.
- Whether your server answers on the open internet at all, which separates "my server is down" from "my server is up and something else is wrong".
What it cannot
- Query the blacklist. There is no public, documented endpoint for it. The old runtime.fivem.net/blacklist.json answers 404 and has no replacement.
- Detect a connection-level block. It is applied per IP and enforced when a player connects; the server keeps running and keeps answering its status endpoints throughout.
- Tell an absent list entry apart from a block. A server that is off, one that never listed, a mistyped code and a blocked server all produce the same nothing.
- Say anything about a Cfx.re account action, or about your Tebex or forum standing. None of that appears in anything public.
QUESTIONS
About blocked and blacklisted FiveM servers
Is there a real Cfx.re blacklist API?
No, and we are not going to pretend otherwise. The file people remember, runtime.fivem.net/blacklist.json, now answers 404, and there is no documented replacement anywhere. Every forum thread about a blocked server ends at a support ticket rather than at an endpoint, and the IP ranges the platform itself uses are deliberately not published. So no tool on the internet can look your IP up on that list, including this one. What this page does instead is check the four things that are publicly observable and label each one honestly.
Then what is this check worth?
One finding in it is genuinely strong. The platform removes a blocked server from the public server list, and the list entry carries a suspendedTill field that Cfx.re fills in itself when it suspends an entry. If your join code resolves, the list backend is taking your heartbeat right now, and suspendedTill is empty, that is real evidence nothing is blocking you — it is the same infrastructure that would be refusing you. It is evidence rather than a certificate, and the page says so on every result.
My server is reachable by IP but nobody can join. Is that a block?
It might be, and that combination is the clearest symptom there is. A platform block is applied per IP and enforced when a player connects, so the machine keeps running, the port stays open and /info.json keeps answering while clients are turned away. No reachability test can see that. The two places that can are your own server console, which prints the block and the stated reason at startup, and Cfx.re support. Check the console first — it is instant and it is authoritative.
Why does my join code return nothing?
Before you assume a ban, there are three ordinary explanations and they are far more common. The server is simply off. The server never got listed, because sv_master could not reach the list from that host. Or the code is wrong — they are six or seven characters and easy to mistype. A missing entry looks identical in all four cases, including a block, which is exactly why this page refuses to call it one.
What are servers usually blocked for?
In the cases people post about publicly, almost always the hosting rather than the content: running a server from a provider the platform does not recognise as a real VPS or dedicated host, which is what the block notice itself says. Appeals go to Cfx.re support with the server IP, proof that you have root or administrator access to the machine, and the name of the hosting provider. Note that the block is per IP, so a dedicated machine with several addresses can have one cleared and the others still blocked.
MORE