A new web page called "Taken" reveals the hidden HTTP requests your browser makes to third-party services without your explicit consent. By leveraging the browser's DevTools protocol, the tool exposes the invisible data flows between websites and tracking scripts, analytics services, and other external endpoints.
Overview
When you visit a website, your browser typically sends dozens of requests to servers you never intended to contact. These include tracking pixels, analytics beacons, ad network calls, and content delivery network fetches. Most users never see this activity. "Taken" makes it visible by intercepting and displaying every HTTP request the browser initiates during a page load — including those triggered by JavaScript, CSS, images, and fonts.
What it does
The page uses the browser's DevTools protocol to capture network activity. When you open "Taken" in a browser with DevTools enabled, it logs every request the page makes, categorizing them by destination domain, request type, and timing. The result is a real-time list of all third-party connections your browser made just to render the page.
Tradeoffs
"Taken" is a transparency tool, not a blocker. It shows what happens but does not prevent any requests. To stop unwanted tracking, you would still need a dedicated ad blocker, privacy extension, or browser-level protection like Firefox's Enhanced Tracking Protection or Safari's Intelligent Tracking Prevention.
The tool also requires DevTools to be open, which means it is primarily useful for developers and technically inclined users. Casual users may find the output overwhelming without context.
When to use it
"Taken" is useful for:
- Auditing a website's third-party dependencies
- Understanding which services a site contacts without user interaction
- Teaching or demonstrating how browser-based tracking works
- Checking whether a site respects privacy expectations
Bottom line
"Taken" is a straightforward demonstration of the hidden data flows that occur on every page load. It does not solve the privacy problem, but it makes the problem visible — which is a necessary first step for anyone who wants to understand what their browser is doing behind the scenes.