NextDNS · home network device coverage
3 JUNE 2026 · window -24h
At a glance
- ⚠ YELLOW — 37.4% of queries from unidentified devices (68,600 of 183,476)
- 5 named device(s) accounting for 114,876 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__) |
68,600 | 37.4% |
| Apple TV Upstairs | 58,378 | 31.8% |
| Dan’s M2 | 33,341 | 18.2% |
| Audrey iMac M1 | 10,401 | 5.7% |
| iPhone 13 Pro | 9,447 | 5.1% |
| Lounge TV | 3,309 | 1.8% |
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