How to Check UKGC Licensed Casinos on the Register

What the UKGC register actually records

The register is not a directory of operators the regulator has vouched for. It is a record of who currently holds a licence, and separately, which domains are registered against that licence at a given moment. Being on the list is a statement about who holds a permission today and which web addresses sit under it — not a statement about how that business behaves, and not a ranking of trustworthiness.

That distinction matters because the register does not group UKGC licensed casinos by trading name. It groups them by licence, then lists every domain currently registered against that licence, which is why a name search and a domain search can return different results for what a player would call the same site.

A domain search also has to specify which file it is reading, since the register keeps two: one for licences, one for domains. The two do not share a status vocabulary, which is a fact worth stating before the statuses themselves are explained, so a reader does not assume the smaller list is the whole picture.

The three domain-file statuses, not two

A domain on the register carries one of three statuses, and treating the check as a binary licensed-or-not question is the single most common way a manual lookup goes wrong. Active, Inactive and White Label each describe a different relationship between a domain and a licence, and only one of the three is the status most people assume is the only one that exists.

Filtering a lookup for Active alone therefore drops two entire categories of domain that are still genuinely licensed. gentingcasino.com and ivycasino.com are examples of exactly this: they do not both surface under an Active-only filter, even though neither is unlicensed. Whichever of the other two statuses actually applies to a given domain, the point stands regardless of which one it is — a status search that stops at Active is an incomplete search, not a stricter one.

White Label status specifically covers a domain trading under a licence someone else holds rather than one it holds in its own name, a distinct brand running on a platform someone else is licensed to operate. Missing that status while reading a domain's entry can make a legitimately licensed White Label site look like it has no licence at all, when the licence is simply registered to a different name than the one on the page.

How to check a UKGC licensed casino's domain against the register

The fastest way to check whether a casino is licensed in the UK is to skip the trading name entirely and search the exact domain. A brand can sit across several near-identical domains, and a name search risks missing the one actually in front of a player, or returning a different licensee whose name happens to be similar.

How to check a Gambling Commission licence properly comes down to two lookups run in sequence rather than one search box answering everything. First, the domain file: does this exact domain appear, and under which of the three statuses. Second, where a domain does appear, the licence file behind it: which entity actually holds the permission the domain is trading under, since the domain file names the domain but the licence file names the licensee.

Running both lookups matters because a domain result on its own can be a set rather than a single record — the same domain can appear against more than one licence row, which a reader expecting one answer can misread as a contradiction rather than as the register doing exactly what it is designed to do.

Two files, two vocabularies, and where a lookup goes wrong

The domain file's three statuses are not the licence file's statuses. The licence file carries six values rather than three — Active, Lapsed, Pending, Revoked, Revoked - Non Payment of Fee, Surrendered — and two of them are easy to conflate: surrendered and revoked describe different endings to a licence, one voluntary and one imposed, and collapsing them into a single "no longer licensed" reading loses that distinction. Those six are read from the same snapshot the lookup above reads, so the list here cannot fall out of step with the data behind it.

None of this licenses a shortcut on the domain side either. Matching UKGC licensed casinos by a shared parent domain instead of the exact host on file is a mistake that turns a large hosting platform into a false positive, since unrelated sites frequently share a root domain they do not share a licence with. A manual check that walks up to a parent domain to save a step produces exactly that failure, well before any lookup tool goes near automating it.

What a reader who wants to check whether a casino is licensed in the UK is left with, then, is a dated fact rather than a settled question: a specific domain, read against a specific file, on a specific date, reported as one of three statuses. It is not a claim that the operator behind it has never done anything wrong, and it is not a claim that will still be true unread six months from now. No formal published crosswalk between the licence file's six values and the domain file's three appears to exist.

What one snapshot of the register contains

The snapshot behind the lookup on this page was read on 25 August 2026. It holds 2,045 distinct web addresses registered against 630 licence accounts, which resolve to 2,212 address-and-account pairs once duplicate www forms are collapsed into the bare host. Those three figures are not interchangeable, and quoting one where another belongs produces a number that sounds precise while describing something nobody asked about.

The pair count is the one that answers most questions, because a pair is what a lookup actually returns.

