Methodology

How we verify a casino.

Every operator is checked against the same 14 evidence criteria. Automated monitoring runs continuously; manual decisions require documented evidence.

Live audit pipeline
14
Audit criteria
5
Pipeline steps
90d
Re-audit cadence
0$
Affiliate revenue
Every verdict published. Every signal auditable. Never paid placement.
Methodology authority standard

The methodology is a decision standard, not editorial opinion.

SafeOnlineCasino separates measurable evidence, manual assessment, public disclosure and enforcement action. The same rules apply to casino operators, game providers, infrastructure partners and compliance partners.

Scoring is capped by evidence

A strong website cannot compensate for missing license proof, unverifiable provider routing or unresolved player-fund risk.

Critical failures bypass scoring

Fake SEAL use, fake games, false license claims and deliberate payment obstruction trigger rejection, suspension or revocation review.

Roles are assigned, not chosen

Operators, providers and infrastructure partners cannot self-select wording, SEAL class, status or validation scope.

Public files must remain current

Material changes to license posture, complaints, supplier evidence or risk state update the public file and validation status.

Decision control protocol

Methodology outputs are controlled records.

Every public decision is constrained by evidence admissibility, commercial independence, retention rules and current-status precedence.

Public enforcement ledger
Admissible evidence only

A claim enters the file only when the source, date, entity, domain and scope can be tied to the record under review.

Commercial firewall

Validation intake, audit fees, sponsorship contact or legal pressure cannot modify evidence posture or suppress an enforcement event.

Negative record retention

Warnings, revoked status, fake-SEAL findings and material complaint outcomes remain visible as part of the operating history.

No recommendation output

The methodology produces status, scope, risk posture and decision history — not gambling advice, rankings or affiliate recommendations.

Operating standard

Every public file must pass decision gates.

A brand is not verified because it looks legitimate. It is verified only when evidence survives the same gates for role, domain, license, supply chain and public risk.

Role gate

Operator, provider or infrastructure role must be assigned by evidence review, not self-selected.

Evidence gate

Public facts, private files and pending claims are separated before any status is issued.

Risk gate

Complaints, warnings, fake SEAL reports and supplier conflicts can block or revoke verification.

Role-specific validation standard

Different roles. Separate evidence thresholds.

An operator, provider, distributor, platform provider and compliance partner cannot share one generic trust claim. Each role has its own public file, validator URL, evidence scope and revocation triggers.

Operator

License posture, domain control, payments, complaints, player protection and supplier route evidence.

Game provider

Legal identity, certificate scope, genuine game delivery, RTP evidence and clone-risk posture.

Distribution partner

Aggregation route, provider coverage, operator route files and integration evidence.

Platform provider

PAM, wallet, account infrastructure, operational control scope and jurisdiction posture.

Compliance partner

KYC, AML, payment-risk controls, player-safety tooling and response workflow.

Evidence classes

We separate public facts from private evidence.

Players need transparency, but operators and providers also submit sensitive files. We label what is public, what is on file, and what remains pending.

Public evidence

Regulator records, domain checks, public warnings and visible policy pages.

Evidence on file

Certificates, contracts, KYC flows, payment samples and private correspondence.

Pending evidence

Claims that are declared but not yet confirmed through evidence review.

Authority standard

A SEAL is a live validation decision, not a marketing asset.

SafeOnlineCasino records must be added, approved, revoked and restored by evidence review. Participants do not choose their own role, wording or validation status.

Controlled issuance

Official records are created from evidence queues only.

No self-issued SEAL

Embed assets are issued after approval, never by public role selection.

Revocation triggers

License mismatch, fake-game evidence, payment abuse or unresolved risk can revoke status.

Public audit trail

Verification pages show status, record ID, role, timeline and validation scope.

Non-negotiable rejection rules

Some evidence failures do not enter scoring.

When a critical trust claim is false, we do not average it away with good design, fast payouts or brand reputation. The file is rejected, suspended or revoked.

Fake SEAL

Copied, altered or role-mismatched validation asset.

False license

Regulator, entity, domain or license number mismatch.

Fake games

Provider denial, clone evidence or unverifiable delivery route.

Player-fund obstruction

Repeated unpaid balances, deliberate delay or abusive verification pattern.

Self-selected role

Applicant chooses operator/provider/partner status without evidence review.

Commercial pressure

Threats, paid placement requests or attempts to remove public warnings.

The pipeline

