Browse Policies & Filtering
- Application categories (Zero Trust app management)
- Active Directory group policies
- Content categories
- Custom block pages
- Don't mix DNS providers
- Prevent DNS bypass
- Safe Search explained
- Safe Search supported search engines
- Security categories
- Working with policies
- Working with allow and block lists
- YouTube Restricted Mode explained
Safe Search supported search engines
Which search engines ScoutDNS can enforce Safe Search on (Google and Bing), and what happens to other engines when Forced mode is enabled.
ScoutDNS Safe Search works by redirecting DNS queries for a search engine’s normal endpoint to its safe variant. That mechanism only works for search engines that publish a separate “safe” DNS endpoint.
Supported today
| Search engine | DNS-based Safe Search |
|---|---|
| Supported | |
| Bing | Supported |
Other engines (Yahoo, DuckDuckGo, Brave, Startpage, etc.) implement Safe Search via URL parameters rather than separate DNS endpoints, so DNS-layer filtering can’t enforce their safe mode.
What happens in Forced mode
When Safe Search is set to Forced on a policy:
- Queries to Google and Bing get redirected to the safe variants.
- All other search engines are blocked entirely.
If a specific non-Google/Bing engine is required (or some app uses one for its in-app search), add the engine’s domain to a custom allow list attached to the policy.
What happens in On mode
Same Google and Bing redirection as Forced, but other search engines remain accessible. Useful when you want safer Google/Bing results without cutting off alternatives.
Adding support over time
As more search engines publish DNS-based Safe Search endpoints, ScoutDNS will add them to this list. If your preferred engine isn’t here today, the only DNS-layer path is via custom allow/block lists, not Safe Search.
Related
- Safe Search explained, modes and use cases
- Working with allow and block lists, allowing specific engines under Forced mode
- Working with policies