Standard DNS filtering sees traffic from your public IP, not individual devices. This guide covers methods to monitor which devices are making which requests on your network.
DNS filtering services like CleanBrowsing operate at the network level — they only see requests coming from your public IP address, not from individual devices behind your router. This means the CleanBrowsing dashboard shows aggregate activity for your entire network.
To see which specific device (laptop, phone, tablet, smart TV) is making which requests, you need a local solution that sits between your devices and the upstream DNS resolver.
Pi-hole is a popular open-source local DNS resolver that provides per-device visibility while maintaining content filtering.
Devices send DNS queries to Pi-hole running on your local network. Pi-hole logs the device name/IP for each request, then forwards the query to CleanBrowsing for filtering. You get per-device visibility and content filtering.
185.228.168.168)Many advanced routers include built-in DNS logging that shows which devices are accessing which domains.
192.168.1.1 or 192.168.0.1)If your stock router firmware doesn't support DNS logging, consider custom firmware like OpenWRT or DD-WRT for enhanced logging capabilities.
For enterprise or advanced users, dedicated monitoring software provides the most granular per-device insights:
These tools require a dedicated machine or virtual server and route all traffic through the monitoring appliance.
If monitoring isn't your goal but per-device control is, consider configuring CleanBrowsing directly on each device rather than at the router level:
Manage filters and retrieve activity logs programmatically.
Answers to frequently asked questions about CleanBrowsing.
Understanding DNS monitoring and logging for your network.