<?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[&quot;Run a quick DNS speed test&quot; they said… 🤔]]></title><description><![CDATA[<p>"Run a quick DNS speed test" they said… <img src="https://board.circlewithadot.net/assets/plugins/nodebb-plugin-emoji/emoji/android/1f914.png?v=28325c671da" class="not-responsive emoji emoji-android emoji--thinking_face" style="height:23px;width:auto;vertical-align:middle" title="🤔" alt="🤔" /></p><p>One click on dns-speed.tail-f[.]de and your browser helpfully fans out ~5,000 HTTPS handshakes to "random" Cisco Top 1M domains in ~30 seconds.</p><p>That randomness is doing a lot of work.</p><p>Across a handful of runs we saw clients touching:</p><p>- Government + defence: *.uscourts.gov, multiple .gov TLDs, and .mil hosts (incl. disa[.]mil, onr[.]navy[.]mil)<br />- Microsoft sovereign/GCC High endpoints (dodsuite, usgovcloudapi, etc.)<br />- Enterprise collaboration: 100+ Webex, Zoom infra, SharePoint/OneDrive tenants<br />- Identity surfaces: 130+ auth/login patterns, Okta/Auth0/Duo tenants<br />- Autodiscover for named orgs (useful for pre‑populating phish kits)<br />- ~150 banking domains, globally distributed</p><p>All from a page load. No content fetched, just "harmless" handshakes.</p><p>What's interesting isn't malice so much as side‑effects. A "neutral" performance test becomes:<br />- A spray of client IPs into sensitive identity and gov endpoints<br />- Noisy, hard‑to‑explain telemetry for defenders ("why is this workstation touching DISA?")<br />- Occasional redirects into less friendly corners of the web, courtesy of the long tail</p><p>The stated aim is realism (avoid vendor‑optimised test servers). In practice, you inherit the internet's entire distribution of good, bad, and broken—and push it through end‑user browsers.</p><p>It's a reminder that at scale, "just measuring" can look a lot like reconnaissance… or at least generate it for someone else.</p><p><a href="https://infosec.exchange/tags/dns" rel="tag">#<span>dns</span></a> <a href="https://infosec.exchange/tags/threatintel" rel="tag">#<span>threatintel</span></a> <a href="https://infosec.exchange/tags/threatintelligence" rel="tag">#<span>threatintelligence</span></a> <a href="https://infosec.exchange/tags/cybercrime" rel="tag">#<span>cybercrime</span></a> <a href="https://infosec.exchange/tags/cybersecurity" rel="tag">#<span>cybersecurity</span></a> <a href="https://infosec.exchange/tags/infosec" rel="tag">#<span>infosec</span></a> <a href="https://infosec.exchange/tags/infoblox" rel="tag">#<span>infoblox</span></a> <a href="https://infosec.exchange/tags/infobloxthreatintel" rel="tag">#<span>infobloxthreatintel</span></a></p>]]></description><link>https://board.circlewithadot.net/topic/8396e55a-3236-482f-9f53-770cd3b4c4a8/run-a-quick-dns-speed-test-they-said</link><generator>RSS for Node</generator><lastBuildDate>Fri, 15 May 2026 03:47:14 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/topic/8396e55a-3236-482f-9f53-770cd3b4c4a8.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 30 Apr 2026 16:09:58 GMT</pubDate><ttl>60</ttl></channel></rss>