Many protections only apply to domains that a browser has decided are trackers. How a browser makes that decision matters as much as what it does afterwards: the same vendor can be a “known tracker” in one browser and an ordinary third party in another.

Browsers use two broad approaches:

  • Lists. Firefox and Edge use the Disconnect.me lists, which sort tracking domains into categories such as Advertising, Analytics, Social, Fingerprinting and Cryptomining. Brave uses ad-blocking filter lists such as EasyList and EasyPrivacy. Lists are public and predictable, but they need maintaining and react slowly to new domains.
  • On-device classification. Safari’s Intelligent Tracking Prevention watches which domains show up as third parties on many different sites, or redirect the user through many sites, and classifies them on the device. Each Safari user can end up with a slightly different set of classified domains.

Chrome doesn’t classify trackers for its default protections.

By browser

Brave

  • Filter lists: EasyList, EasyPrivacy, uBlock Origin lists and Brave’s own lists.
Sources (1) · 2026-10-31

Chrome

  • n/a

Edge

  • Disconnect.me lists, delivered as Trust Protection Lists, with organization and engagement mitigations. New
Sources (1) · 2026-10-31

Firefox

  • Disconnect.me
Sources (1) · 2026-10-31

Safari

  • Algorithmic

History

  1. Edge

    New Edge ships with tracking prevention

    The Chromium-based Edge 79 is released with tracking prevention set to Balanced by default.

    affects: known trackers, 3rd-party cookies · source: Tracking prevention in Microsoft Edge

  2. Safari

    Intelligent Tracking Prevention 1.0

    Safari starts classifying cross-site trackers on the device and restricting their cookies.

    affects: known trackers, 3rd-party cookies · source: Intelligent Tracking Prevention (WebKit blog)