NextDNS · home network device coverage
26 JUNE 2026 · window -24h
At a glance
- ⚠ YELLOW — 46.2% of queries from unidentified devices (51,846 of 112,285)
- 9 named device(s) accounting for 60,439 queries
- Threshold: ≤5% green · 5-20% amber · >20% red
Why this matters
Unidentified traffic is the home-network equivalent of an unaccounted-for log line — something is making DNS queries and we can’t tell which device it is. Most often it’s: a router doing recursive resolution (forward to NextDNS but don’t tag with device id), an IoT device NextDNS can’t fingerprint, or a device that’s deliberately or accidentally bypassing the profile (guest Wi-Fi, plain-DNS escape, VPN flip).
The fix is one of: name the device in the NextDNS dashboard so it stops rolling up under UNIDENTIFIED, or configure the router to forward per-client DNS rather than recursing centrally.
Device breakdown
| Device | Queries | Share |
|---|---|---|
unidentified (__UNIDENTIFIED__) |
51,846 | 46.2% |
| Dan’s MacBook 14” Pro | 23,964 | 21.3% |
| Audrey iMac M1 | 12,961 | 11.5% |
| iPhone 13 Pro | 7,533 | 6.7% |
| iphone-13-pro-max | 5,823 | 5.2% |
| Apple TV Upstairs | 5,750 | 5.1% |
| Lounge TV | 4,297 | 3.8% |
| immich | 63 | 0.1% |
| Dan’s M2 | 39 | 0.0% |
| dans-macbook-14–pro | 9 | 0.0% |
What to do next
- Open the unidentified bucket — likely 1-2 devices, IoT or guest.
- Name what you recognize; document the unknowable.
Generated by dare_nextdns_audit.py --check device_coverage
Source:
dare_nextdns_device_coverage_2026-06-26.md · Rendered Built with — component scripts
seo_render_html.py— wraps the source.mdin the dash.gf.cx design language (+anchor_enricher.pyfor inline-link promotion & rollover thumbnails)dare_dev_reports_publish.py— bundles the day’s reports into the catalog and ships to dash.gf.cx/reports