Why BlockSite blocked by Control D?
Control D filters at the DNS level: when a domain is blocked, your device never gets its address, so the browser can’t even start loading it. That works the same in every browser and app, which also means a browser can’t tell you why.
Updated November 2026. Menus move around between versions: if a label is a little different, look for the closest match.
Signs it’s Control D
- Errors like
DNS_PROBE_FINISHED_NXDOMAIN,ERR_NAME_NOT_RESOLVEDor “Hmm. We’re having trouble finding that site.” - Part of a page missing in every browser on the device, even with extensions off.
- It works on mobile data or another network, or with the Control D app paused.
Find what blocked it
- In the Control D dashboard, open Analytics → Activity Log. Logging must be enabled for the device or endpoint.
- Reload the broken page, then filter the log to blocked queries.
- The entry for the domain shows what blocked it: a filter (such as ads & trackers), a blocked service, one of your custom rules, or the profile’s default rule.
Allow it
- One domain: open your profile, go to Custom Rules and add the domain with the Bypass action. A rule for
example.comcovers its subdomains too. - A service you use: if a whole service is blocked under Services, set that service to bypass instead.
- A filter that keeps breaking things: lower its level or turn it off in the profile’s Filters.
- Changes apply within a minute or so. Browsers and operating systems cache DNS answers briefly, so restart the browser if the page still fails.
Good to know
- If your browser’s own “Secure DNS” / DNS-over-HTTPS setting is on, the browser may skip Control D entirely, and your rules won’t apply in that browser.
- Blocked domains may come back as “doesn’t exist” or as
0.0.0.0, depending on your profile’s settings.