Lock the object
Record exact domain, brand, legal entity, terms version and comparison date. Similar names or mirrors must not be merged without evidence.
A useful table does not award a score before defining the evidence. Freeze the exact domain and date, then compare identity, exit path, terms and controls using the same fields for every candidate.
Open the verified play routeThis page is a decision worksheet built around a specific search task. It separates observable records, first-party wording and unresolved claims so the conclusion can be checked again after a material change.
Record exact domain, brand, legal entity, terms version and comparison date. Similar names or mirrors must not be merged without evidence.
Apply the same identity, payment, withdrawal, KYC, support, complaints and control fields to each site. Mark unknown rather than converting absence into a positive score.
Distinguish first-party terms, official records, live account tests and user reports. State sample size and verification status beside every performance claim.
Give withdrawal clarity, account closure, limits and escalation at least as much attention as game count or promotion size.
Retest after entity, domain, terms, payment, platform or support changes and date the affected rows.
A blank evidence field should reduce confidence, not invite a marketing guess. Readers should be able to reproduce the route and see why a conclusion changed.
No. A score hides weights and uncertainty unless the underlying evidence remains visible.
Update the affected rows when material identity, terms, payment or control evidence changes.
They can suggest test questions, but an individual claim requires its own records and context.