License record
An official or regulator-published record that may show legal operator name, license status, domain, product category or actions. It does not prove universal safety or state approval.
Read license checksThis glossary gives short definitions of casino safety terms and routes you to the full owner page when action or evidence is involved.
This glossary is not a casino ranking, security audit, legal guide, or proof that any operator is safe. Use the owner pages when money, identity data, or account access are involved.
| Situation | Terms to understand | Full owner page |
|---|---|---|
| Checking an operator | License record, legal entity, domain match, regulator, market approval | Check casino license |
| Suspicious site behavior | Warning sign, copied seal, fake support, watchlist, evidence packet | Scam warning signs |
| Suspicious message or link | Phishing, fake domain, support impersonation, KYC upload trap | Phishing scams |
| Account access risk | 2FA, MFA, backup code, SIM swap, password reuse, recovery flow | 2FA and password security |
An official or regulator-published record that may show legal operator name, license status, domain, product category or actions. It does not prove universal safety or state approval.
Read license checksThe exact website domain should match or be supported by official records. Similar-looking domains can be phishing or mirror-site risk.
Read phishing risksA dated collection of URLs, screenshots, terms, transaction IDs, KYC messages, withdrawal status and support logs used before reporting or disputing.
Read reporting checklistConnection security that can help protect data in transit. It does not prove licensing, payout reliability or operator safety.
Read SSL/TLS limitsAn additional account-login check beyond a password. It reduces risk but does not remove phishing, recovery or device-compromise risk.
Read 2FA safety| If you are about to... | Use this owner page | Why |
|---|---|---|
| Deposit after seeing a badge or license claim | Check a Casino License | A definition cannot verify a legal entity or domain. |
| Upload documents | Data Protection | That page owns upload-route and KYC evidence. |
| Respond to support or report a problem | Report a Scam Concern | That page owns evidence packet and official-route selection. |
| Secure an account | 2FA and Password Security | Those pages own account-access controls and recovery boundaries. |
| Term pair | Why users confuse them | Safer distinction |
|---|---|---|
| HTTPS vs licensed operator | Both can look like trust signals. | HTTPS protects connection; license records address operator authorization. |
| Warning sign vs proof of fraud | Users may treat one bad sign as final proof. | Warning signs require evidence, timeline, and official-source checks. |
| Report route vs recovery promise | Users may expect reporting to return funds. | Reporting preserves evidence and supports escalation; it does not promise recovery. |
Verify legal entity, domain, license status, product category, and jurisdiction limits.
Understand records, market limits, and complaint routes.
Slow down before depositing and build evidence.
Read watchlist claims without treating them as legal findings.
Check terms evidence before claiming.
Protect account access, payment details, and KYC documents.
Understand what HTTPS can and cannot prove.
Reduce account-access risk and prepare recovery steps.
Use unique credentials and a breach-response workflow.
Check KYC, privacy, and upload-route boundaries.
Separate KYC, bonus, payment, and support issues.
Choose official routes and preserve records.