0

Improve Tracker Insights: Tell us what a domain actually does, not who owns it

Subject: Feature Request: Make "Tracker Insights" actually useful for troubleshooting (Functional context instead of company bios)

 

Hi NextDNS Team,

 

I am writing this because the current "Tracker Insights" feature (the little "eye" icon in the logs) is fundamentally useless for real-world troubleshooting. 

 

Right now, when a service or website breaks (e.g., Xbox party chat audio, app logins, or retail site images) and we look at the logs to find the culprit, clicking on "Tracker Insights" only gives us generic company bios. 

 

For example, on 'www.gstatic.com' or various Microsoft domains, it says something like: "Owned by Google. Google LLC is an American multinational technology company..." or "Dangerously prevalent (tracks 38.35% of web traffic)". 

 

Frankly, as a user, I do not care who owns the server or what year the company was founded. That is completely useless pseudo-information when I am trying to fix a broken device. 

 

What we actually need is FUNCTIONAL CONTEXT. 

 

When we click on a domain in the log, the AI / Insights should tell us:

1. WHAT does this specific domain actually do under the hood? (e.g., "This domain is used for Xbox Live authentication and headset party chat audio" or "This domain delivers static image assets for Scandinavian retail sites").

2. WHAT will break if we block it? (e.g., "If blocked, your wireless Xbox headset will have no sound" or "If blocked, certain retail websites will fail to load images").

3. Is it a safe bypass? (e.g., "This is core infrastructure required for functionality, not a telemetry tracker").

 

Even if you don't run this analysis on every single query in real-time (to save compute power), you should allow us to click a "Query Domain Function" button to trigger a quick, on-demand AI lookup of that specific subdomain’s known functions.

 

Please stop giving us lazy Wikipedia summaries about big tech companies. We know who Google and Microsoft are. Instead, give us the actual, functional purpose of the subdomains so we can maintain our whitelists quickly and efficiently without breaking our home setups.

 

Thank you.

Reply

null

Content aside

  • yesterdayLast active
  • 15Views
  • 1 Following