1

SafeSearch option blocks Brave Search and Qwant

When the NextDNS SafeSearch option is enabled, some popular search engines aren’t supported (and thus get blocked), like Brave Search or Qwant, even though they already support SafeSearch.

If you could add support for them, it would make NextDNS a perfect DNS service. I really think so.

Good luck, your work is awesome. 😎

2 replies

null
    • Martheen
    • 2 wk ago
    • Reported - view

    I can immediately find the CNAME for Brave Search to enforce safe search, but where's in the Qwant site do they document this? I can only find third party forum talking about it

      • Hugo.10
      • 2 wk ago
      • Reported - view

       

      Brave offers an official way to force SafeSearch via DNS:

       

      'search.brave.com IN CNAME forcesafe.search.brave.com'

      This setting "locks" Brave Search in SafeSearch mode for the affected network.

      However, this CNAME must only apply to the main domain (search.brave.com), not to subdomains (e.g., cdn.search.brave.com), otherwise you risk SSL certificate issues.

       

      However, for Qwant, I haven't found any documentation confirming that the "forced SafeSearch" mode via DNS is still active.

      A forum indicates that Qwant was redirected to safeapi.qwant.com for SafeSearch, but that this domain is no longer functional.

Login to reply

Content aside

  • 1 Votes
  • 2 days agoLast active
  • 2Replies
  • 64Views
  • 2 Following