Public-evidence checklist

How to Review an Online Casino Before Registration: A Public-Evidence Checklist

A structured way to separate what a casino website displays, what it claims, what primary sources confirm, and what remains unknown before you create an account.

An online casino can publish an impressive homepage without answering the questions that matter most. A long game list does not prove that every game is available to you. Payment logos do not prove that deposits or withdrawals work reliably. A licence badge does not prove that the licence is valid or covers the domain you are visiting.

A useful review should therefore begin with public evidence—not registration, deposits, private account areas or marketing promises.

This checklist follows Online Review Casino’s review methodology: record what is publicly visible, identify what the website claims, verify material claims through primary sources, and leave unresolved questions marked as unknown.

What can you check without registering?

A public-page review can examine:

  • The exact domain and final URL
  • Market, language and currency signals
  • Public game categories and provider labels
  • Operator and company information
  • Licence claims and reference numbers
  • Terms, privacy and responsible-gambling pages
  • Public promotion conditions
  • Payment-method claims
  • Contact and support routes
  • Browser security warnings

These checks can improve the quality of your decision. They cannot prove that a casino is safe, legal in your location, financially reliable or suitable for you.

Separate evidence into four categories

Combining every visible statement into a single list of “facts” creates false confidence. Use four labels instead.

Directly observed information

This is information visible on a normal public page, such as:

  • A navigation label
  • A country or language selector
  • A displayed currency
  • A provider logo
  • A public promotion card
  • A company name in the terms
  • A contact route published by the site

The reliable fact is that the information was displayed. Its accuracy may still require verification.

Site-published claims

These include statements about:

  • Security
  • Licensing
  • Payment speed
  • Customer-support availability
  • Game fairness
  • Market leadership
  • Years in operation

Record them as claims unless a suitable independent source confirms them.

Independently verifiable records

Material claims should be checked at their source. Examples include:

  • A regulator’s licence register
  • A government or regulator warning
  • An official company register
  • A provider’s own public information
  • Current browser or cybersecurity documentation

An independent record should match the legal entity, domain, licence status and permitted activity—not merely a similar brand name.

Unknowns

Some information cannot be verified from public pages. Common examples include:

  • Account acceptance
  • Available payment methods after login
  • Withdrawal processing
  • Support response quality
  • Game availability for a specific location
  • Internal account limits
  • Successful identity verification

“Unknown” is a valid research result. It is more useful than an unsupported score.

Step 1: Record the exact route you reviewed

Save the full URL, language, date and visible market state.

Do not record only the brand name. One brand may use multiple domains, redirects or regional routes. Those pages may show different currencies, terms, products or eligibility conditions.

Your notes should include:

  • Starting URL
  • Final URL after normal redirects
  • Page title
  • Visible language and currency
  • Country or regional selector
  • Date checked
  • Screenshots of relevant public sections

Do not use hidden APIs, private account areas, access-control bypasses or geographic workarounds. If the normal public route does not load, record that limitation.

Step 2: Identify the legal entity behind the website

Look in the footer, terms, privacy notice and licensing section for:

  • Legal company name
  • Registered address
  • Regulator name
  • Licence or account number
  • Contact information
  • Entity responsible for personal data

A brand name is not necessarily a legal entity. If different pages name different companies, record the conflict rather than choosing the most favourable version.

If no operating entity is identified, do not invent one from domain-registration details or third-party review sites.

Step 3: Verify licence claims at the named regulator

A badge, seal or licence number on a casino website is only a starting point.

Open the named regulator’s website and search for:

  1. The legal entity
  2. The trading name
  3. The exact domain
  4. The licence status
  5. The activities covered
  6. Any published regulatory action

The UK Gambling Commission business register supports searches by business name, trading name, domain or account number. The Malta Gaming Authority licence register provides separate licence and URL-checking routes.

These are examples of regulator-owned registers, not evidence that a particular casino is licensed by either authority.

If a claimed licence cannot be matched, use wording such as:

The website publishes a licensing claim, but ORC did not independently confirm the legal entity, domain and active status in the named regulator’s public register.

Do not convert an unverified claim into a statement that a casino is illegal. Record what remains unconfirmed and check the relevant jurisdiction.

Step 4: Treat market signals carefully

