<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[1ms notes]]></title><description><![CDATA[Notes on exit IPs, HTTPS latency, and other network diagnostics, including 1ms.dog.]]></description><link>https://1ms-notes.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Wed, 18 Nov 2026 15:04:14 GMT</lastBuildDate><atom:link href="https://1ms-notes.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Your VPN changed your IP. Here is what it didn't change.]]></title><description><![CDATA[Disclosure: I'm Yang, and I made the tool mentioned at the end (who.1ms.dog, source under MIT at github.com/yt1988/who-are-you). I used AI help to tidy up…]]></description><link>https://1ms-notes.hashnode.dev/your-vpn-changed-your-ip-here-is-what-it-didn-t-change</link><guid isPermaLink="true">https://1ms-notes.hashnode.dev/your-vpn-changed-your-ip-here-is-what-it-didn-t-change</guid><category><![CDATA[privacy]]></category><category><![CDATA[browser]]></category><category><![CDATA[webdev]]></category><category><![CDATA[Security]]></category><category><![CDATA[Open Source]]></category><dc:creator><![CDATA[香蕉痞 Yang]]></dc:creator><pubDate>Fri, 13 Nov 2026 16:27:03 GMT</pubDate><content:encoded><![CDATA[<p><em>Disclosure: I'm Yang, and I made the tool mentioned at the end (<a href="https://who.1ms.dog">who.1ms.dog</a>, source under MIT at <a href="https://github.com/yt1988/who-are-you">github.com/yt1988/who-are-you</a>). I used AI help to tidy up the English; the content and the replies are mine.</em></p>
<p>Most people think of "being recognized online" as cookies and logins. But a page you open for the first time, with no account and no permission prompt, can already read a lot. And when those readings disagree with each other, that disagreement is itself a signal. Below are the leaks I ran into most often while building a page that collects them.</p>
<h2>1. The DNS resolver that actually looked you up</h2>
<p>Your browser goes through the VPN, but the system resolver may not. A site can make you resolve a random subdomain it controls and see which resolver asked. If the exit IP is in one country and the resolver sits at your home ISP in another, that's a leak, and a cheap one to detect.</p>
<p>Typical fixes: let the VPN client handle DNS, or for Clash-style setups use fake-ip / TUN mode so DNS goes through the tunnel too.</p>
<h2>2. WebRTC</h2>
<p>WebRTC asks STUN servers for your public address over UDP. If UDP bypasses the proxy (common with browser proxy extensions), the page sees a public IPv4 or IPv6 address that is neither the one it got the HTTP request from nor anything the VPN gave you.</p>
<p>Typical fixes: a system-wide tunnel instead of a browser proxy, or limiting WebRTC's IP handling in the browser.</p>
<h2>3. Timezone and language vs. the IP</h2>
<p><code>Intl.DateTimeFormat().resolvedOptions().timeZone</code> and <code>navigator.languages</code> come from your machine, not from the network. "IP in Frankfurt, clock in Asia/Shanghai, language zh-CN" is the classic "this is a proxy" tell. Nothing is leaking in the strict sense, but a site that wants to label you doesn't need a leak, only a contradiction.</p>
<h2>4. Canvas, WebGL and fonts</h2>
<p>Drawing the same text to a canvas gives slightly different pixels on different GPU/driver/font stacks. WebGL hands out the renderer string. Measuring the width of text in a list of fonts tells you which fonts are installed, even when local font access is blocked. None of this changes when your IP changes, so it's the part that follows you across VPN servers and private windows.</p>
<h2>5. The round trip</h2>
<p>If the browser's round trip is much longer than the one the CDN measures on its own TCP connection, there's probably another hop in between, like a proxy. A residential IP doesn't hide that.</p>
<h2>What I built</h2>
<p><a href="https://who.1ms.dog">Who Are You</a> runs these checks (127 readings in total, all without a permission prompt), writes the result as one paragraph ("who websites think you are"), and then checks the readings against each other the way a site would: timezone vs. IP, language vs. IP, DNS resolver country, WebRTC addresses, data-center network, user agent vs. client hints and WebGL, a tampered environment, whether the fingerprint is stable. Each failing check comes with a fix for the OS you're on. It's free, needs no account, and the whole thing is open source.</p>
<p>Known limits, so you don't have to find them yourself:</p>
<ul>
<li>The grade means "how consistent you look", not "how safe you are". Tor + VPN can get a worse grade while nothing actually leaks.</li>
<li>The language-vs-country rule produces false positives: a user in Kyrgyzstan whose device is in Russian was flagged as a bad disguise. Widely used languages should count as local in more countries; that's on my list.</li>
<li>"Unique" means unique among this page's visitors, not the whole internet.</li>
<li>It needs JavaScript, and it runs behind Cloudflare.</li>
<li>Anonymous counting can be switched off on the page; with Global Privacy Control on, nothing is counted.</li>
</ul>
<p>If it gets your setup wrong, comments here or an issue on GitHub are both welcome.</p>
]]></content:encoded></item><item><title><![CDATA[Check your real exit IP and HTTPS latency in the browser with 1ms.dog]]></title><description><![CDATA[I'm affiliated with 1ms.dog (the source is at This article was written with AI assistance. When you're on a VPN, proxy, split tunnel, homelab, or VPS, a…]]></description><link>https://1ms-notes.hashnode.dev/check-your-real-exit-ip-and-https-latency-in-the-browser-with-1ms-dog</link><guid isPermaLink="true">https://1ms-notes.hashnode.dev/check-your-real-exit-ip-and-https-latency-in-the-browser-with-1ms-dog</guid><category><![CDATA[networking]]></category><dc:creator><![CDATA[香蕉痞 Yang]]></dc:creator><pubDate>Fri, 06 Nov 2026 11:32:08 GMT</pubDate><content:encoded><![CDATA[<p>I'm affiliated with 1ms.dog (the source is at <a href="https://github.com/yt1988/1ms.dog">https://github.com/yt1988/1ms.dog</a>). This article was written with AI assistance.</p>
<p>When you're on a VPN, proxy, split tunnel, homelab, or VPS, a single “what is my IP” page only sees its own route. <a href="https://1ms.dog">1ms.dog</a> is a small public website that tries to answer two questions in the browser: where your traffic actually leaves, and how far common services are from you.</p>
<h2>What it does</h2>
<ul>
<li><strong>Exit IPs:</strong> it asks several lookups at once (including IPv4/IPv6 and WebRTC) and groups what they see as a direct exit or a proxy/split path.</li>
<li><strong>HTTPS latency:</strong> your browser opens a real HTTPS connection to about 40 services across AI, video, social, gaming, developer tools, and CDNs (for example ChatGPT, YouTube, Discord, GitHub, Steam, and Cloudflare). The first request is only connection setup; then it reuses the connection and shows the median. That is closer to what apps feel than ICMP ping.</li>
<li><strong>Related tools</strong> on the same site: EgressLens (which IP each site sees), IP Quality, Who Are You, ASN lookup, and streaming/AI unlock checks.</li>
<li><strong>CLI:</strong> you can run the same kind of HTTPS timing from a VPS, Linux box, or router:</li>
</ul>
<pre><code>curl -fsSL https://1ms.dog/i | sh
</code></pre>
<h2>Privacy</h2>
<p>Latency requests go straight from your browser to the services being tested. Results stay in the browser unless you share them.</p>
<ul>
<li>Site: <a href="https://1ms.dog">https://1ms.dog</a></li>
<li>Source: <a href="https://github.com/yt1988/1ms.dog">https://github.com/yt1988/1ms.dog</a></li>
</ul>
<p>If you try it, I am happy to answer questions in the comments.</p>
]]></content:encoded></item></channel></rss>