The crypto casino blacklist

An operator is listed when at least one of the canonical buckets above is documented against it during our deposit-test. A single failure inside a single bucket is enough; we do not require pattern-of-failure for licence or withdrawal-integrity buckets.

Operators may request a re-test after addressing the documented failure. Re-tests are not free of effort: we re-deposit, re-time withdrawals, and require a 90-day clean window before delisting. Delisting is at editorial discretion; we publish the delisting decision with reasoning when it happens.

• Day 0 — operator submits a remediation statement to [email protected] documenting which failure mode was resolved and how.
• Day 0–14 — editorial review of the statement; we re-deposit and re-time the failure mode under our normal protocol. If the remediation does not survive the first re-test the clock does not start.
• Day 0–90 clean window — measured from the date the first successful re-test completes, NOT from the original audit date. We monitor complaints, withdrawal-timing, and licence registry during the window; any regression resets the counter.
• Day 90+ — editorial decision published on this page with the delisting reason and the date the clean window closed. The original blacklist entry stays on the page as a strike-through with the delisting note attached — we do not silently delete blacklist history.

Many failing operators recycle brand names every few months — the cloned / reputation-laundered bucket exists exactly for that pattern. Names you don't recognise are usually the freshest skins of older blacklisted parents; we identify the parent in the failure-detail column when the link is documented.

To submit an operator for blacklist review, email [email protected] with the brand name, the URL, and the failure pattern you observed (ideally with timestamps and the withdrawal transaction IDs). Every submission is read by a real editor and triaged inside 48 hours.