NextDNS · home network device coverage

3 JULY 2026 · window -24h

At a glance

• ⚠ YELLOW — 42.1% of queries from unidentified devices (34,168 of 81,140)
• 8 named device(s) accounting for 46,972 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

What to do next

1. Open the unidentified bucket — likely 1-2 devices, IoT or guest.
2. Name what you recognize; document the unknowable.

_{Generated by dare_nextdns_audit.py --check device_coverage}