<?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>Webrtc on Vitalii Zaiats</title>
    <link>https://vitalii-zaiats.com/tags/webrtc/</link>
    <description>Recent content in Webrtc on Vitalii Zaiats</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 15 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://vitalii-zaiats.com/tags/webrtc/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The extra hop: counting a visitor&#39;s NAT layers from the outside</title>
      <link>https://vitalii-zaiats.com/posts/counting-nats-reverse-traceroute/</link>
      <pubDate>Wed, 15 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://vitalii-zaiats.com/posts/counting-nats-reverse-traceroute/</guid>
      <description>A NAT is a router that subtracts one from the TTL, so every NAT layer is a hop you can count. I built a small tool that reverse-traces a visitor back through the hole their own connection punched — and asked the honest question: is any of it useful for catching bots? Mostly no, sometimes cheaply yes.</description>
    </item>
  </channel>
</rss>
