The browser is only one boundary
A browser block is the quickest barrier to set up and the narrowest in reach. It decides what one browser, in one profile, will load. Knowing exactly where that decision stops makes it easier to pair the block with controls that reach further, rather than trusting it with more than it can carry.
What a browser block can reach
A browser block works because the browser is the program that fetches and draws web pages. An extension or setting can inspect each address before the page loads and replace it with a block page when the address matches a list. For someone who uses a single browser for nearly everything, that covers most ordinary web access to casino sites on that device.
The same strength explains the limit. The rule lives inside the browser and applies only to that browser, and only to the profile where it was installed. Native apps, other browsers and other devices never consult it.
Four browsers, four starting points
Chrome, Microsoft Edge, Firefox and Safari each treat blocking tools differently. None of them ships a dedicated gambling blocklist as a built-in setting, so the starting point is usually an extension or a device-level control.
| Browser | Source of blocking tools | Check before relying on it |
|---|---|---|
| Google Chrome | Extensions from the Chrome Web Store | Running in Incognito windows is a separate permission; each Chrome profile needs its own copy. |
| Microsoft Edge | Edge add-ons, Chrome Web Store extensions, and Microsoft Family Safety on supervised accounts | The InPrivate permission is set for each extension. |
| Mozilla Firefox | Add-ons from Mozilla's add-on site | Private windows need the add-on to be allowed to run there. |
| Apple Safari | Extensions from the App Store, and Screen Time web content limits | Private Browsing permission is set for each extension. |
Setting up a browser block
- Choose the extension from the browser's own store and read the permissions it asks for. A blocker needs to read page addresses; little else should be necessary.
- Switch on a gambling category if the extension offers one, and add any domain names you already know about.
- Allow the extension to run in private windows.
- If the extension offers a password or a delay on changes, set it and give the password to a trusted person rather than keeping it yourself.
- Repeat in every browser and every profile in regular use on the device.
- Open one address you added to confirm that the block page appears in place of the site.
Lists versus your own entries
Extensions that ship with maintained lists benefit from other people finding new casino domains, but they depend on the maintainer's pace and on you keeping the extension updated. Entries you type yourself are exact and permanent, and just as exact in what they miss: an address you did not know about is simply not there. Most people end up using both, then add a device-level control that updates from a wider source.
A blocker acts when a page loads, not when an advert or a message appears. The pause happens at the destination, which is why it matters that the destination is covered in every browser in use.
Where the boundary ends
- A second browser, such as Brave, Opera or Samsung Internet, is a separate boundary with its own rules.
- A second profile in the same browser carries its own extensions.
- Native apps and in-app browsers do not consult a browser's extension list.
- Another device, or another user account on the same computer, sits outside the rule.
- Anyone with the extension's password or access to the extensions page can change the rule, so a trusted person holding the password matters.
Every one of these gaps has an answer in a different layer, not in a stricter browser rule.
This is general information, not personal advice. If gambling is causing harm, free and confidential help is available from services such as GamCare and BeGambleAware in Great Britain.