At a glance
Recent detections
What is firing
Findings beside the number of distinct players they came from. A rule that fires for most of your players is describing ordinary machines, whatever its severity says — that is the thing worth noticing before it refuses anybody.
Enabled rules that produced nothing
Not evidence of a clean server. A rule that never fires is usually a pattern in the wrong shape — opengl32 where opengl32.dll was meant — and nothing else reports it, because there is no error to report.
Game servers
Players
Search
A machine fingerprint, an address, a module hash or a signer. A bare 32-character GUID is looked up as one; anything else is taken as part of a module path, which is what a pasted DLL name is.
Detections
Every finding the rules produced, newest first. Severity 3 is the only one the master refuses a player on; everything below it is recorded for someone to look at.
Detection rules
Every verdict comes from a row here. The client reports and these judge, which is why a new rule takes effect on the next attestation rather than needing a module release.
Screenshots
The picture goes to the game server that asked for it. What the master keeps is the record: what each end reported, and whether the two hashes agree. A mismatch means the bytes changed between the client and the server.