blastradius

loading snapshot…

See the blast radius of an ad-block filter rule before you ship it. Type a candidate filter rule and this page shows exactly which network requests it would change across a corpus of real web-page causal graphs - plus everything downstream that only loaded because of them. Built on Brave's PageGraph and the same adblock-rust engine Brave Shields uses, running entirely in your browser.

How it works
  1. Type a rule (e.g. ||example.com^). It is compiled live with Brave's adblock engine in your browser.
  2. blast radius re-decides every request in the corpus under the base list vs. your candidate (Tier 1), then walks the provenance graph for everything downstream of a new block (Tier 2).
  3. Read the result: which requests flip allow→block and the structural footprint, risk-stratified. This is a structural estimate - the behavioral "does the page actually break?" check is Tier 3 (a paired Brave re-crawl, run locally).
booting duckdb-wasm…

Rule impact - blast radius

"What requests, and downstream effects, would change if I add rule X?" Tier 1 decision deltas + Tier 2 structural footprint, decided live in your browser with Brave's adblock engine. Structural estimate, not behavioral.

high first-party request or critical API (payments/auth) in the blast radius review removal/exception, undetermined party, or missing attribution low tracker-only - no first-party or critical reach

Persistent storage keys

Which persistent keys do scripts set across the corpus? Value-blind: key names, sizes, identifier category, setter-script reach - never the values. Click a key for its setter scripts.

Fingerprinting surface

Which JS APIs on the fingerprinting surface do scripts call across the corpus? Value-blind: API name, surface, distinct script / origin reach, vendors, call counts - never arguments or returns.