Realtime

Watch blocked requests as they happen, and see which app asked and why it was blocked.

The log

Blocked requests shows the most recent blocks, newest first: Time, Domain, App (the program that asked, when Windows says), Network, Category and Matched rule (the rule and the list it came from; via CNAME means a harmless-looking domain pointed at a blocked one).

• Type in Filter by domain or network… to search.
• All apps narrows the log to one program.
• The group buttons narrow it to Ads, Privacy, Threats or Content, the same groups as the sidebar pages. Other shows the rest: blocked secure DNS services (so apps can't route around AdBolish), Firefox's secure DNS check, and your own custom blocks.
• Pause stream freezes the log so it stops scrolling while you read. Resume stream picks it back up.

The log only holds recent blocks while AdBolish is running. Counts and charts are kept; the log itself is not saved.

Allowing from the log

Every row has an Allow menu with four choices:

• Allow domain: for every app.
• Allow network: every domain of that network, for every app.
• Allow app name: everything that app looks up.
• Allow domain for app only: the domain, only when that app asks.

The two app choices need the app to be known; when it isn't, they're greyed out with Windows hasn't said which app asked. Allowing a whole web browser asks first, because it turns ad blocking off for every site you visit in that browser. To fix one site, allow just the domain instead.

What usually goes wrong

• The App column is mostly empty. Telling apps apart needs the protection service. Click Set up on the banner (or in Settings ▸ Protection ▸ Protection service).
• "No blocks match." Your search, app or group filter hides everything. Clear the search box, choose All apps and All.