Restricted Countries Casino Lists: Where They Hide

Every argument about a restricted countries casino list starts one step too late. Before you can read a list of codes you have to find it, and our records show that finding it is the hard part: we hold the exact address for 39 refusal lists, and exactly one of those addresses names the subject in its path. The other 38 sit inside a general document you have to search — a terms page in 33 cases, a help centre in three, an anti-money-laundering policy in one, and a bare homepage in one. This page is about the locating, which is the step no comparison table shows.

One address in thirty-nine says what it contains

Thirty-nine records in our library carry a recorded address for the page a refusal list was read from. Sportsbet.io’s is the only one that names the subject in the path: a help-centre page at the address ending /restricted-jurisdictions, holding 17 codes. Every other list in the file was extracted from a document whose title is about something else entirely.

That single fact governs how the work has to be done. A reader cannot navigate to a restricted countries casino list the way they navigate to a bonus page, because on 38 of 39 brands there is no such page. There is a terms document, and somewhere inside it there is a table or a paragraph of two-letter codes. Any method that depends on the restricted-country list being linked from a menu will find one brand in thirty-nine.

It is worth pausing on why that is the norm rather than an oversight. A refusal list is not a selling point, so there is no commercial reason to give it a page of its own, and there is a drafting reason to keep it inside the contract where it belongs. The consequence is simply that a reader has to treat the search as a document-retrieval task. Nothing about that is sinister, and we are not reading it as evasion; it is what a contractual schedule looks like.

All 39 addresses were read on 26.08.2026, and the counts below refer to that reading. Sixty-one records carry no address at all, and 62 carry no codes — the one-record difference between those two figures is the subject of a later section, and it is the most precise kind of empty cell in our file.

Thirty-three lists inside a terms document

The ordinary case, by a wide margin, is a restricted-country list buried in the terms and conditions. Thirty-three of the 39 addresses point at a terms page, under a variety of spellings: /terms, /terms-and-conditions, /tos, /terms-of-service, /terms-of-use, /policy/terms-of-use, /info/terms, /general-terms-and-conditions, /legal/terms-of-service und /docs/terms-and-conditions.

The named brands in that group, with their code counts: 7Bit Casino 216, Bets.io 42, BitStarz 74, Bitdreams 216, Bitsler 1, Cloudbet 2, CryptoLeo 74, Metaspins 58, Mirax 220, Nine Casino 74, Rainbet 11, Rakebit 13, Rocketpot 34, Shuffle 15, Slotum 216, Wild Fortune 47, Wild.io 45, Winz.io 92, Bitkingz 218, Windice 9, DuckDice 16, Wolf.bet 48, Crashino 18, JacksClub 10, Instant Casino 48, Playbet.io 30, BetPlays 15, LeeBet 8, CoinCasino 36, Oshi Casino 224, PlayAmo 217, Coins.Game 1 and Punt Casino 0.

Ten of those addresses are worth flagging for a different reason: the path includes a language or country segment. Mirax and PlayAmo were read from /en-AU/, Oshi Casino and Slotum from /en-CA/, Bitkingz and Windice from /de/, Playbet.io from /pt-BR/, Instant Casino from /no/, and Bets.io and Bitsler and BetPlays from /en/. We record the address we actually read, and we did not compare one language version against another, so for those brands the list quoted is the list that path carried on the date given.

The spread of spellings in that group is itself a practical finding. A reader who bookmarks /terms as the place a restricted countries casino list lives will miss Bitsler at /tos, Rakebit at /policy/terms-of-use, Shuffle at /info/terms, JacksClub at /legal/terms-of-service, LeeBet at /docs/terms-and-conditions and Crashino at /general-terms-and-conditions. Six different conventions for the same document, inside one shelf of a hundred brands.

Three help centres, one policy page, one homepage

Six addresses sit outside the terms, and each one is a different lesson in where a restricted-country list can end up.

Three are inside a help centre. Bitcasino.io’s list of 1 code came from a path running /help-center/help-terms-and-conditions/…, and Empire.io’s list of 12 came from the structurally identical path on its own domain — the same layout, which is what two brands sharing a template look like. Sportsbet.io’s 17 codes came from the one address in the file that names the subject.

One is on an anti-money-laundering policy rather than the terms at all. Primedice’s four codes were read from /policies/aml. That is a different class of document with a different purpose, and a reader searching only the terms would not have found it. Stake’s single code came from /licenses, a licensing page, which is the second document class in the file to carry a refusal list.

One is the bare homepage. Coins.Game’s single code was read from the root of the domain, with no path at all. And one address is on a different domain from the brand itself: Nitrobetting’s six codes were read from mynitro.io while the operator record’s domain is nitrobetting.eu. A reader checking only the brand domain would have come away with an empty cell.

Those six are 15 per cent of the addresses we hold, which is a large enough share to break any method that only searches the terms. Put the other way round: if a search of the terms comes back empty, the correct conclusion is not that no restricted-country list exists. It is that four more document classes remain unchecked — a help centre, a licensing page, an anti-money-laundering policy and the homepage — plus any secondary domain the operator runs.

A restricted countries casino list that was read and found empty

Sixty-one records have no address and 62 have no codes, and the difference between those two numbers is one brand. Punt Casino’s terms page address is recorded in our file and its code count is zero.

That distinction is worth more than it looks. For 61 records, an empty country cell means we did not locate a document to read. For Punt Casino, it means we opened the document and the codes were not in it. Those are two different states of knowledge, and collapsing them is how a comparison table ends up implying that a brand refuses nobody. Our file does not say Punt Casino refuses nobody; it says the page we read did not carry a list.

