If your CleanBrowsing dashboard shows "No Data Available" or "DNS Inactive," your devices aren't sending DNS queries through CleanBrowsing yet. Here's how to fix it.
When your CleanBrowsing dashboard shows "No Data Available" or "DNS Inactive," it means CleanBrowsing hasn't received any DNS queries from your network or devices recently.
This typically means one of three things:
Confirm that your device or router is using CleanBrowsing DNS servers. The easiest way is to use terminal/command prompt:
nslookup cleanbrowsing.org
The "Server" line should show one of CleanBrowsing's DNS IPs (e.g., 185.228.168.168 for the Family filter).
dig cleanbrowsing.org
Check the ;; SERVER: line in the output. It should point to a CleanBrowsing IP.
If the DNS server shown is not a CleanBrowsing IP, your device isn't configured correctly. Visit the Setup Guide for step-by-step instructions.
For paid accounts, CleanBrowsing needs your public IP address registered in the dashboard to associate DNS queries with your account.
If your public IP changes frequently (common with residential ISPs), set up a dynamic IP updater to keep it current.
After making DNS changes, your device may still use cached entries from the previous DNS server. Flush the cache:
ipconfig /flushdns
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
sudo systemd-resolve --flush-caches
Also clear your browser's DNS cache — browsers maintain their own cache separate from the OS.
Verify that CleanBrowsing is actively filtering by testing a known-blocked domain:
nslookup pornhub.com
If CleanBrowsing is working correctly with the Family or Adult filter, this should return a blocked IP (like 0.0.0.0 or CleanBrowsing's block page IP). If it returns a real IP address, DNS filtering isn't active.
You can also use the command-line DNS tools guide for more detailed diagnostics.
If DNS is still showing as inactive after the steps above, check for these common issues:
Some ISPs and routers force their own DNS servers regardless of your settings. Check if your router has a DNS override enabled. See how to block DNS bypasses with firewall rules.
Antivirus or security software (like Avast or Norton) may redirect DNS queries to their own servers. See known services that conflict with CleanBrowsing.
If a VPN is active, it typically uses its own DNS servers, bypassing CleanBrowsing entirely. The same applies to browser-level encrypted DNS (DoH). See how to prevent filter bypass.
If your ISP uses CGNAT (common with T-Mobile and some cable providers), multiple customers share the same public IP. This can cause issues with IP-based account association. See understanding CGNAT.
Contact support@cleanbrowsing.org with your public IP address and a screenshot of your DNS settings. We'll help you get connected.
Step-by-step instructions for configuring CleanBrowsing on any device or router.
Keep your public IP current in CleanBrowsing when it changes.
Use dig, nslookup, and other CLI tools to diagnose DNS issues.