Ad & Tracker Blocking

Category overview · ProPrivacyTime

Blocking happens in three layers - browser extensions, DNS filters, and privacy browsers - and each sees a different slice of tracking. The durable setup layers them deliberately.

Most privacy advice treats "use an ad blocker" as a single switch. In practice the switch does not exist. An ad or a tracker can reach you through your browser tab, through a native app, or through the quiet name-lookup that happens before any page loads. A tool that only watches one path leaves the other two open. That is why this category treats blocking as three distinct layers:

• Browser extensions sit inside the browser and read the full page - every request, script, and element. They have the most detail and the finest control.
• DNS filters work at the name-resolution step, before a connection to a tracking domain is ever made. They see only domain names, but they cover every app on a device, not just the browser.
• Privacy browsers build blocking into the engine itself, adding fingerprint resistance that neither standalone tool can match.

Each layer sees a different slice of the same problem. A browser extension cannot stop a tracker that fires from a background app; a DNS filter cannot tell a tracking script from a needed one on the same hostname; a privacy browser protects only its own sessions. The setup that holds up over time places these layers on purpose - a quiet baseline at the network level, a precise blocker where you read, and a hardened browser for the sessions that matter.

How we evaluate tracker blockers

We do not run speed tests or infection simulations, and we make no first-person "we tested it" claims. Instead we read what vendors actually publish - their filter-list sources, privacy policies, documentation, and fine print - and we judge a blocker on document-based criteria:

• What the layer can and cannot see. A browser blocker and a DNS filter are not comparable on the same axis. We note the structural blind spots of each rather than pretending one number ranks them.
• Default-block lists and their maintenance. A blocker is only as good as the lists it ships and how often they are updated. We look for named, maintained filter sources and a clear update cadence, not an opaque "smart" engine.
• The privacy of the blocker vendor itself. A tool that blocks trackers while logging your every query is a poor trade. We read the vendor's own policy on logging, resolution, and "acceptable ads" whitelists.
• Configurability. Defaults are usually set to avoid breaking the web, which often means weak protection out of the box. We check whether the meaningful settings are reachable and documented.

Common misconceptions

• "One blocker covers everything." A single layer sees a single slice. Browser-only blocking leaves apps exposed; DNS-only blocking leaves page-level trackers and fingerprinting intact.
• "Blocking ads also blocks all trackers." Many trackers load from the same domains as the content you want, or use first-party requests that an ad list never targets. Ad blocking and tracker blocking overlap but are not the same job.
• "A private browser equals full privacy." A privacy browser protects its own sessions and adds fingerprint defense, but it does nothing for the other apps on your device or for the network traffic leaving them.
• "DNS blocking is enough on its own." DNS filtering is the best household-wide baseline, but it cannot remove an ad that shares a domain with content, cannot collapse empty page slots, and cannot stop fingerprinting.

Where to start

For the full comparison of the three layers, their trade-offs, and the over-blocking trap most people hit, start with the guide below. The second link goes to a specific product page for a vendor we reference.