{"id":8714,"date":"2026-06-03T12:29:24","date_gmt":"2026-06-03T17:29:24","guid":{"rendered":"https:\/\/www.dnsfilter.com\/blog\/the-ai-tools-your-dns-cant-see"},"modified":"2026-06-03T12:29:24","modified_gmt":"2026-06-03T17:29:24","slug":"the-ai-tools-your-dns-cant-see","status":"publish","type":"post","link":"https:\/\/ddi.mohflo.net\/index.php\/2026\/06\/03\/the-ai-tools-your-dns-cant-see\/","title":{"rendered":"The AI Tools Your DNS Can&#8217;t See"},"content":{"rendered":"<p><a href=\"https:\/\/www.dnsfilter.com\/features\/cybersight\" rel=\"noopener\" target=\"_blank\"><u><span>CyberSight<\/span><\/u><\/a><span>&#8216;s new AI Usage Report sees what DNS misses: Locally installed AI clients, locally-hosted models, and the active time employees spend in each.<!--more--><\/span><\/p>\n<h2>Shadow AI and the AI visibility gap<\/h2>\n<p><span>Ask most IT and security leaders which AI tools their employees use, and the honest answer is some version of &#8220;ChatGPT, and probably others.&#8221; The &#8220;probably others&#8221; is the problem, and it&#8217;s bigger than most teams realize.<\/span><\/p>\n<p><span>The &#8220;AI visibility&#8221; tools on the market today are mostly DNS-based. They count queries to known AI domains and call that a report. That works fine for the AI tools that look like websites. It misses everything else: Locally installed AI applications running directly on the laptop, downloadable LLM clients, IDE plugins that run inference on-device, desktop AI assistants. These tools generate little to no recognizable DNS traffic. To a DNS-based visibility tool, they don&#8217;t exist.<\/span><\/p>\n<p><span>That gap matters because the local-AI category is growing fast. The same employees who installed unsanctioned SaaS a decade ago are now running models on their own machines, downloading clients, and stitching together workflows that bypass the network (and your security protocols) entirely.<\/span><\/p>\n<p><span>And even the network-visible portion is climbing. Gen AI traffic on the DNSFilter network grew more than 6x in the past year, a 561% increase from roughly 432 million requests in April 2025 to over 2.86 billion in April 2026. That&#8217;s only what we can see at the DNS layer. The full picture is larger.<\/span><\/p>\n<p><span>Most organizations don&#8217;t have a tool for any of this. The dedicated AI governance vendors that do exist are priced for the Fortune 500 and require a separate agent on every endpoint. Everyone else has been left to guess.<\/span><\/p>\n<h2>What&#8217;s new in CyberSight<\/h2>\n<p><span>The new AI Usage Report inside CyberSight gives admins a purpose-built view of employee AI tool activity, built from telemetry the Roaming Client and browser extension already collect. No new agent. No new deployment. No new data collection.<\/span><\/p>\n<p><span><span><img data-recalc-dims=\"1\" fetchpriority=\"high\" decoding=\"async\" src=\"https:\/\/i0.wp.com\/ddi.mohflo.net\/wp-content\/uploads\/2026\/06\/the-ai-tools-your-dns-cant-see.png?resize=640%2C360&#038;ssl=1\" width=\"640\" height=\"360\" srcset=\"https:\/\/ddi.mohflo.net\/wp-content\/uploads\/2026\/06\/the-ai-tools-your-dns-cant-see-2.png 955w, https:\/\/ddi.mohflo.net\/wp-content\/uploads\/2026\/06\/the-ai-tools-your-dns-cant-see.png 1909w, https:\/\/ddi.mohflo.net\/wp-content\/uploads\/2026\/06\/the-ai-tools-your-dns-cant-see.png 2864w, https:\/\/ddi.mohflo.net\/wp-content\/uploads\/2026\/06\/the-ai-tools-your-dns-cant-see.png 3818w, https:\/\/ddi.mohflo.net\/wp-content\/uploads\/2026\/06\/the-ai-tools-your-dns-cant-see.png 4773w, https:\/\/ddi.mohflo.net\/wp-content\/uploads\/2026\/06\/the-ai-tools-your-dns-cant-see.png 5727w\" sizes=\"(max-width: 1909px) 100vw, 1909px\"><\/span><\/span><\/p>\n<p><span>When you open the report, you&#8217;ll see:<\/span><\/p>\n<ul>\n<li><strong><span>Detection of locally installed AI applications<\/span><\/strong><span>, including desktop clients (ChatGPT, Copilot) and locally-hosted model runtimes (Ollama, LM Studio). DNS-based visibility tools miss these entirely.<\/span><\/li>\n<li><strong><span>Executive summary cards<\/span><\/strong><span> showing total AI tool activity across your organization, distinct tools detected, and active users over the selected period.<\/span><\/li>\n<li><strong><span>Top AI applications by activity volume and active time spent<\/span><\/strong><span>, so you can see at a glance whether your environment is mostly ChatGPT, mostly Copilot, or quietly running a long list of tools you&#8217;ve never approved.<\/span><\/li>\n<li><strong><span>User and device drilldown<\/span><\/strong><span>, so when a tool shows up that shouldn&#8217;t be there, you can see exactly who&#8217;s using it and on which device.<\/span><\/li>\n<li><strong><span>CSV export<\/span><\/strong><span> for compliance reviews, board reporting, or handing a clean record to an auditor.<\/span><\/li>\n<\/ul>\n<p><span>It&#8217;s available now to all Pro and Enterprise CyberSight customers as part of the existing subscription.<\/span><\/p>\n<h2>Why this is more accurate than DNS-only reporting<\/h2>\n<p><span>Most &#8220;AI visibility&#8221; tools on the market today are really just DNS query counts with a new label. That sounds fine until you realize how noisy that data actually is. A meaningful share is browser prefetch, background tab activity, telemetry calls, and domains that resolve but are never actually visited.<\/span><\/p>\n<p><span>CyberSight&#8217;s browser extension captures actual URL and IP-level context, which means the AI Usage Report reflects what users actually opened, not what their browser happened to look up. For an audit, a compliance review, or a difficult conversation with an employee, that distinction matters.<\/span><\/p>\n<p><span>More importantly, CyberSight sees AI applications that DNS-based tools cannot. A growing share of AI usage happens on locally installed clients and on locally-hosted model runtimes like Ollama and LM Studio, which run inference directly on the endpoint and generate no recognizable traffic. DNS-based visibility tools are blind to this category by design. CyberSight isn&#8217;t, because the visibility comes from the endpoint itself, not the resolver.<\/span><\/p>\n<p><span>CyberSight also measures active time spent on AI tools, not just how many times a domain was queried. For a security team trying to understand real usage patterns, &#8220;an employee spent four hours in ChatGPT this week&#8221; is a different signal than &#8220;ChatGPT resolved 40 times.&#8221; <\/span><\/p>\n<h2>Why we built this and who it&#8217;s for<\/h2>\n<p><span>We built the AI Usage Report to provide visibility. It does <\/span><strong><span>not<\/span><\/strong><span> inspect prompt contents, read what employees are typing into AI tools, or proxy AI traffic. This is a deliberate choice. CyberSight&#8217;s job is to make behavior transparent, not to read over employees&#8217; shoulders.<\/span><\/p>\n<p><span>For organizations that need to block specific AI tools, those policies live where they&#8217;ve always lived in DNSFilter, at the filtering layer. The AI Usage Report makes it easier to know which tools you&#8217;d want to set policy on in the first place.<\/span><\/p>\n<p><span>We specifically built this for:<\/span><\/p>\n<ul>\n<li><strong><span>IT admins<\/span><\/strong><span> who need to answer &#8220;what AI is running in our environment?&#8221; without standing up a new tool. The report is filterable by user, device, and time range, so the answer takes minutes instead of weeks.<\/span><\/li>\n<li><strong><span>MSPs<\/span><\/strong><span> who want a clean, exportable artifact to share with clients.<\/span><\/li>\n<li><strong><span>Security teams and CISOs<\/span><\/strong><span> preparing for board questions, AI governance committees, or insurance renewals. The CSV export gives you a defensible record of what was running, when, and on which endpoints.<\/span><\/li>\n<li><strong><span>SMBs<\/span><\/strong><span> that have heard the phrase &#8220;shadow AI&#8221; in a webinar and want to know if it applies to them. The report answers that question the first day you open it.<\/span><\/li>\n<\/ul>\n<h2>Getting started<\/h2>\n<p><span>The AI Usage Report is available now for Pro and Enterprise customers. Just <\/span><a href=\"https:\/\/app.dnsfilter.com\/\" rel=\"noopener\" target=\"_blank\"><u><span>log in<\/span><\/u><\/a><span> and <\/span><a href=\"https:\/\/app.dnsfilter.com\/cybersight\/ai-usage\" rel=\"noopener\" target=\"_blank\"><u><span>click here<\/span><\/u><\/a><span> to see it.<\/span><\/p>\n<p><span>Not a customer yet? <\/span><a href=\"https:\/\/explore.dnsfilter.com\/free-trial\" rel=\"noopener\" target=\"_blank\"><u><span>Try it for free today<\/span><\/u><\/a><span>.<\/span><\/p>\n<p><a href=\"https:\/\/www.dnsfilter.com\/blog\/the-ai-tools-your-dns-cant-see\">Source<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>CyberSight&#8216;s new AI Usage Report sees what DNS misses: Locally<\/p>\n","protected":false},"author":8,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[4244],"tags":[4245],"class_list":["post-8714","post","type-post","status-publish","format-standard","hentry","category-dnsfilter-community","tag-dnsfilter-community"],"featured_image_urls":{"full":"","thumbnail":"","medium":"","medium_large":"","large":"","1536x1536":"","2048x2048":"","chromenews-featured":"","chromenews-large":"","chromenews-medium":""},"author_info":{"display_name":"DNSFilter","author_link":"https:\/\/ddi.mohflo.net\/index.php\/author\/dnsfilter\/"},"category_info":"<a href=\"https:\/\/ddi.mohflo.net\/index.php\/category\/dnsfilter-community\/\" rel=\"category tag\">DNSFilter Community<\/a>","tag_info":"DNSFilter Community","comment_count":"0","jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts\/8714","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/comments?post=8714"}],"version-history":[{"count":0,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/posts\/8714\/revisions"}],"wp:attachment":[{"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/media?parent=8714"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/categories?post=8714"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ddi.mohflo.net\/index.php\/wp-json\/wp\/v2\/tags?post=8714"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}