Five steps. Public at every stage.

  1. 01

    Application

    Operator submits license, RNG certificates, KYC policy, ADR membership and payout history. Free. No commercial terms attached.

    Day 0 · Free
  2. 02

    Automated checks

    TLS scan, regulator records lookup, WHOIS history, DNS reputation, license expiry crawl and complaint feed ingestion. Runs continuously.

    Day 1–2 · 38 signals
  3. 03

    Manual review

    Evidence review of terms, KYC flow walkthrough, payout cadence sampling, ADR caseload, RNG lab cross-check and supplier authenticity.

    Day 3–8 · Editorial
  4. 04

    Public file decision

    Evidence posture, approved scope, evidence status and decision reason are published. Eligible records receive a live SEAL tied to the validation file.

    Day 10 · Public file
  5. 05

    Continuous monitoring

    Re-audit every 90 days. License, security, complaint and supplier signals are watched daily. Any material change updates the public file.

    Day 11 → forever

Public-file walkthrough

Check the public file before trusting a claim.

01

Paste the URL

Enter the casino domain, brand name or SOC record reference.

02

Read the live verdict

Status, evidence posture, license, open complaints — fetched from the audit file.

03

Decide with evidence

Read the current decision state, evidence posture and enforcement context before acting.

What we measure

Fourteen checks, one verdict.

Each criterion carries a fixed weight. Weights are public and never change without a published methodology update.

Licensing
Security
Fairness
Player protection
  • 01

    License authority

    Tier of regulator (MGA, UKGC, SGA, GBGA, GCB).

    15
    weight
  • 02

    License verification

    Cross-checked against regulator public records.

    10
    weight
  • 03

    TLS / SSL configuration

    Cipher suites, HSTS, certificate chain integrity.

    10
    weight
  • 04

    RNG certification

    eCOGRA, iTech Labs, GLI or equivalent recent audit.

    8
    weight
  • 05

    RTP transparency

    Per-game RTP published and matches lab certificates.

    8
    weight
  • 06

    Responsible gambling tools

    Deposit limits, reality checks, self-exclusion.

    8
    weight
  • 07

    Domain age & ownership

    WHOIS history, registrar, parent company filings.

    8
    weight
  • 08

    Self-exclusion participation

    GAMSTOP, ROFUS, SPELPAUS or equivalents.

    6
    weight
  • 09

    Complaint response

    Average resolution time and ADR provider.

    6
    weight
  • 10

    KYC / AML procedures

    Documented verification flow, AML reporting.

    5
    weight
  • 11

    Payment provider trust

    Tier-1 processors vs. unlicensed crypto rails.

    4
    weight
  • 12

    Withdrawal policy

    Limits, processing time, identity locks.

    4
    weight
  • 13

    Terms clarity

    Wagering math, max bet, time limits and dispute terms in plain language.

    4
    weight
  • 14

    Public reputation

    Forum signal, regulator actions, ADR cases — last 24 months.

    4
    weight
Evidence posture rule

Weighted posture, capped by evidence quality.

Each criterion is assessed 0–100, multiplied by its published weight, then normalized to 100. Manual evidence review may reduce the evidence posture when evidence is incomplete, contradictory or stale; it may not raise it without documented evidence.

evidence posture = Σ(criterion_value × criterion_weight) / 100
Evidence admissibility

Claims do not count until verified.

Accepted

Regulator records, lab certificates, domain records, payment proof, operator responses and reproducible public evidence.

Rejected

Affiliate copy, screenshots without source context, expired certificates, unverifiable claims and self-issued SEAL assets.

Stale

Evidence older than 12 months is downgraded unless the regulator/certificate remains publicly active.

Decision thresholds

Evidence posture from 0 to 100. Approval threshold at 75.

90–100
Excellent
75–89
Verified
50–74
Fair
0–49
Caution

A public validation file is issued only after the most recent evidence review reaches 75 or above and no critical-failure rule is active. A drop below 75 suspends or revokes the SEAL within 24 hours.

Revocation policy

Immediate revoke

Fake SEAL use, fake games, false license claim, revoked regulator status or deliberate player-fund obstruction.

Conditional suspend

Evidence posture below 75, missing proof after evidence request, unresolved high-risk complaint or supplier authenticity gap.

Watchlist escalation

Repeated weak signals, delayed response, clone/domain confusion or public evidence conflict.

Restore only with proof

Status can return only after new evidence is reviewed and the public timeline records the restoration.

Public utility

One decision record. Three accountability uses.

For players

Check the operator file before making a decision: regulator, evidence posture, warnings, complaints and validation status.

For operators

A live verification record tied to evidence, status changes and a role-specific validation URL.

For regulators

Independent secondary signal. Complaints triaged and forwarded with evidence already attached.

Authority controls

Why the decision record holds.

No affiliate model

Zero commission on deposits. No featured slots for sale.

Public audit files

Public evidence, evidence on file and pending evidence are separated in the dossier.

Continuous re-audit

Every 90 days, plus daily license + security signals.

Revocable SEAL

Drops below threshold and the validation status changes within 24h.

Ready to verify?

Open a public validation file that can stand scrutiny.

Applications are free. We never sell placement. The only way onto SafeOnlineCasino is to pass evidence review.