Methodology

How the Adblock.io Quick Check works

Understand how Adblock.io observes delivery, matches pinned filter lists, reviews creative, and labels remaining uncertainty.

Current scope

Quick Check v0.2 combines three independent modules: delivery inspection, static EasyList/EasyPrivacy matching, and optional AI creative review. A visitor can run any useful subset. The overall score appears only when all three modules return a score.

URL inspection follows at most three redirects, reads at most 220 KB of eligible text, and samples up to 100 document resources. The result is a preflight review, not proof of delivery in every browser or privacy configuration.

Finding methods

MethodMeaningExample
ObservedDirectly measured during the request.HTTP status, redirect count, image dimensions.
HeuristicA conservative pattern that needs further verification.An ad-related token in a hostname or resource path.
Static ruleA request decision made by a pinned filter engine and named list snapshot.An EasyList or EasyPrivacy network rule.
AIA model-generated rubric result with evidence and confidence.Message clarity or CTA specificity.

AI image reviews use @cf/moondream/moondream3.1-9B-A2B for visible evidence and@cf/qwen/qwen3-30b-a3b-fp8 for the schema-validated rubric. Copy-only reviews use Qwen3 directly. Model identifiers are included in successful reports.

How the score is formed

Delivery, filter exposure, and creative readiness each have a separate 0–100 score. When all three are available, the overall score weights delivery at 30%, filter-list exposure at 35%, and creative readiness at 35%. The detailed findings remain more important than the summary number.

  • 85–100: low immediate risk in the checks currently available.
  • 65–84: review recommended before launch.
  • 0–64: high preflight risk or a delivery failure.

Known limitations

The beta does not run installed ad blockers.

Firefox, Brave, Safari, iPhone, DNS, and extension profiles will be added as separate observed environments.

A browser extension can use a complete executed page, request context, cosmetic rules, user settings, and a different list version. The static module checks the main document and resource URLs found in sampled HTML. It does not execute JavaScript, apply cosmetic filtering, or observe requests created after page load.

Product principles

  • Show evidence and method for each conclusion.
  • Do not invent absolute CTR, conversion, or revenue predictions.
  • Do not provide cloaking or instructions intended to evade user choices.
  • Recommend removing unnecessary tracking and repairing false positives.
  • Publish material changes to methods and scoring in the changelog.
  • Publish the exact filter-list versions used by the current deployment.