VAC Ban Checker: How Steam Lookups Work
Direct answer: A VAC ban checker reads the public ban data Steam exposes for one account and shows it in one place: whether a VAC ban exists, how many VAC bans and Game bans are recorded, and how many days ago the last ban was recorded. Paste a SteamID64, profile URL or custom URL into the SteamReport.net lookup and you get those fields without adding the player as a friend. It does not show Trust Factor, and it cannot tell you what happened in a specific match.
What does a VAC ban checker read from Steam?
A checker is a front end for Steam’s public ban data. The usual source is the Steam Web API method ISteamUser/GetPlayerBans, which returns one ban record per SteamID64. Calling it requires a Steam Web API key. The fields most checkers display map to these values:
- VACBanned: true or false. True means the account has at least one VAC ban on record.
- NumberOfVACBans: the total count of VAC bans on the account. This is a count of ban records, not a count of matches.
- NumberOfGameBans: the total count of Game bans. These come from game-specific enforcement and are separate from VAC.
- DaysSinceLastBan: the number of days since the most recent ban record. Check the value against the ban counts before reading it as a date.
- CommunityBanned: true or false for a community restriction, which affects community features rather than matchmaking.
- EconomyBan: the trade and market restriction status, usually reported as none or as a restricted value.
Those six fields are the whole public ban picture a lookup can read. Anything beyond them, such as a Trust Factor number, is not part of that response.
How do I look up a player by SteamID64, profile URL or vanity URL?
The API works on numeric IDs, so a checker first converts whatever you paste into a SteamID64. A 17-digit number that starts with 7656119 is the standard format for an individual account. A full steamcommunity.com/profiles/ URL already contains that number. A vanity URL such as steamcommunity.com/id/name has to be resolved to an ID first, which is why some lookups take a moment longer.
Older Steam2 (STEAM_0:x:y) and Steam3 ([U:1:z]) forms can be converted into the same 64-bit ID. The SteamID formats guide covers each one and where to find them in the client.
How do I read “days since last ban”?
The value is a whole number of days counted from the date the most recent ban was recorded. A value of 0 means a ban was recorded on the day of the lookup. A large number means the most recent ban is old, but it does not mean the player has stopped cheating, and it does not mean the account is clean. Read it together with the VAC and Game ban counts. An account with a single ban from three years ago and an account with five bans in the last month look very different, even though both are flagged.
Why does the ban date differ from when the cheating happened?
The field records when enforcement was applied, not when the offence took place. Valve does not publish a per-player timeline of detections, so a checker cannot tell you which matches were involved. Detection and ban can be separated by days or weeks. That gap is the main limitation of any “days since last ban” reading. Use the number to place the ban in time, not to date the behaviour you saw in a match.
What can a VAC ban checker not show?
A ban checker answers one narrow question: what ban records does Steam expose for this ID? These things are outside its scope:
- Trust Factor: a hidden matchmaking signal. Valve does not publish it through the public API, so no checker can show a reliable number for it. See Trust Factor vs VAC vs Game Ban.
- Detections that did not lead to a ban: the public ban fields only record bans. Valve does not publish a per-account list of detections or actions that were not turned into a ban.
- Private account details: a checker sees the ban fields, not the private game library, match history or friends list unless the profile is public.
- Match behaviour: a ban flag says that enforcement happened. It does not say which round, which weapon or which map was involved.
Does a clean result mean the player is not cheating?
No. Zero bans means no ban records are visible today. Two common reasons it can be misleading are the delay between detection and ban, and the fact that a player may have been cheating in a way that has not yet produced a ban. This is why a lookup should be one input among several. If you have a specific concern, the step-by-step VAC check guide explains how to read the result, and the Game ban vs VAC ban guide explains why the two flags are not interchangeable.
How do I use the SteamReport.net lookup on the homepage?
The homepage lookup runs the same kind of check described above. The steps are short:
- Copy the player’s profile URL, SteamID64 or custom URL from their Steam profile, the in-game scoreboard, or a match lobby.
- Paste it into the lookup on SteamReport.net and run the check.
- Read the VAC and Game ban counts separately, then the days since the last ban.
- Open the profile itself to confirm the same flags are shown there, and note anything you cannot see.
- If you need performance data, open the stats dashboard, and keep in mind that stats are not ban evidence.
Key Takeaways
- A VAC ban checker reads public ban fields from Steam, such as VACBanned, NumberOfVACBans, NumberOfGameBans and DaysSinceLastBan.
- Paste a SteamID64, profile URL or vanity URL; vanity URLs are resolved to an ID first.
- Days since last ban counts from the ban record, not from the date of the cheating.
- Trust Factor is hidden and is not shown by a ban checker.
- A clean result is a snapshot of recorded bans, not proof of clean play.
Read Next in This Cluster
FAQ
What does a VAC ban checker show?
It shows the public ban fields Steam exposes for an account: whether a VAC ban exists, the number of VAC bans, the number of Game bans, days since the last ban, and the community and trade restriction status.
Does a VAC ban checker show Trust Factor?
No. Trust Factor is a hidden matchmaking signal. Valve does not publish it through the public Steam Web API, so no ban checker can display it as a number.
What does days since last ban mean?
It is the number of days since the most recent ban was recorded on the account. It counts from the ban record, not from the date the cheating happened.
Can I check a player with a vanity URL?
Yes. A vanity URL such as steamcommunity.com/id/name is resolved to the underlying SteamID64 first, then the ban fields are read for that ID.
Does zero bans mean a player is clean?
Not necessarily. A zero count only reflects bans recorded so far. Detection and ban can be separated by days or weeks, and a checker cannot show behaviour that was never banned.
Ready to check an account? Run a lookup on the SteamReport.net homepage.