Great Britain · evidence ledger · 2026-08-20

Check the licence. Match the domain. Keep the receipts.

A British casino fact-check desk for operator identity, withdrawals, payment friction and complaint routes—without direct casino links.

How the catalogue resists paid-ranking pressure

AI-assisted evidence collection helps organise candidate checks, while rule-based scoring keeps paid popularity out of the verdict. Sources, dates, limits and the correction channel stay visible. Automation can miss context, so no score is treated as infallible.

Front-page docket

Latest reviewed files

Latest publication:

888 Casino logo888 Casino888casino.comGcurrent matchbet365 logobet365bet365.comGcurrent matchWilliam Hill logoWilliam Hillwww.williamhill.comGcurrent matchLadbrokes logoLadbrokesladbrokes.comGcurrent matchPaddy Power logoPaddy Powerwww.paddypower.comGcurrent matchBetfair logoBetfairbetfair.comGcurrent matchCoral logoCoralcoral.co.ukGcurrent matchSky Vegas logoSky Vegaswww.skyvegas.comGcurrent matchBetfred logoBetfredbetfred.comGcurrent matchCasumo logoCasumocasumo.comGcurrent matchGala Casino logoGala Casinogalacasino.comGcurrent matchPartyCasino logoPartyCasinopartycasino.comGcurrent match
01

Match a licence

Search the public register by exact domain, then match the named operator.

02

Audit a payment

Record method, timestamps, verification requests and withdrawal status.

03

Build a complaint file

Use the operator process, preserve evidence and identify the correct ADR route.

Catalogue checkpoint: start with a current domain match, then compare the evidence limits.

See the checked route