2

No safe search enforcement when using brave search.

When having safe search toggle enabled. Brave search is not getting resolved instead of being redirected to "forcesafe.search.brave.com". 

Possible solution/hint for solving can be found here: https://search.brave.com/help/safesearch

I found a github issue as well: https://github.com/nextdns/metadata/pull/1021#issuecomment-1185021541
 

6 replies

null
    • JPP
    • 2 wk ago
    • Reported - view

    Hello! I experienced this issue while trying out NextDNS and found a work around. I added search.brave.com and brave.com in the allow list tab. Chances are, brave.com is only necessary since it already accounts for subdomains but I haven't tested as of yet. Also be sure to purge the DNS cache (in Windows it is

    ipconfig/flushdns

    so you don't have to wait out the 5 minute cache of the 0.0.0.0 block. Hope this helps!
    Edit: This work around does not automatically redirect to safe.search.brave.com as of yet.

      • goodbaad
      • 2 wk ago
      • Reported - view

       Yeah this doesn't solve it then. I need a redirect to brave safe search

      • JPP
      • 2 wk ago
      • Reported - view

      I know that CleanBrowsing Adult, DNSforFamily, and AdGuard already enforce the redirect. I hope NextDNS.io can eventually do the same.

    • goodbaad
    • 2 wk ago
    • Reported - view

    Found the way the Team over at AdGuard does it: https://raw.githubusercontent.com/AdguardTeam/HostlistsRegistry/refs/heads/main/assets/engines_safe_search.txt

    • JPP
    • 4 days ago
    • Reported - view

    Brave SafeSearch appears to be working with NextDNS at the DNS level. Visits to search.brave.com are automatically being redirected to safe.search.brave.com. I disabled the whitelist workaround, cleared DNS cache with ipconfig /flushdns and it's working good so far.

      • goodbaad
      • 4 days ago
      • Reported - view

      finally

Login to reply

Content aside

  • 2 Votes
  • 4 days agoLast active
  • 6Replies
  • 74Views
  • 2 Following