cs2promocodesHome / Methodology
Methodology — How We Verify
A code appears here only after being entered on the platform and producing the advertised reward. One that fails a re-check is deleted the same day rather than labelled expired — which is why this list is short and stays short.
What has to be true before publication
Three things, and the third is the one that decides an offer's real value. The code has to be accepted; the reward has to be credited; and the condition attached to it has to be legible. Codes circulating on aggregators that cannot be reproduced do not appear here regardless of how widely they are repeated — and they are repeated widely, because a dead code still earns traffic for whoever publishes it and costs them nothing. Where a reward is granted conditionally, the condition is recorded alongside it. Where the condition is unreadable or changes between sessions, the entry is not published at all. That rule costs us listings, and it is deliberate: an entry a reader cannot verify is worth less than no entry, because it looks like verification that did not happen.
Why there are no ratings here
We do not publish Trustpilot scores we did not collect, RTP figures, withdrawal-time guarantees, fee estimates or registered-user counts. Those numbers are the standard furniture of this category and almost all of them are invented — precise-looking, uncited, and impossible to reproduce. Adding one to a page does not inform anyone; it borrows the appearance of rigour. What replaces them is coverage: how much of a page's intent a platform serves first-party from one login, and whether its terms are visible before registration. That is checkable by any reader, which is the entire point. Where a ranking is more subjective than that, we say so and give the criterion rather than converting the judgement into a decimal. There is also a self-check any reader can run on us: does this site publish numbers that work against the offers it links to? The odds tables do exactly that, and if they ever disappear, the answer has changed.
Re-checks, corrections and limits
Published offers are re-checked cyclically and the outcome is binary. An offer that fails disappears the same day. It does not get an expired tag, an archive row or a strikethrough, because a long table of dead codes costs the reader more time than it saves and manufactures an impression of abundance that is not real. The limits are worth stating rather than implying. Checking is periodic, not continuous, so between one check and the next an offer can stop working before we remove it — which is why every page carries the date it was last checked instead of a general assurance of accuracy. We do not measure prize distributions independently, because we have neither the access nor the sample size; where numbers come from Valve we cite Valve, and where they come from an operator we say so and point at their page. And we do not test many platforms in parallel, which is precisely why this site publishes criteria you can apply yourself rather than a ranking of things we have not examined. Report anything wrong via report a dead CS:GO promo code — corrections are made in the text itself and the date is updated.
What gets recorded for each entry
Every listing carries the same four fields, and nothing is published without all four. The reward is written in the units the operator uses, without conversion, because a converted figure is one more thing that can drift out of date silently. The location is where the field actually sits in the flow, since that is the detail that determines whether a valid code pays. The condition is recorded whenever the reward is granted conditionally. And the date is the last time the entry was checked, not the date it was first written — a distinction that matters, because a page that quietly reuses its publication date is telling you nothing.
| Field | Source | Why it is there |
|---|---|---|
| Reward | Operator's own wording | Conversions drift; the original does not |
| Where it is entered | Observed in the flow | Decides whether a valid code pays |
| Condition | Promotion terms | Determines the offer's real value |
| Last checked | The re-check itself | Not the publication date |
Frequently asked questions
How do you verify a promo code?
By entering it on the platform and confirming the advertised reward is credited, then recording the condition attached to it. Codes that cannot be reproduced are not published.
Why do you not give star ratings?
Because scores in this category are typically invented and cannot be reproduced. We rank on service coverage and on whether terms are visible before registration, both of which a reader can check.
What happens when an offer stops working?
It is deleted the same day it fails a check. We do not keep an archive of expired codes.
How do I report an error?
Through the contact page. Corrections are made directly in the text and the last-checked date is updated.
Sources
Last checked 2026-09-10 · CS2PromoCodes editorial · how we verify