# Our method: sources, the 12 checks, and what we do not do

> How operators enter the comparison, how each of the twelve checks is read and labelled, how often facts are re-read, and what the site does not do.

Source: https://bookiechecklist.com/how-we-check-bookmakers/
Updated: 2026-11-13

Operators enter this comparison only when the ACMA register of licensed interactive gambling providers lists them, matched by brand and domain on the day of work. Each is then read against the same twelve checks. Every result is labelled Found, Not found on the page checked, or Not confirmed, with a source address and a date.

## How an operator gets onto the site

The starting list is the register extract, not a ranking or a sales list. The extract of 6 November 2026 holds 214 records, 66 of them without a web address.

We then follow four rules:

1. The brand and the domain must sit in one register record on the day of work.
2. The licence holder is looked up in [ABN Lookup](https://abr.business.gov.au).
3. The domain must not be on ACMA's blocked list.
4. A profile is written only when at least 10 of the 12 checks could be read.

**Where this stands:** the register decides who is listed; nothing else does.

## The three labels

Each cell in the comparison has one of three results, and each carries a link and a date.

**Result labels · site method, criteria version 1.0 · checked 2026-11-13**

| Label | When we use it |
|---|---|
| Found | The item was read on the page checked (response 200), with the quote, address and date recorded. |
| Not found on the page checked | The page was read, but the item is not on it. This does not show the feature is absent. |
| Not confirmed on | The page or register could not be read (the status code is recorded), or the record is ambiguous. |

A cell without a source address is not allowed. If a page returns an access error, we do not work around it. The cell reads Not confirmed.

**Where this stands:** a gap in our reading is shown as a gap, never as a verdict.

## What we do not do

- We do not place bets, and we do not test payouts.
- We do not give points, stars or a best-overall pick.
- We do not publish reviews from players or promotional codes.
- We do not link to services that are not in the register.
- We are not a bookmaker and do not take bets.

Order on every comparison page is alphabetical. A count of found items is not a merit score.

**Where this stands:** the method describes what is published, not how good a service is.

## State of this edition

The register extract of 6 November 2026 is the baseline.

Operator pages and app stores are not yet read for this edition, so the operator-level checks read Not confirmed until each source is read and dated.

Details of each check are on [the twelve checks explained](https://bookiechecklist.com/the-12-checks-explained/). Refresh rules are on [how data is refreshed](https://bookiechecklist.com/how-we-source-and-update-data/).

Found an error? Use [Report an error](https://bookiechecklist.com/corrections/).

18+ only. Gamble responsibly. Get help: Gambling Help Online 1800 858 858.

## FAQ

**Which bookmakers can appear on this site?**

Only operators with a record in the ACMA register of licensed interactive gambling providers, matched by brand and domain on the day of work. No record, no profile.

**Does the site place bets to test a bookmaker?**

No. We do not place bets or test payouts. We read what operators and regulators publish and record the address and date of each page read.

**Is the count of checks a score?**

No. A line such as 9 found, 2 not found on the page checked, 1 not confirmed is a count. Operators are listed A to Z, and the count is never used to sort.

**What does Not found on the page checked mean?**

The page was read and the item was not on it. This does not show the feature is absent, only that we could not confirm it from that page.

**How do I report a mistake?**

Use the corrections page. A factual error is checked and corrected within 2 working days, and the change is recorded in the changelog.

