Maker here. I built this because MV3 made every blocker worse at the one thing that matters when something goes wrong: telling you what it did. Under MV3 the static rulesets are compiled into the package and can't change until a store release clears review. So when a rule over-blocks and breaks a checkout page, you're stuck. The usual answer is a badge with a number on it, which tells you nothing you can act on. JSK Shield shows the request that was blocked, the exact filter rule that matched it, and the list that rule came from - then lets you allow that one request on that one site. If a page does break, guided recovery tries the least destructive fix first: allow one request, then turn off element hiding while keeping ads blocked, and only then pause the site. Two things I'd genuinely like feedback on. Filter fixes arrive between store releases through a small set of dynamic rules that are cryptographically signed, and the extension fails closed on a bad signature - an unsigned remote channel into a blocker is a backdoor. And network blocking needs no permission to read the pages you visit; per-site access is only requested for the extras that need it. Being straight about what it isn't: uBlock Origin blocks better than this. Years of filter authoring and a cosmetic engine I don't match. If you're on Firefox and happy with uBO, stay there. This is aimed at MV3 Chrome and Edge users who've been pushed onto a Lite-class blocker and want to know why a page broke. GPL-3.0, source is public. No telemetry, no analytics, no paid allowlist - that last one isn't negotiable. Blocking is free and identical on every plan; there's a paid Family tier that adds parental controls, and that's the only thing behind a payment. Happy to answer anything about the DNR rule budget, cosmetic filtering under MV3, or the signing setup. Criticism welcome.

JSK Shield

The ad blocker that shows you the rule it blocked with

The ad blocker that shows you the rule it blocked with