Block the sites you've decided are off-limits.

Gambling is where GuardianBlock starts. From there, you decide what else belongs on your own no-go list.

Start with gambling, then add your own.

GuardianBlock leads with gambling; the list is yours to extend. These are examples of what people add, not what GuardianBlock reaches on its own — it works from the domains you declare and it doesn't try to police the entire internet for you.

  • betting sites
  • trading apps
  • shopping
  • adult sites

You see what a block covers before you confirm it.

When you add a domain, GuardianBlock previews the scope it covers, so there are no surprises about what's included.

  • registrable domain + subdomains

    Registrable domain, by default

    Default

    Declaring a registrable domain off-limits also covers its subdomains, so you don't have to list each one by hand. The preview shows you that scope before you confirm.

  • exact host

    Exact host, when you want it

    Advanced option

    Prefer to narrow a block to one specific host instead of the whole website and its subdomains? That's available as an advanced option.

  • path-level

    Path-level isn't in this build

    Not in this build

    Blocking one specific page inside a larger site is not supported. You can block a whole website and its subdomains or one specific host.

You decide what goes on. Taking one off stays accountable.

The no-go list belongs to the person it protects. Adding a block is easy; undoing one in a weak moment is not a quiet switch.

  1. You build the list

    The no-go list is yours. You add the domains you've decided to stay away from, in your own words.

  2. Your partner can propose

    An accountability partner can suggest a domain worth adding, but a proposal becomes a block when you confirm it, and not before. Nothing is added behind your back.

  3. Not a silent one-tap toggle

    Removing a domain from your no-go list is a real change, not a switch you can flip on impulse and forget about.

  4. Your keyholder is in the loop

    Because removals are partner-accountable, your keyholder sees the request and can help you honour the decision you made earlier, when it was easier to think clearly.

A custom block is a decision, not a feed.

Your partner can see which domains you've declared off-limits, so a removal stays accountable — never your browsing history or the private note behind a block.

See exactly what you share

What a custom block keeps

  • The domain or exact host you declared off-limits.
  • An optional short note to yourself about why — kept minimal.
  • Whether the block is currently active.

What a custom block is not

  • A record of the sites you actually visit.
  • Your browsing history, searches, or keystrokes.
  • A monitoring feed sent to your accountability partner.

Decide your no-go list while it's easy.

Set the lines you don't want to cross in a calmer moment, and let an accountability partner help you hold them.

Start GuardianBlock