How to block betting sites on iPhone
Betting sites stop loading in every browser on the phone, and which layer you use decides how easily that comes off.
Updated October 2026
Why the sites are the harder half
An app is a single object with a single seal. A website is an address, and an address can be reached from Safari, from Chrome, from a browser living inside a messaging app, from a search result, from a link somebody sent you, and from a shortcut you saved to the home screen a year ago. A sportsbook's website works whether or not its app is on the phone.
So the question is not really how to block a betting site. It is which of the phone's layers answers the address, and which of them a browser can step around.
Apple's own website filter, which is real and small
iOS ships a website filter inside Screen Time, and it does what it says: a domain on the list is refused, and what the reader sees is Apple's own restricted site page rather than anybody else's block screen.
Two limits come with it. The first is coverage. A curated list is a list, a regional bookmaker it does not carry is open, and a new address is open until somebody adds it. The second is the one that matters more: the filter takes effect inside Safari and nowhere else. Chrome, Firefox, Edge, Brave and every browser embedded in another app are untouched by it.
There is also the question of who can lift it, and on your own phone the answer is you. The self built version of this is a Screen Time passcode that somebody else typed in, and Apple's own page on a forgotten Screen Time passcode explains that you can reset it with the Apple Account used to set it up. If the Apple Account is yours, so is the reset, and the friend never hears about it. Why blockers fail quotes that page directly.
A DNS or VPN profile you install yourself
The next step up is a filtering service you point the phone at. Some do it with a DNS profile, which changes where the phone sends its name lookups; some do it with a local VPN profile, which routes traffic through a filter on the device. Both are real mechanisms, both stop real pages, and both reach every browser rather than Safari alone. If breadth is what you are missing, this is the layer that supplies it.
Two holes come with the class, and neither is a fault of any particular service. A profile lives in Settings on a device you own, so removing it takes about as long as adding it did; a filter of this kind is exactly as strong as your willingness to leave the setting alone. And name based filtering cannot see an app that ships its own addresses, pins its own resolver inside itself, or reaches its servers through a shared host, so a native app may keep working while every browser is covered.
The same layer, with something holding it on
Fold’em's web shield is the DNS mechanism above. Every name this phone looks up goes to Fold’em's own encrypted resolver, and the resolver answers a known gambling domain with 0.0.0.0, the address for nowhere, so the page never loads. That reaches every browser on the phone, browsers inside other apps included, and it needs no tunnel.
The difference from the paragraph above it is not the blocking, because the blocking is the same idea. It is what happens when you decide to end it. Switching the setting off leaves the app seal standing and leaves your protection running, so it weakens one layer rather than ending the block, and the record of your protection is on the server where the phone cannot move it.
One thing is worth saying plainly rather than leaving you to discover it. Switching the DNS setting off lets the sites load again, and the Gambling sites layer then reads Needs attention.
Two site lists, and why they are never added together
Reading a product page you would think there is one number. There are two lists in Fold’em, one Fold’em keeps and one you keep, and adding them up would be arithmetic on things that are not the same kind.
The web filter answers for about 356,500 gambling addresses and reaches every browser on the phone. The second list is yours: any website you add by typing its address, and it stays blocked while protection holds. Which sites are on the block list keeps the two apart.
What still gets through, and what each one means
Four things let a site through, and they need different responses.
- The address is not on the list. A resolver answers for names it knows. A regional bookmaker, a new domain or a site that moved is a gap in coverage rather than a failure of the mechanism, and it is fixed by adding the address rather than by changing products.
- Something else is answering first. If a second VPN is running, it takes the answer before the shield does.
- The app is reaching its servers directly. Name filtering is blind to an app that carries its own addresses. This is why an app seal and an address shield are two layers rather than one, and why a product that only sells you one of them is selling you half.
- The shield is not on. The Gambling sites layer reads Needs attention, with the line The filter is off, so gambling sites are open, and Turn on web protection brings it back. A betting site still loads walks each of the four scenarios in order and says which are the block working at its edge.
Belt and braces is a legitimate answer
Nothing here argues for one layer. A broad address filter for reach, plus a sealed set of apps for the ones that matter, plus something holding both on, is a better arrangement than any single piece of it, and the reason is that they fail in different directions. The layer to be most careful about is the one you can undo alone, at the hour you will want to.
The pillar covers the app half of the same question, and the mechanism table sets the four classes side by side with what each one can and cannot reach.
The help center answers how the app behaves, screen by screen. If your question is not there, write to us. A person reads it and answers within two working days.