<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Anti-Detect on Vitalii Zaiats</title>
    <link>https://vitalii-zaiats.com/tags/anti-detect/</link>
    <description>Recent content in Anti-Detect on Vitalii Zaiats</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 22 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://vitalii-zaiats.com/tags/anti-detect/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A browser can fake its WebRTC address — it can&#39;t fake the packet</title>
      <link>https://vitalii-zaiats.com/posts/active-stun-probing/</link>
      <pubDate>Wed, 22 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://vitalii-zaiats.com/posts/active-stun-probing/</guid>
      <description>Every WebRTC leak check reads a value the browser reports, and an anti-detect browser reports whatever keeps you happy. So I stopped reading its answer and started checking mine: run the STUN server yourself, and whether a packet actually arrived becomes the one thing the browser can&amp;rsquo;t forge. Here&amp;rsquo;s the idea, a widget to test your own browser, and an honest tour of everywhere it fails.</description>
    </item>
  </channel>
</rss>