Of those 2,212 pairs, 1,040 carry the status Active. The remaining 1,172 divide into 795 marked Inactive and 377 marked White Label. Fewer than half the domain entries in the file are Active, which means a reader who treats Active as a synonym for licensed has discarded roughly 53 per cent of the register before asking a single question about any particular address. That is the practical case against filtering on Active alone, and it rests on counting rather than on judgement.

The proportion moves between readings. Accounts open and close, domains are registered against licences and released from them, and a snapshot taken on a different date divides differently. The split above therefore describes one reading of one file, which is the same limit that applies to every individual result the lookup returns.

When a domain returns more than one register row

Most addresses in the file appear once. In this snapshot 1,918 of them do, which is why a lookup usually looks like a single tidy answer and why the exceptions catch people out. The remaining 127 addresses, a little over six per cent, carry between two and thirteen entries each: 116 have two, three have three, four have four, and a short tail runs up through five, eight, eleven and thirteen.

A multi-row result is not a contradiction to be resolved. The domain file records addresses against licence accounts, so an address that has been registered by two different accounts produces two rows, both of them correct, describing two different arrangements that may have applied at different times or may apply simultaneously.

ivycasino.com is the clearest illustration in this snapshot. It returns two entries. One sits under account 23328, held by Betable Limited, with a domain status of White Label. The other sits under account 67098, held by Jupiter Gaming Limited, with a domain status of Inactive. Both accounts hold licences that are themselves recorded as Active. A reader looking for one answer would have to decide which of White Label and Inactive is the real one, and the honest response is that neither is: they are two entries about two accounts, and the file does not rank them.

The relationship runs the other way too, and more commonly. Those 2,212 pairs are spread across 630 accounts, so the average account in this snapshot has around three and a half addresses registered against it, and some hold considerably more. An operator running several brands, or the same brand across several country domains, produces exactly that pattern. It is worth knowing before a lookup, because finding an unfamiliar company name attached to a familiar casino address is ordinary rather than suspicious: the file names the account holder, which is often the platform or the licensing entity rather than the brand on the page.

Whose licence a domain status actually describes

The register records which licence account a web address was registered against. It does not record what the site at that address does, and the distinction matters more than it first appears.

play.google.com is on file in this snapshot. Under account 44448, held by Eaton Gate Gaming Limited, it carries a domain status of Active, and that account holds a Remote Casino licence recorded as Active. Printed as a single line, address then status then licence type, that reads as a statement that the Google Play store is a licensed casino. It is not one. It is a statement that a licensed operator registered that address against its account, and every part of the row belongs to the operator rather than to the address.

This is why the lookup on this page names the licensee at the top of each result and introduces every licence row as belonging to that named company. A layout that leads with the address invites the wrong reading, and no amount of surrounding explanation reliably undoes a heading that has already said the wrong thing.

The same address also demonstrates the licence file's wider vocabulary. Under account 57994, held by Circl. Gaming Limited, both licences on file are recorded as Surrendered, a value the domain file's three statuses have no way to express.

Matching the address exactly, and why near enough fails

The domain file is inconsistent about the www prefix. It carries bare hosts and www-prefixed hosts side by side, sometimes both forms of the same address, which is why the raw file in this snapshot yields 2,131 distinct strings that reduce to 2,045 actual addresses once the prefix is normalised away on both sides of the comparison. A check that normalises only the address a reader typed, and not the addresses in the file, misses entries while its hit rate still looks perfectly healthy.

Scheme and path have to go the same way. Someone checking a casino will paste whatever their browser shows them, which usually carries https at the front and frequently a path or a tracking query at the end, and none of that appears in the file. The lookup above strips all of it before comparing, for the same reason: a silent miss is worse than a visible error, because a reader reads it as an answer.

The one shortcut that must never be taken is walking a failed match up to the parent domain. If an exact address is not on file, the address is not on file. Treating a subdomain as covered by its root would mean matching anything hosted under a large shared platform, and this snapshot contains a live demonstration of why that breaks: play.google.com is on the register, and google.com is a different string entirely with its own separate answer.

