Methodology
How Serverfind collects and evaluates server data
Discovery, direct queries, ranking, and moderation answer different questions. This page explains what Serverfind measures, what it cannot verify, and how those limits affect the directory.
1. Candidate discovery
A discovery source can advertise an address as a possible public game server. That is only a candidate signal: discovery by itself does not prove that the address is reachable, currently online, or reporting truthful information.
2. Direct server queries
Serverfind queries candidates through the protocol supported by each game. Successful responses can include a name, map, slot capacity, current player count, version, password state, and optional player details. Public listings require a successful direct response and the platform's current visibility checks.
3. Reported data and freshness
Names, player counts, maps, tags, and player lists are reported by the game server. Serverfind confirms that a response was received; it cannot independently prove every value inside that response. Timestamps show when the latest successful observation occurred, and older observations should be treated with more caution.
4. Ranking
The default leaderboard uses current and recent server observations rather than paid placement. Stable tie-breaking keeps pagination predictable. A high position reflects the available ranking inputs; it is not a quality, safety, or ownership endorsement.
5. Moderation signals
Automated checks look for protocol contradictions, implausible capacity, repeated occupancy patterns, configured deceptive names or tags, and other evidence associated with misleading listings. Depending on confidence, evidence may be retained for review or a server may be removed from public results. False positives remain possible, so moderation rules are deliberately reversible.
6. Location and classification
Country labels are approximate IP geolocation, not proof of physical location. Game modes are classified from constrained protocol fields, maps, rules, and tags; unknown or custom configurations can be classified incorrectly. Owners can use the claim process to provide stronger context without changing the underlying scan record.
Corrections and abuse reports
Incorrect, deceptive, unsafe, or impersonating listings can be reported to [email protected] with the server address and a short explanation. See the contact page for the appropriate route.