Is CleanBrowsing down today?

DNS filter blocks a legitimate site

If a site you need gets blocked unexpectedly, the filter category it falls under might be too broad for your use case. Go to your dashboard, open the Filter Profile settings, and check which content categories are active. You can whitelist specific domains under ''Allow list'' — add the full domain, save the profile, and wait 1–2 minutes for the change to propagate. If the site still doesn''t load, flush your local DNS cache: on Windows run ''ipconfig /flushdns'', on macOS use ''sudo dscacheutil -flushcache''.

Custom DNS settings stopped working

This usually means your device or router reverted to the ISP''s default DNS servers. Check your network adapter settings and confirm the DNS addresses are still set to CleanBrowsing''s resolvers (185.228.168.9 and 185.228.169.9 for the free tier). On routers, some firmware updates reset DNS configuration — reapply the settings after any router update.

Dashboard login fails or page won''t load

- Clear browser cookies and cache, then try again in an incognito window

- Make sure you''re using the correct email — accounts are tied to a single address with no alias support

- If password reset email doesn''t arrive, check your spam folder and whitelist the sender domain

- Disable any browser extensions that interfere with forms before submitting credentials

Filtering works on Wi-Fi but not on mobile data

Mobile carriers assign their own DNS automatically, overriding your settings. To fix this, configure the DNS directly on the device level rather than on the router. On Android 9+ use the ''Private DNS'' option (Settings → Network → Advanced) and enter your CleanBrowsing hostname. On iOS, install a DNS profile via the dashboard''s device configuration section.

High latency after switching DNS servers

If pages load slower than before, the resolver closest to your location may not be responding optimally. Try switching between the IPv4 and IPv6 resolver addresses. Also check whether your router is set to ''relay'' DNS queries rather than forward them directly — relay mode adds unnecessary hops and increases response time noticeably.