Two straightforward results show what the ordinary case looks like. gentingcasino.com returns one entry, under account 39326 held by Skill On Net Limited, with a domain status of White Label and three licences all recorded as Active. williamhill.com returns one entry, under account 39225 held by WHG (International) Limited, with a domain status of Active and six licences also recorded as Active. The first of those two would vanish from an Active-only filter despite holding three licences in force, which is the whole argument of this page compressed into a single lookup.

What a register status does not settle

An address that does not appear in the domain file has not been found unlicensed. It has been found absent from one file on one date, which is a much narrower statement and frequently a much less interesting one. Addresses are added and removed, and a business can operate lawfully in ways that put no entry in this particular file.

A status also says nothing about conduct. Active records that an address is currently registered against a licence in force. It does not describe how the licensee has behaved, whether complaints have been made, or whether enforcement action has ever been taken, and none of that sits in the domain file to be read out. Questions of that kind belong to the regulator's own enforcement record, which a domain lookup does not reach.

What a check of this kind gives a reader is narrow and useful: on a stated date, this exact address either was or was not registered against a licence account, under one of three statuses, held by a company the file names. Treated as that, it settles something real. Treated as a verdict on a business, it says more than the data can carry. Anyone wanting more than that is asking a question the domain file was never designed to answer, and no amount of careful reading will get it out of a record that does not contain it.

How the snapshot is maintained without turning it into a live claim

The lookup identifies its source date as 25 August 2026 on every result. That date belongs to the downloaded register files, not to the day a visitor happens to open this page. Keeping the two separate matters: a browser can load an old snapshot today, but it cannot honestly describe that snapshot as today's register.

A later register reading should replace the domain and licence files together. Updating only one would leave the domain-to-account join pointing at a different edition of the licence data, which can create mismatched statuses even when every individual row is genuine. The counts on this page also belong to the same edition and have to move with it: addresses, account pairs, account totals and the Active, Inactive and White Label split are four measurements of one snapshot rather than evergreen facts.

Corrections follow the same rule. A mistaken normalisation step, duplicate count or account join is corrected against the retained source files and the page date stays attached to those files. A change observed in a newer register is not backdated into the older snapshot. It is a new reading, with a new date and new totals. This keeps a correction to the method separate from a change in the underlying register.

The dated register is still only the first stop for a question about a named operator. The domain file says which account recorded an address, while enforcement notices and licence conditions answer different questions. Combining them into one approval label would discard the limits of all three sources, so the lookup returns the rows and leaves the broader judgement out.

Normalisation is recorded as part of that method because it changes the counts. The raw file can carry both a bare host and its www-prefixed form. Collapsing those into one address prevents a duplicate from being presented as two casinos, while keeping every address-and-account pair preserves the fact that one normalised domain may sit on several rows.

The lookup removes schemes, paths and query strings from submitted addresses for the same reason. Those parts belong to a URL but do not appear in the domain field. It does not climb from a failed subdomain to a parent host, because that would turn shared platforms into false matches. Exactness is relaxed only for forms the source itself treats inconsistently, never to manufacture a hit.

A correction log can therefore distinguish three kinds of change: a new source edition, a fixed parsing or join rule, and revised explanatory copy. Only the first changes the date of the underlying register facts. The second may change calculated counts while retaining the source date, and the third changes how the limitation is explained without changing any result row.

Named examples are checked the same way as any submitted address. ivycasino.com returns two account relationships in this edition, so both are reported. gentingcasino.com demonstrates why an Active-only filter is incomplete. play.google.com demonstrates why a registered address must not be described as though the address itself holds a casino licence. Each example tests a different failure mode in the lookup rather than acting as a judgement about the company or platform named.

The counts provide another check on the implementation. Distinct raw host strings, normalised addresses and address-and-account pairs should not collapse to the same total, because they measure different things. If an update produces identical figures, the normalisation and join deserve inspection before the new snapshot is described. A plausible total is not enough when the relationship between totals is part of the method.

Look up a domain against the snapshot

Enter a web address to see whether the domain file carried it when this snapshot was taken, which account it was registered against, and what licences that account held. The result is a reading of one file on one date. It is not a verdict on the site, and it is not advice.