Four checks. One decision.
Every page you visit passes through four layers before ShieldBet decides to block or allow it. Most pages clear in milliseconds. Pages that look risky get a closer look. Here is exactly what happens.
Instant blocklist check.
Continuously updated lists are checked first, because if a site is clearly known there is no need to look further.
The block list covers known gambling operators, offshore and crypto brands, verified affiliates and tipsters, and paid-entry competition products. A match means an instant block. The page doesn't load.
The safe list covers verified safe services: search engines, banks, gov.uk, the NHS, major retailers, productivity tools, and recovery organisations. A match means an instant allow.
Why check these first?
Bet365 doesn't need analysis. It should be blocked before anything else runs. The same goes the other way: gov.uk should never be subject to uncertainty. Fixed lists are fast, reliable, and easy to audit.
One exception: known platforms like Reddit, Discord, Twitch, Telegram, and YouTube pass through to the next step even when they're on the safe list, because the same site can host both normal content and gambling-adjacent content depending on the page.
Smart path check.
The same website can be fine on one page and a problem on another. ShieldBet checks the full address, not just the domain name.
| Domain | Path | What it is | Verdict |
|---|---|---|---|
| reddit.com | / |
Homepage | Allow |
| reddit.com | /search/?q=casino |
Search results page | Allow |
| reddit.com | /r/sportsbook |
Subreddit on risky path | Block |
| reddit.com | /r/gambling |
Subreddit on risky path | Block |
| discord.com | /invite/casinochat |
Invite path with gambling hint | Block |
| youtube.com | /results?search_query=casino |
Search page | Allow |
Page analysis.
For any page that gets this far, four things run at once and contribute to a shared picture. None of them make the final call alone.
The address
Looks at the domain, the path, and any query parameters. Strong gambling signals in a URL (sportsbook, betslip, casino, jackpot, freebet) push toward a block. Safe sector signals (banking, NHS, gov.uk) push toward allow.
The page text
Scans visible text against lists of known gambling and recovery terms. The page title is weighted more heavily than the body, since it reflects what the page is actually about. Terms like "free spins" or "welcome bonus" count as strong signals.
The page layout
Looks at the structure of the page itself: bet-slip elements, dense call-to-action buttons with gambling language, odds-ranking tables, affiliate link patterns. Sometimes the shape of a page says more than the words on it.
On-device detection model
A lightweight detection model runs directly on your device, using the address, page title, and visible text. It returns a probability that the page is safe or should be blocked, along with a confidence score. It works offline and adds no noticeable delay.
The decision.
One component takes everything gathered in the previous steps and makes a single call. It applies a fixed set of rules, in order, and every decision keeps a full record of what drove it.
| What was found | Decision |
|---|---|
| Active gambling feature present (bet slip, spin button, deposit screen) | Block. Gambling mechanism. |
| Paid-entry chance mechanic present (raffle, instant win, prize draw) | Block. Paid entry. |
| Strong route to a gambling site, backed by page or detection evidence | Block. Route to gambling. |
| Detection model clearly says safe, overriding weaker route signals | Allow. Verified safe. |
| Route signals present but the site is finance, recovery, or editorial with strong safe indicators | Allow. Safe context. |
| Route signals without enough safe evidence to override | Block. Route to gambling. |
| Structured commercial gambling promotion | Block. Promotion. |
| Otherwise | Allow. Not enough to block. |
What happens after a block.
Detecting a gambling site is only half of it. The other half is making sure you can't simply turn protection off in the moment you most want to.
Partner alerts that get serious
A small number of attempts within a rolling hour sends a supportive message to your trusted partner. Persistent attempts send a stronger one. Each level has a gap built in, so your partner is informed without being flooded with messages.
A structured pause at the worst moment
At a persistent run of attempts in a rolling hour, the block page is replaced with something different: a short, guided conversation. No shame language, no lectures. Built to interrupt the loop, not punish you for being in it.
Tamper detection
ShieldBet watches for signs that protection is being removed or disabled: uninstall attempts, protection service removal, systems-down states, and protection-disabled events. These trigger an immediate notification to your partner, with a cooldown window before another one sends.
Recovery vault
When a tamper attempt fires, ShieldBet shows your pinned recovery item from your recovery vault: a photo, a message, a reason you saved. Something personal. Not a warning label.
Works without a connection
Blocking keeps working even if ShieldBet's servers go offline. Your subscription state, blocklists, and attempt counts are all stored on your device. A server issue can't open a window to gamble.
Alerts calibrated, not constant
Your partner only hears from ShieldBet when it actually matters. Repeated attempts after the serious threshold don't create a constant stream of extra alerts. The goal is for them to be informed, not overwhelmed.
The architecture is the product.
Every other tool tries to make blocking smarter. ShieldBet makes removal harder. That is the difference that holds when willpower doesn't.