NextDNS · home network device coverage
8 JUNE 2026 · window -24h
At a glance
- ⚠ YELLOW — 36.5% of queries from unidentified devices (57,439 of 157,211)
- 6 named device(s) accounting for 99,772 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__) |
57,439 | 36.5% |
| Apple TV Upstairs | 42,649 | 27.1% |
| Dan’s MacBook 14” Pro | 30,942 | 19.7% |
| iPhone 13 Pro | 12,584 | 8.0% |
| Audrey iMac M1 | 8,272 | 5.3% |
| Lounge TV | 3,614 | 2.3% |
| Dan’s M2 | 1,711 | 1.1% |
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