Skip to content
Search 100+ games/
CRAZY 8 Ball Codes Fruit Battlegrounds Codes Ninja Time Codes

How We Verify Codes

by Moh Updated

A code list is only useful if you can trust it. This page explains exactly how a code gets onto CodesRush, how we keep it current, and what happens when it stops working.

The two-source rule

A code is listed as working on CodesRush only after at least two independent sources list it as working. “Independent” is the important word: two websites that copied the same list count as one source, not two. A code that appears in a single place, however convincing it looks, stays off the working list until a second source backs it up.

This rule sometimes makes us a little slower than sites that post anything they see. We think the trade is worth it. A fake or mistyped code wastes your time and makes you doubt every other code on the page.

The sources we check

  1. The game’s official channels, where they exist: the developer’s Discord server (usually an announcements or codes channel), the game’s official X account, its official Trello board or wiki, and the description or update notes on the game’s Roblox page. This is where codes are announced, so these channels carry the most weight.
  2. Established code sites and creators with a track record of accurate coverage. We use them to cross-check and to catch codes quickly, but we never copy their lists, and one of them alone is never enough.

Many games do not announce codes in a single obvious place, so we record which sources confirmed each code. When sources disagree, for example one site lists a code as expired while others still list it as working, we look for the developer’s own statement or an announced end date before deciding. If we cannot resolve the conflict, the code does not go on the working list.

From tip to published code

  1. A new code reaches us from our own monitoring, from a reader, or from a source we follow.
  2. We look for independent confirmation and note the exact spelling, because many codes are case-sensitive.
  3. We record the reward as the sources describe it and the date the code first appeared, so its age can be shown honestly.
  4. Once two independent sources agree, the code is published at the top of the game’s page with a one-tap copy button.

Daily rechecks

Codes expire, often without warning, so publishing a code is the start of the job rather than the end. Every active code is rechecked at least once a day against its sources. Each codes page shows when its list was last checked, in US Eastern Time, both under the title and below the list. If the last check is more than a day old, that label changes color, so you can tell at a glance that a check is overdue.

Expired codes

A code is marked expired when the developer says it has ended, when it is removed from the official list, or when our recheck finds that it no longer meets the two-source rule. It then moves from the Active list to the Expired tab on the same page. We keep expired codes visible instead of deleting them, so that if you find a code somewhere else you can see in seconds that it is already dead.

Expired codes never appear in the Active list, are never included in the count of working codes, and are never used in a page’s title or search description.

NEW badges

A code carries a NEW badge for 72 hours, counted from the moment it first appeared in a source we track. Rechecking the code, editing the page, or moving things around does not restart that clock. An old code will never be dressed up as new on CodesRush.

Checked and Updated dates

  • Checked is the last time we confirmed the code list. It moves forward with every recheck, even when nothing changed.
  • Updated, which is also the modification date search engines see, changes only when the codes themselves change (a code is added or expires) or when the guide on the page is meaningfully revised. A recheck that finds nothing new leaves it alone, and we never re-save a page just to make it look fresh.

What we cannot guarantee

Developers can end a code at any moment, including between two of our checks, and a reward can depend on your level, server, or account. The verification process makes mistakes rare, not impossible. Before assuming a code is dead, read the “Why isn’t my code working?” answer on the game’s page: many codes are case-sensitive, require a minimum level or a group membership, or only work on public servers.

When you report a code

Every report of a dead code triggers a fresh check of that code, and every tip about a new code goes through the same two-source rule as everything else. If a report shows we were wrong, the page is fixed as soon as the problem is confirmed. How we handle corrections across the whole site is described in our Editorial policy, and the details to include in a report are on our Contact page.

Copied