NextDNS · home network device coverage
4 JUNE 2026 · window -24h
At a glance
- ⚠ YELLOW — 34.1% of queries from unidentified devices (62,658 of 183,825)
- 5 named device(s) accounting for 121,167 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__) |
62,658 | 34.1% |
| Apple TV Upstairs | 53,820 | 29.3% |
| Dan’s M2 | 28,494 | 15.5% |
| iPhone 13 Pro | 17,642 | 9.6% |
| Lounge TV | 10,858 | 5.9% |
| Audrey iMac M1 | 10,353 | 5.6% |
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