Setting things up is a task for a calm moment, and trying to do it mid-urge usually ends with you deciding it is all pointless. Go to the urge plan, get through the next ten minutes, and come back to this page afterwards. It will still be here.
And if things are darker than that — if you are thinking about harming yourself — please contact a crisis line now. In the US and Canada, call or text 988. In the UK and Ireland, call 116 123. Elsewhere, findahelpline.com. A blocked phone is not the problem worth solving tonight.
1. Turn on what your device already has
Five minutes, no account, nothing to buy. Pick the device you actually reach for, not the one you use for work. Be honest about which one that is; setting this up on the wrong device is the most common way people waste an evening.
iPhone or iPad
This is where iPhone is genuinely strong. Settings → Screen Time → Content & Privacy Restrictions → turn on → App Store, Media, Web, & Games → Web Content → Limit Adult Websites.
This one setting also covers pages opened inside other apps, which is the gap most setups miss. One caveat: on current iOS it no longer reliably removes Safari's Private Browsing, so it blocks well but do not count on it for a complete history; Only Approved Websites still applies inside private tabs. It also does not filter what native apps show in their own feeds, so pair it with an app age-rating limit (Apps: 16+ or lower on iOS 26) and Installing Apps: Don't Allow.
Android
Android has no built-in web filter for an adult's own account, so Step 2 is your step 1. One thing worth two minutes: in the Play Store, under your profile -> Settings -> Family -> Content restrictions, set a rating ceiling with a PIN the trusted person chooses. It stops installing apps above that rating; it does not touch browsers or links.
While you are in Settings, delete browsers you do not use. Every extra browser is another thing to configure later.
Mac or Windows
The built-in filters are weaker than people assume: on a Mac it only covers Safari, on Windows only Edge. Worth turning on if that is the browser you use, but do not stop there.
Step 2 matters more on a computer.
2. Add a filter that covers every app
Ten minutes. This is the step that does the most work, on every platform, because it applies to everything on the device rather than one browser — including pages opened inside other apps, and including when you are on mobile data rather than home Wi-Fi.
Or do it by hand. Do not spend tonight comparing services — use CleanBrowsing's Family Filter: free, no account, set up in a few minutes. Exactly what to enter:
| Device | Where | What to enter |
|---|---|---|
| Android | Settings -> Network & internet -> Private DNS -> Private DNS provider hostname. On Samsung: Connections -> More connection settings. | family-filter-dns.cleanbrowsing.org |
| iPhone / iPad | Settings -> Wi-Fi -> the i beside your network -> Configure DNS -> Manual | 185.228.168.168185.228.169.168 |
| Mac / Windows | Your connection's network settings, DNS servers | 185.228.168.168185.228.169.168 |
3. Put it behind a passcode you do not hold
Three minutes, and this is the step that decides whether any of the above survives next week. Everything you just did can be undone in under a minute by you, tonight, in a worse mood.
The ideal is that someone else sets the passcode and you never see it. If nobody is available tonight, do this instead: generate a long random passcode, write it on paper, set it, and put the paper somewhere inconvenient — a sealed envelope, a drawer at a relative's house. Then hand it over properly when you can. An awkward temporary version tonight beats a perfect version you never get around to.
Private DNS is an ordinary setting with no lock, so you can always switch it back. What makes it work anyway is that switching it off stops the log, and someone else is watching the log. Agree tonight that a gap in the record is something they will ask about. On Android, that agreement is the lock. A real technical lock does exist, but it is demanding and it is not tonight's job: Lock the DNS profile.
When you set a Screen Time passcode, iOS asks for an Apple Account for Screen Time Passcode Recovery. If you enter your own, you can reset the passcode whenever you like and none of this counts. Enter the trusted person's Apple Account instead.
Doing this alone tonight, with nobody to name yet? Enter your own account rather than skipping the prompt, and make fixing it the first thing you do once you have someone. Skipping does close the loophole, but it also removes the only supported way back in: a forgotten passcode with no recovery account means erasing the device and setting it up as new. Your own account tonight, changed later, is the safer trade.
4. Test it, in two minutes
Almost every failed setup was never tested. Do not skip this because you are tired; a setup you believe in but which does not work is worse than none, because you stop watching.
- Open something you know is blocked. Your provider's own test page confirms you are using their resolver; then open one domain from a category the provider documents as blocked, because a resolver-in-use test alone does not prove filtering. Do not go hunting for something to test with — you are testing the mechanism, not the category.
- Try it again in a different browser, and in a private window.
- Send yourself a link and open it from inside another app, so it opens in that app's own browser.
- Turn Wi-Fi off and try once on mobile data.
- Try to change the setting back. If you can, go back to step 3.
Then, this week: the part that makes it hold
The four steps above are worth doing alone. But every honest version of this eventually comes down to one thing, and it is not technical.
Tell one person. Someone steady, who will not hand the passcode straight back when you ask for it in a bad moment. Their job is not to police you or to read your history. Their job is to hold something you cannot get at, and to be willing to say no.
- Ask them. Trusted person has wording for the conversation if you do not know how to start it, and send them this so they know what they are agreeing to.
- Hand over the passcode, and on iPhone fix the recovery prompt from step 3.
- Agree what they should refuse, and what counts as a real emergency, before you need either.
- Later, when you have the energy: run the recovery audit to find the passwords and reset paths that could quietly undo all of it.
What to ignore for now
Consider this explicit permission to close the other tabs.
The rest of this site is written for specific problems that you may not have. Router configuration, browser policy files, device supervision, and Apple Configurator are all real answers to real gaps, and none of them are your first move. They matter when the simple version has failed in a specific way, and you will know which way that was when it happens.