<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Posts on watchkeeper.net</title>
    <link>https://watchkeeper.net/posts/</link>
    <description>Recent content in Posts on watchkeeper.net</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 23 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://watchkeeper.net/posts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A Recipe Blog Adds a Data Broker and a Video Ad Network Between Two Visits</title>
      <link>https://watchkeeper.net/a-recipe-blog-adds-a-data-broker-and-a-video-ad-network-between-two-visits/</link>
      <pubDate>Fri, 23 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://watchkeeper.net/a-recipe-blog-adds-a-data-broker-and-a-video-ad-network-between-two-visits/</guid>
      <description>&lt;p&gt;Sites change their trackers all the time, and nobody tells their readers. A new ad deal, a new plug-in or a theme update can add a company to every page overnight. The Last visit section is there to catch that.&lt;/p&gt;&#xA;&lt;p&gt;This case study uses a made-up recipe blog whose page changes between visits. The first time it&amp;rsquo;s opened in Watchkeeper, the panel counts three other sites: an analytics service, an ad pixel and the ad partner the pixel calls. On the next visit the same soup recipe tells five.&lt;/p&gt;</description>
    </item>
    <item>
      <title>A Shop Page Calls Five Other Sites Before Anyone Answers Its Cookie Banner</title>
      <link>https://watchkeeper.net/a-shop-page-calls-five-other-sites-before-anyone-answers-its-cookie-banner/</link>
      <pubDate>Fri, 23 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://watchkeeper.net/a-shop-page-calls-five-other-sites-before-anyone-answers-its-cookie-banner/</guid>
      <description>&lt;p&gt;Picture the owner of a small clothing shop. She added a cookie banner because her web designer said the law needed one, and she assumes nothing goes out until a visitor clicks Accept. This case study is built on a made-up shop page that behaves the way many real ones do.&lt;/p&gt;&#xA;&lt;p&gt;Open the product page in Watchkeeper and leave the banner alone. Before you&amp;rsquo;ve read the first line, the panel lists five other sites.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Checking a Staging Site on Localhost Before It Goes Live</title>
      <link>https://watchkeeper.net/checking-a-staging-site-on-localhost-before-it-goes-live/</link>
      <pubDate>Fri, 23 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://watchkeeper.net/checking-a-staging-site-on-localhost-before-it-goes-live/</guid>
      <description>&lt;p&gt;The best time to find out what a page sends is before it&amp;rsquo;s live. Watchkeeper opens a local copy as easily as a public site, so a developer can check a build on their own machine before anyone else loads it.&lt;/p&gt;&#xA;&lt;p&gt;Start the staging server as usual, then point Watchkeeper at it. A local address needs its http:// written out:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; style=&#34;color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;&#34;&gt;&lt;code class=&#34;language-sh&#34; data-lang=&#34;sh&#34;&gt;&lt;span style=&#34;display:flex;&#34;&gt;&lt;span&gt;watchkeeper http://localhost:8090/&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;&lt;img src=&#34;https://watchkeeper.net/images/example-staging-localhost.png&#34; alt=&#34;Watchkeeper on a staging copy of a shop at localhost:8090. The panel lists four other sites: an ad pixel, analytics, the pixel&amp;rsquo;s ad partner and session-replay.example, plus a canvas read by the ad pixel.&#34;&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>How Watchkeeper Was Tested Against a Page Built to Fool It</title>
      <link>https://watchkeeper.net/how-watchkeeper-was-tested-against-a-page-built-to-fool-it/</link>
      <pubDate>Fri, 23 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://watchkeeper.net/how-watchkeeper-was-tested-against-a-page-built-to-fool-it/</guid>
      <description>&lt;p&gt;A tool that says &amp;ldquo;this page contacted five sites&amp;rdquo; is only worth something if the page really contacted five sites. Watchkeeper&amp;rsquo;s main promise is that nothing a page does gets missed, and that the page can&amp;rsquo;t hide from it or tamper with it. So the tests don&amp;rsquo;t ask Watchkeeper what it saw and trust the answer. They ask the servers.&lt;/p&gt;&#xA;&lt;p&gt;The self-test runs the real app, on the system&amp;rsquo;s own web engine, against two small web servers started on the same machine. One plays the site at 127.0.0.1. The other plays a tracker at localhost, which counts as a different site. Both write down every request they receive, and those logs are the ground truth: whatever reached a server must be in Watchkeeper&amp;rsquo;s report.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How Web Tracking Works and Why You Never See It</title>
      <link>https://watchkeeper.net/how-web-tracking-works-and-why-you-never-see-it/</link>
      <pubDate>Fri, 23 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://watchkeeper.net/how-web-tracking-works-and-why-you-never-see-it/</guid>
      <description>&lt;p&gt;A web page isn&amp;rsquo;t one thing from one place. The article comes from the news site, but the fonts may come from a font service, the ads from an ad network, the share button from a social network and the visitor counter from an analytics company. Your browser fetches each piece from wherever it lives, and every one of those places learns that someone at your internet address just opened that article.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Sending a Landing Page Report to the Agency That Built It</title>
      <link>https://watchkeeper.net/sending-a-landing-page-report-to-the-agency-that-built-it/</link>
      <pubDate>Fri, 23 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://watchkeeper.net/sending-a-landing-page-report-to-the-agency-that-built-it/</guid>
      <description>&lt;p&gt;Say a small software company paid an agency to build its sign-up page, and a customer asks a question nobody in the company can answer: which companies does your sign-up page send my visit to? This case study answers it for a made-up landing page.&lt;/p&gt;&#xA;&lt;p&gt;Open the page in Watchkeeper and press Save report. You get two files: an HTML page anyone can open and a JSON file for tools. The HTML version starts like this.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Telling a Fingerprinting Script Apart From a Page Saving Its Own Chart</title>
      <link>https://watchkeeper.net/telling-a-fingerprinting-script-apart-from-a-page-saving-its-own-chart/</link>
      <pubDate>Fri, 23 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://watchkeeper.net/telling-a-fingerprinting-script-apart-from-a-page-saving-its-own-chart/</guid>
      <description>&lt;p&gt;Reading back a canvas is the classic first step of a device fingerprint. It&amp;rsquo;s also how a page turns a chart into an image you can download. So a canvas read on its own proves nothing. What matters is who made it.&lt;/p&gt;&#xA;&lt;p&gt;This quiz page draws a bar chart of your answers and offers it as an image, which takes one canvas read by the page&amp;rsquo;s own code. It also loads a script from a fingerprinting vendor.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Watchkeeper Is a Tiny Free Browser That Shows You Who Is Watching</title>
      <link>https://watchkeeper.net/watchkeeper-is-a-tiny-free-browser-that-shows-you-who-is-watching/</link>
      <pubDate>Fri, 23 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://watchkeeper.net/watchkeeper-is-a-tiny-free-browser-that-shows-you-who-is-watching/</guid>
      <description>&lt;p&gt;Open a news article and you see a headline, some text and an ad or two. You don&amp;rsquo;t see the other companies the page told about your visit while it loaded. On many news sites that list runs to a dozen names or more, and nothing in a normal browser window mentions any of them.&lt;/p&gt;&#xA;&lt;p&gt;Watchkeeper is a small browser built to show that list. You type an address and use the page as you would anywhere else. A panel on the right fills in as the page works: the other sites it contacts, the cookies it leaves, the keys it writes to your computer and the scripts that read your device&amp;rsquo;s fingerprint.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Why a Browser That Watches Trackers Is Called Watchkeeper</title>
      <link>https://watchkeeper.net/why-a-browser-that-watches-trackers-is-called-watchkeeper/</link>
      <pubDate>Fri, 23 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://watchkeeper.net/why-a-browser-that-watches-trackers-is-called-watchkeeper/</guid>
      <description>&lt;p&gt;On a ship, someone is always on watch. While the rest of the crew sleeps, eats or works below, one officer stays on the bridge, keeps a lookout and notes what passes. That person is the watchkeeper, and watchkeeping is still the word sailors use for the job.&lt;/p&gt;&#xA;&lt;p&gt;The day is cut into watches of about four hours, so nobody has to stay alert for too long. Whoever has the watch looks out for other ships, lights and changes in the weather, and writes what they see in the log. The captain doesn&amp;rsquo;t have to stand there all night. The log says what happened.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
