Some sites should simply not open.

Most blockers want to become your life coach. This one just blocks websites.

Add a domain and it stops opening. Switch it off when you want it back. There are no accounts, timers, streaks, schedules, or password gates, and no button on the block page to click straight through.

Three permissions, and why

storage

Keeps your blocklist and theme choice on this device.Without it the list could not survive closing the tab. It is local storage only, never cloud sync.

declarativeNetRequest

Hands Chrome one rule per domain you have switched on.Chrome does the refusing, in its own network stack. The extension declares rules and never sees a request.

webNavigation

Tells the extension a navigation happened, so a blocked one gets a readable page.It also catches sites that answer their own navigation from a service worker cache, which network rules cannot see.

No host permissions. No content scripts. It cannot read or change any page you visit, and it makes no network requests of its own.

Questions

Do you run analytics?

No. No telemetry, no error reporting, no “anonymous usage statistics that help us improve the product”. The extension makes no network requests of any kind. Not one. Its typeface is bundled in the package for exactly that reason.

Are there ads?

No. Nothing is injected into any page, because the extension has no way to touch a page at all.

Does it cost anything, now or later?

No. There is no paid tier, no trial, no licence key, and nothing to upgrade. It is finished software under a licence that lets you do whatever you like with it.

Do I need an account?

No. There is nothing to sign up for and nothing to sign in to.

Does it ask to read and change data on every website?

No. That prompt comes from host permissions, and blockx declares none. It also has no content scripts, so it cannot read or modify any page you visit.

Can you see my browsing?

The developer cannot. Chrome does hand the extension navigation URLs through webNavigation so it can catch a blocked site. Those URLs are compared with your list locally, discarded immediately, and never stored or transmitted. Only the hostname of a blocked URL reaches the local blocked page.

Can I sync my blocklist between devices?

No. It lives in local extension storage and stays there. Syncing means an account, or at minimum handing your list of “sites I can’t stop visiting” to a sync server. Copy it across yourself; it is a list of domains.

Does it have streaks, scores, or a productivity dashboard?

No. It blocks websites.

Can I get past the block page without touching the list?

No. There is no bypass button, no timer, no “five more minutes”. The page is a dead end on purpose. Open the list and switch the entry off if you mean it.

Can I lock myself out by blocking the blocklist?

No. The blocklist lives on a chrome-extension:// address, and only http and https are ever considered for blocking. An extension id has no dot in it either, so it cannot be entered as a domain. There is a test for that.

Does it block tabs I already have open?

Not until they navigate or reload. Blocking applies to requests, and an open page has already made its. Shutting it down retroactively would mean reading the URL of every tab you have open, which needs a permission whose warning is “Read your browsing history”. That is a bad trade for saving you one keystroke.

Will it ask for more permissions in an update?

It asks for three and needs all three. If that ever changed, Chrome would disable the extension until you approved the new ones. Read that prompt carefully — for anyone’s extension, not just this one.

Should I trust a random blocker from the internet?

No, and that is rather the point. It is a small set of readable JavaScript modules with no bundler and no runtime framework. Read it. Privacy claims are easier to trust when you can check them.

Free, local, open source, and finished.