A full-page block means a filter in one of your lists matched the page's own address, so your blocker stopped it before connecting. Here's how to read it.
You click a link and, instead of the page, your ad blocker shows a warning that the page was blocked because of a matching filter in a list such as EasyList. Nothing loaded, and the site never got a chance to show you anything. This is a different thing from an ad being hidden inside a page: the blocker has refused the whole document.
Key Takeaways
- It is your own extension acting, not the website. One of the filter lists you have enabled contains a rule that matches the page address itself, so the blocker stopped the page before the browser connected to the server.
- A block screen is not a verdict that the site is malicious. uBlock Origin's documentation states that a strict-blocking warning does not necessarily mean the site is harmful; it only means a matching filter exists in your selected lists.
- Which rule matched is the useful part. Domain-only rules block the root document by default, while other patterns do so only when they carry the
documentoralloption. Knowing the rule tells you whether it is a deliberate listing or a broad pattern catching an innocent page. - The fix is narrow, not "turn the blocker off". Go back, proceed temporarily for a page you trust, add a per-site exception, or report a false positive to the list maintainers.
- This post is the user-side view. How sites detect that you run a blocker is covered separately, and nothing here is advice on evading a site's protections.
What "blocked a whole page" actually means
Most of what an ad blocker does is invisible. It hides an ad slot, drops a request to a tracking script, and the page you asked for still loads around the gap. Strict blocking is the exception: the filter matched the document you were trying to open, so there is nothing left to load around.
In uBlock Origin's own words, strict blocking blocks the whole page: the root document is blocked, so the browser makes no connection to the server that hosts it. The wiki notes that other blockers such as Adblock Plus only filter secondary resources, and that uBlock Origin did the same until version 0.9.3.0, when it began filtering web pages themselves. Other blockers show their own screens with different wording, and the exact sentence you saw depends on the product. What they share is the mechanism, and that is what the rest of this post explains.
Why a filter matches a page address
A static network filter is a pattern tested against a URL. The rule decides two things: what the pattern looks like, and which request types it applies to. According to uBlock Origin's strict blocking documentation, the answer to "does this block the page itself?" comes down to two cases:
- Domain-only filters such as
||example.com^trigger strict blocking by default. The wiki says this default exists to reduce false positives: a rule that names a whole host is a deliberate statement about that host. - Other pattern-matching filters trigger it only when they use the
documentoption (aliasdoc) or thealloption.
The static filter syntax page describes the building blocks. The document option matches the main frame, the root page, and a filter that gives only a hostname includes it automatically. The all option is shorthand for every network request type plus popups, documents, inline fonts and inline scripts. In uBlock Origin a plain hostname pattern means "this site and all its subdomains", and it covers the main document too.
Where do these rules come from? Mostly from the community-maintained lists your blocker subscribes to. EasyList is the best known, and its repository is also where its issue tracker lives. A list entry can be there because the domain really does serve ads or trackers, because it is a redirector or a link shortener that lists treat as a tracking hop, or because a broad pattern was written to catch one thing and caught another. A domain that changed hands may also still carry a listing written for its old owner.
How to read the block screen
The block screen is more informative than it looks. Work through it in this order:
- Find the list and the rule. uBlock Origin's block page names the filter that matched. Whether a rule is a bare hostname or a longer pattern with
$documentor$alltells you how deliberate the listing is. - Look at the address. The wiki points out that when a blocked URL has a query string, uBlock Origin can break it into parameters. For a redirect link, the real destination often sits in one of them. If it does, the redirector was the thing listed, and the final page may be fine on its own.
- Ask whether you expected this site. A block on a host you have never heard of, reached through an unsolicited link, is the filter list doing its job. A block on a page you navigate to every day is more likely a false positive.
Your options on the block screen
uBlock Origin's block page offers a short set of choices:
- Go back returns you to the previous page. This is the right choice when you did not mean to be there.
- Proceed (temporary) disables strict blocking for a limited time. The default is 120 seconds, and it is configurable through the
strictblockingbypassdurationadvanced setting. Use this for a page you trust and need once. - Proceed (permanent) is done by ticking "Don't warn me again about this site" before clicking Proceed. The site is then filtered the way it was before strict blocking existed: its resources can still be blocked, but the page itself is allowed to open.
The wiki also documents a global switch: adding no-strict-blocking: * true in the My rules pane and clicking Commit disables strict blocking everywhere. That is a much bigger lever than the problem usually needs. It turns off a safeguard for every site to fix one, so prefer the per-site choices above.
A diagnosis checklist for false positives
If the page is one you trust and the block looks wrong, treat it as a bug report rather than a battle with your blocker:
- Identify the matched rule and the list it came from. Do not guess; the block page tells you.
- Check whether the list is up to date. Lists are updated regularly, and a stale copy can keep an entry that maintainers have already fixed. Update your lists and reload.
- Report the false positive to the list maintainers. The EasyList project tracks issues on github.com/easylist/easylist. A report there fixes the rule for everyone, whereas the extension vendor does not own the list contents.
- Use the narrowest exception that works. An exception filter (
@@) lets matching requests through, and it can be scoped to one site. That beats disabling the blocker entirely. - Proceed temporarily only for pages you trust. The warning is there because something matched; a few seconds of friction is cheap compared with loading an unknown page.
A note on scope: this is about handling a block you hit by accident on a legitimate page. It is not a guide to bypassing a site's protections or anyone's access controls.
Does this work the same in every browser?
Not exactly. The classic uBlock Origin inspects each request in script and shows its own block page; it remains fully supported on Firefox, while Chrome has phased out the Manifest V2 extension platform it was built on. Under Chrome's Manifest V3, extensions that block network requests are expected to hand the browser a compiled rule set through declarativeNetRequest instead of inspecting each request in script, so the way a "blocked page" is presented, and which rule options exist, can differ between blockers. The idea carries over, though: a rule from a filter list matched a document URL, and the blocker acted on it before the page loaded.
Check which browser actually has a blocker on
If you are not sure which browser profile is doing the blocking, BrowserInsight's plugin and extension check runs the same bait-element test that sites use, so it shows whether a content blocker is active in the browser you are using right now. It is a cosmetic test, so a network-level blocker such as a filtering DNS service will not show up in it. For the site-side view, see how websites detect your ad blocker. For the trust question of what a filtering extension can see on the pages you visit, read browser extension privacy risks. And if a block involves a domain that looks first-party but is not, CNAME cloaking explains why lists also target tracker hosts disguised as subdomains.
Frequently Asked Questions
Does a blocked-page warning mean the website is dangerous?
No. It means a filter in one of your selected lists matches the address. That can be a real ad or tracking host, but it can also be a broad pattern or an outdated entry, so check the matched rule before drawing a conclusion.
Is the website blocking me, or is my ad blocker blocking the website?
Your ad blocker. With strict blocking the browser makes no connection to the server at all, so the site never sees the request and cannot have refused it.
How long does "Proceed" last in uBlock Origin?
By default the temporary bypass lasts 120 seconds, adjustable through the strictblockingbypassduration advanced setting. Ticking "Don't warn me again about this site" before proceeding makes it permanent for that site.
Where do I report a rule that blocks a legitimate page?
To the maintainers of the list that contains the rule. For EasyList that is its issue tracker on GitHub. The extension itself only reads the list.