The same brand’s record shows why that kind of precision matters elsewhere too: its terms require the registration name to match a government-issued identification and allow documents to be requested to verify the legal and beneficial ownership of a payment medium. A record can be detailed on one axis and blank on another, and the blank is not evidence about the operator’s conduct. It is evidence about how far we got.

For the other 61 records the wording has to be even more careful. Twenty-one of them could not be read at all, so there is no document, no address and no codes — a row with a name and a domain. The remaining 40 were readable in other respects, and no page carrying a restricted-country list was located on them. Between those two groups and Punt Casino there are three distinct kinds of blank in this one column, and a table with a single dash for all three is throwing away most of what we know.

Why we store the address and not just the count

A number on its own cannot be checked. This brand refuses 48 countries is a claim about a document somebody once opened, and without the address it is unfalsifiable: a reader who disagrees has nowhere to go, and a reader who agrees has learned nothing about where to look next. So our records carry the address beside the count for all 39 lists, and the reading date beside both.

That practice has a cost and it shows up immediately. Ten of the 39 addresses carry a language or country path segment, which means the restricted-country list we quote is the version that path served. We did not diff the language versions against each other, and we are not going to pretend the ten are global statements. Instant Casino is the sharpest case, read from a Norwegian path; Playbet.io from a Brazilian Portuguese one; Mirax and PlayAmo from Australian English; Oshi Casino and Slotum from Canadian English. Naming the path is what makes the limitation visible instead of invisible.

It has a second consequence for how a claim can be phrased. With an address, the honest form of a statement is: on this date, this page carried these codes. Without one, the only available form is a generalisation about the brand, which is both stronger and less supportable. Almost every restricted-country list you will see quoted elsewhere is quoted in the second form.

The same discipline is why we separate no address from address with nothing in it, which is the subject of the next section, and why we print 39 and 38 as two different numbers rather than rounding them together.

Counting from the right denominator

Four numbers govern everything on this page, and they are easy to mix up.

So a statement like a third of brands publish a restricted countries casino list is true against a denominator of 100 and misleading without it, because 21 of those 100 records could not be read in any respect. Against the 79 records where anything at all was readable, 38 lists is nearly half. Both figures are correct and they support different sentences, which is why we print the base every time.

The gap between 39 and 38 is the single record described above: an address that yielded no codes. The gap between 38 and 62 is made of records where no document carrying a list was located. Neither gap is evidence about whether any country is refused, and a restricted countries casino comparison that treats a blank cell as a permissive answer has inverted the meaning of the cell.

One more caution about the 38. The counts run from 1 code to 224, and a count is not a measure of diligence. Our own scoring sheet reflects that split: a brand earns points for publishing a restricted-country list at all, and separately and independently for the number of markets it refuses. The two components are deliberately not multiplied together.

Two document classes that answer differently

Because restricted-country lists sit in different document types, they are not all answering the same question, and that is the subtlest point on this page.

A refusal list in the terms is a contractual statement about who the operator will serve. A list on a licensing page — Stake’s case, at /licenses — sits next to the licence that permits the service, and its one entry reads as a jurisdiction the licence arrangement does not cover. A list in an anti-money-laundering policy — Primedice’s case, with four entries — sits next to customer due diligence language, and its entries read as a risk classification. Same format, three different documents, three different reasons a code might be on it.

Our library does not record which of those three reasons applies to any given code, and we are not going to assign one. What we record is the address, the count, and the date. Where the surrounding licence row sits for each brand is a separate matter, gathered under markets left outside a licence’s reach.

One further observation about document class. Stake’s list holds a single code and Primedice’s holds four, and they are two of the four shortest lists in the file. The other two short lists, Bitsler’s and Bitcasino.io’s and Coins.Game’s at one code each, come from a terms page, a help centre and a homepage respectively. So there is no tidy rule connecting document class to list length, and anyone hoping the address predicts the content will be disappointed.

How to locate one, in five steps

This is the procedure our own reading followed, and it is reproducible without an account.

1. Open the terms and search for a pair of capital letters. Thirty-three of 39 lists are in a terms document, and a two-letter code table is easy to spot once you stop reading and start scanning.
2. If the terms carry nothing, try the help centre. Three lists live there, and one of the three — Sportsbet.io’s — is on a page actually titled after restricted jurisdictions.
3. Then try the licensing page and the anti-money-laundering policy. Stake’s list is on /licenses and Primedice’s on /policies/aml. Both are documents most readers never open.
4. Check the homepage and any secondary domain. Coins.Game’s list is at the root with no path, and Nitrobetting’s is on a different domain from the one in its record.
5. Note the path segment you used. Ten of the 39 addresses carry a language or country segment, so record which version you read. Without that, the list cannot be re-checked.

Five steps, and at the end of them a reader has either an address and a count or a documented absence. Both outcomes are useful, and the second is only useful if it is written down as we looked here and found nothing rather than as a blank. Every restricted-country list in our file was produced by exactly that sequence, and so was every documented absence.

That is the whole argument for treating a restricted countries casino list as a locating problem before a reading problem. A code table can be misread; an address cannot be guessed. Per-market cuts of the same data sit under no KYC casinos listed for Canada und no KYC casinos listed for Australia, and the register-side reading of the same hundred domains is at an online casino without KYC, checked in the register. Our ranking of the best no KYC casinos ranked on published documents pays a brand for publishing a list at all, precisely because the alternative — rewarding silence — is worse.