<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Iframes on pxta.com</title>
    <link>https://pxta.com/tags/iframes/</link>
    <description>Recent content in Iframes on pxta.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 25 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://pxta.com/tags/iframes/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Tracking Requests From Iframes and Web Workers, the Ones a Page Source Check Never Finds</title>
      <link>https://pxta.com/tracking-requests-from-iframes-and-web-workers-the-ones-a-page-source-check-never-finds/</link>
      <pubDate>Sun, 25 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://pxta.com/tracking-requests-from-iframes-and-web-workers-the-ones-a-page-source-check-never-finds/</guid>
      <description>&lt;p&gt;The quickest way to see which trackers a site uses is to read its HTML and look for known scripts. Plenty of free tools do just that. It finds the Meta Pixel in the page template, and it misses everything that isn&amp;rsquo;t there.&lt;/p&gt;&#xA;&lt;p&gt;Two places hide tracking from that kind of check: iframes and web workers.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://pxta.com/images/frames-workers.png&#34; alt=&#34;A diagram of one page with three sources of requests: the page&amp;rsquo;s own scripts sending to facebook.com/tr, an iframe such as a chat widget sending to collector.example, and a web worker sending to events.example.&#34;&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