A local language, familiar currency or country-themed title may show marketing intent. It does not by itself prove:

  • Legal availability
  • Account acceptance
  • Local licensing
  • Local payment support
  • Promotion eligibility
  • Access from every part of that country

The ORC Malaysia guide therefore treats public market mapping as evidence of a visible route—not as a licensing, legality or acceptance guarantee.

Before registering, consult the competent authority for the jurisdiction where you are physically located. Do not use a working domain or currency selector as legal advice.

Step 5: Check product, payment and promotion claims

Games and providers

Public category pages can confirm that labels such as slots, live casino or sports appear before login. Provider names can also be recorded when the mapping is clear.

They do not prove that:

  • Every displayed provider has an active integration
  • Every game is available in your location
  • The catalogue remains the same after login
  • A logo represents a current commercial relationship

Payments

A payment logo or written payment-method list confirms only what the website publishes. It does not demonstrate:

  • Successful deposits
  • Successful withdrawals
  • Processing time
  • Fees
  • Limits
  • Account-level availability

Those points should remain unverified unless supported by appropriate evidence.

Promotions

A promotion cannot be evaluated from its headline alone. Look for public information about:

  • Eligibility
  • Minimum deposit
  • Wagering requirements
  • Game contribution
  • Maximum bonus or withdrawal
  • Expiry
  • Payment-method exclusions
  • Regional restrictions

If the detailed conditions are behind login or absent, state that the offer could not be fully assessed.

Step 6: Review privacy and account-security information

Before submitting personal information, read the privacy notice and check whether it identifies:

  • The organisation handling the data
  • Why information is collected
  • Who may receive it
  • International transfers, where relevant
  • Retention periods or criteria
  • User rights and contact routes

The UK Information Commissioner’s Office lists these among the transparency details required under the UK GDPR. Its privacy-information guidance is a useful evaluation framework, although the exact legal requirements depend on the jurisdiction. As of this 2026 publication, the ICO’s related detailed guidance says it is under review following changes made by the Data (Use and Access) Act and may change, so readers should recheck the current material before relying on it for a compliance decision.

Also check the browser’s connection warning. Google Chrome explains that HTTPS protects the connection between the browser and website, but still advises users to verify the site name before sharing sensitive information. A secure connection is not a general endorsement of the operator. See Chrome’s connection-security guidance.

A practical public-evidence worksheet

Question Useful public evidence What remains unproven
Who operates the site? Entity named in terms and privacy pages Ownership accuracy and current corporate status
Is a licence claimed? Regulator, entity and reference number Validity until matched in the regulator’s register
Which market is targeted? Language, currency and country route Legality and account acceptance
Which games are displayed? Public categories and provider labels Logged-in and regional availability
Which payments are advertised? Public payment page or help article Transaction success, limits, fees and speed
Is a promotion visible? Public offer and complete terms Eligibility until all conditions are confirmed
Is support listed? Public contact routes Availability and service quality
Is data use explained? Privacy notice and controller details Actual compliance and security performance

Worked example: recording an AB33 public page

At the time of review, AB33’s published platform overview displayed statements about market focus, currencies, product categories, payments, mobile access, languages, support and security.

That makes the page a useful primary source for what AB33 publishes about itself. It does not independently establish that every statement is accurate, current or available to every user.

ORC’s existing AB33 review therefore separates visible category and market evidence from unresolved questions about licensing, ownership, payment performance, account-level availability and payouts.

When should you stop the review?

Do not register or enter personal information when:

  • The browser shows a serious security or certificate warning
  • The final domain differs unexpectedly from the route you intended to visit
  • Operator or licence details conflict across pages
  • A regulator’s register does not match a material licensing claim
  • Important terms are missing or unreadable
  • A message pressures you to act immediately
  • Someone asks for a password or one-time verification code
  • You cannot determine which organisation will receive your personal data

None of these checks can guarantee safety. Their purpose is to prevent visible uncertainty from being presented as verified confidence.

Final takeaway

A good pre-registration review is not a search for enough positive signals to justify signing up. It is a structured record of:

  • What the public website shows
  • What the brand claims
  • What independent sources confirm
  • What remains unknown

If a material question cannot be answered, preserve the uncertainty. That is more valuable to readers than a confident verdict built on marketing copy.

Sources