Fake and cloned gaming domains
Check domain spelling, operator consistency, registration records and impersonation signals before trusting a gaming website.
Read resource →Gaming safety and verification
Practical checks built around evidence, not fear.
Each resource shows the issue, a real-world evidence pattern, practical verification steps, what a signal cannot prove, limitations, sources and a dated change history.
Published
Last checked
Last updated
Scope11 safety resources
Editorial reviewCompleted
Resource library
Identity, claims, evidence and player protection.
These resources do not certify a named platform. They provide a repeatable process that can be applied before a platform claim is accepted.
How to use this library: start with the resource matching the problem, follow its verification process, record the evidence and apply a status only to the specific fact checked. These resources are educational and do not replace technical, legal, financial or medical professionals.
Use facts narrowlyA source-backed general rule does not verify a named platform.
Preserve uncertaintyMissing, conflicting and outdated information is labelled rather than guessed.
Protect personal dataOriginal evidence remains private; public copies remove unnecessary identifiers.
Operator identity and company verification
A practical process for checking legal-entity claims, domain records, app publishers and conflicting business details.
Read resource →APK permissions and security risks
Review app source, permission requests, publisher identity and device protections before installing an Android package.
Read resource →Fake support, Telegram and WhatsApp impersonation
Recognise copied branding, urgent payment demands, account-takeover attempts and unofficial support contacts.
Read resource →Bonus, payout and withdrawal claim checking
Separate a promotional statement from verifiable terms, transaction evidence and repeatable outcomes.
Read resource →Payment-proof screenshot limitations
Understand what a screenshot can show, what it cannot prove and which additional records matter.
Read resource →Fake app reviews and manufactured testimonials
Evaluate review timing, repetition, incentives, reviewer history and unsupported success stories.
Read resource →Guaranteed winning strategy claims
Test certainty claims against probability, independence, evidence quality and consumer-protection standards.
Read resource →Colour-prediction and lottery-style loss risk
Understand repeated-round exposure, randomness, chasing losses and why short winning streaks do not remove risk.
Read resource →Responsible-play controls and spending limits
Set money and time boundaries, recognise warning signs and create a stop plan before play begins.
Read resource →Evidence preservation after a platform shutdown
Preserve URLs, messages, transaction records and original files in a form that remains useful later.
Read resource →No matching resource was found.
Four questions connect the library
Who is responsible?
Domain, company, app publisher, support and payment identities should connect through checkable records.
What is actually claimed?
Promotional wording is separated from material terms, transaction evidence and repeatable outcomes.
What can harm the user?
App access, impersonation, repeated financial exposure and loss of control require practical prevention steps.
What evidence survives?
Original URLs, files, messages, transaction records, limitations and dates make later review possible.
Resource publication threshold
A resource must explain a real user problem, provide a repeatable process, distinguish facts from claims, include limitations and link to authoritative material. Word count alone does not determine value. Repetition, unsupported certainty and generic warnings do not meet the threshold even when the text is long.
When a topic cannot yet support a distinct evidence-based resource, it remains unpublished rather than being padded with repeated content.