BlockMyself

Exact steps for stronger digital guardrails.

Start with built-in controls. Add DNS and browser friction. Use a trusted person when you need real lockout. The goal is not perfection; it is making the bypass hard enough that you do not casually do it.

BlockMyself

Choose a level

Start with the lowest level that could work. Add stronger layers only where the weaker setup fails.

Platforms

Use the device page first. Then add the network and lockout layers that apply to your situation.

More step-by-step guides

Use these when the basic device pages are not enough, or when you want a concrete recipe instead of building your own setup from scratch.

Bypass map

A strong setup covers the specific escape paths that match your device. Use this as the checklist before calling a setup finished.

Bypass path Why it works Where to harden it
Installing another browser Some filters only cover one browser or one account. Block app installs, remove extra browsers, use browser policy, and use router or DNS filtering.
Changing DNS DNS filters fail if the device can choose a different resolver. Use standard-user accounts, router DNS enforcement, Private DNS profiles, and trusted-person admin control.
VPN, proxy, Tor, iCloud Private Relay, or mobile hotspot Traffic can leave through a path that does not use your filter. Block app installs, restrict VPN/profile changes, use network rules where possible, and disable unneeded cellular/hotspot access.
Admin, root, or owner access The person with admin can uninstall, change policy, edit hosts files, or reset settings. Use a standard daily account and let a trusted person hold the admin password.
Factory reset or external boot A local reset can remove device-level restrictions. Use account recovery controls, device management where practical, disk encryption recovery keys off-device, router-level blocking, and physical access controls.
Saved recovery codes and password managers You can undo the setup by recovering the parent, admin, DNS, or router account. Run the Recovery audit and move recovery paths to the trusted person.
Cellular data and hotspots Home router rules do not apply when traffic leaves through another network. Use Mobile data and hotspots plus device-level controls.
In-app browsers and platform settings Content can appear inside apps that do not use the managed browser path. Use Apps and platforms and test each app directly.
Portable browsers, developer tools, and package managers Technical users may run tools from Downloads, USB drives, Homebrew, winget, WSL, Docker, or other user-writable paths. Use standard daily accounts, app allowlisting, browser policy, and trusted-person admin control.
Remote desktop and cloud workstations The blocked device can become only a viewer for another unrestricted computer. Block or approve remote-desktop tools, SSH, RDP, VNC, cloud IDEs, and unmanaged virtual desktops.
AI, chat, image, or roleplay tools Risky content may appear inside broad-purpose apps instead of a known adult-content domain. Use Apps and platforms, app blocks, account controls, and trusted-person recovery.
Old or shared devices A spare phone, smart TV, console, tablet, or family computer may still have an unrestricted browser. Inventory every screen you can access and include it in Recovery audit.

What to do first

  1. Pick the device you actually use when you bypass.
  2. Complete the built-in guide for that device in Guardrails.
  3. Test the block in every browser and account that still exists with Test your setup.
  4. Add the DNS, router, and policy steps in Friction.
  5. Move passcodes, admin credentials, recovery keys, and router logins to the trusted person when you need Lockout.

Official resources

Menus change. These are useful reference points when a step name has moved.