Description of the issue: I was just checking out Brave Search and I searched 4k and p*rnhub website was in the results even do I had the safe search set to strict. This is the same problem on DuckDuckGo. I hope this will be fixed I don’t want to see adult content because I’m really young and I shouldn’t see it
Brave Version: 1.26.67 Chromium: 91.0.4472.114
Operating System: Windows
i have found even the free filters work very well
check it out.
I can´t reproduce it, I searched “4K” and even with Safe Search set at Off there are no porn results of any kind in links or images.
You don´t have to pay for this, go to brave://settings/security in Advanced and pick “Use Secure DNS”, with “Customised” and you will see a drop down menu of various DNS providers, one of them is CleanBrowsing (Family Filter), the same company you mention but for free, it already comes with Brave.
oh good call @yubi!
i should have mentioned that the setup is super simple, just select the CleanBrowsing option in the DNS provider list.
Well when i search 4K now there’s no porn results. Idk why but it showed some
@anon23769284,
Search is constantly being adjusted and fine tuned – there’s a chance there was some special circumstance that allowed for those initial results but was subsequently resolved, so now they no longer show.
I have tried Adguard family and cleanbrowsing family and the new cloudflare for families DNS and none of them successfully lock brave search into safe mode.
Click on images search tab and the smut rolls right in.
Please fix this.
I agree. We need a way to lock in the safe search feature so this can be recommended to others (like youth).
This is totally not supported or official, as far as I can tell, but you can create a “search[.]brave[.]com” DNS zone on your local DNS server and then create either a CNAME record to safesearch[.]brave[.]com, or create A records for the IP addresses that safesearch[.]brave[.]com currently resolves to.
Eg:
local zone search[.]brave[.]com
_ CNAME safesearch[.]brave[.]com
or:
local zone search[.]brave[.]com
_ A 108[.]138[.]246[.]75
_ A 108[.]138[.]246[.]114
_ A 108[.]138[.]246[.]94
_ A 108[.]138[.]246[.]5
So far, this hack seems to work for our school district in testing.
(FQDNs and IPs defanged due to new user posting limitations.)
My last comment got ate by the spam filter, so here goes:
This is totally not supported or official, as far as I can tell, but you can create a “search[.]brave[.]com” DNS zone on your local DNS server and then create either a CNAME record to safesearch[.]brave[.]com, or create A records for the IP addresses that safesearch[.]brave[.]com currently resolves to.
Eg:
local zone search[.]brave[.]com
_ CNAME safesearch[.]brave[.]com
or:
local zone search[.]brave[.]com
_ A 108[.]138[.]246[.]75
_ A 108[.]138[.]246[.]114
_ A 108[.]138[.]246[.]94
_ A 108[.]138[.]246[.]5
So far, this hack seems to work for our school district in testing.
(FQDNs and IPS defanged due to new user posting limitations.)
That safesearch.brave.com domain didn’t exists before I started this thread here because I did mention in theory a domain like this should exists just like duckduckgo.com provides safe.duckduckgo.com.
It still doesn’t work I think because I can just change the strictness settings. Okay actually I just tried changing it it while typing this. It actually works! 
even though you can change the options.
You can change the safe search settings on the page, but it does not seem to have an actual effect of turning safe search off.
Again, as far as I know, this is totally unsupported by Brave and is firmly in “workaround” territory, but it’s better than having to block Brave Search altogether (eg, to meet CIPA compliance).
Oh, and people might notice that Image Search is broken after applying this workaround. To fix it, see my addendum on my blog post about this: https://absent.org/2022/06/22/force-brave-safe-search.html
I tried it and it doesn’t work …
This solves the problem for me. I block search.brave.com and leave safesearch.brave.com opened. Perfect solution, thank you.
I wish we could get moderatesearch.brave.com
//////////////////////////////////////
For that matter I do wish that search.brave.com just followed in line with other search engines and respected DNS family safe settings like Google and the rest do.
Have you found that safesearch.brave.com is functioning as well as the “safe search” options from Google & Bing?
We run FreeFiltering.org - a free internet filtering service for home wi-fi, based on traditional Christian values. We enable our users to enforce the “safe search” modes from Google, Bing, DuckDuckGo, & Yandex presently. When this mode is turned on by our users, we attempt to block access to all other search engines that we’re aware of. As of now, we are blocking access to search.brave.com when our users have our “safe search” mode enabled.
We would consider adding “safesearch.brave.com” to our list of search engines we allow access to when our “safe search” is enabled, if we feel like it’s working effectively at preventing porn result from showing in the search results pages.
Thoughts? Thanks!
It seems to work great for me.
If the ssl certificate would be instead of safesearch.brave.com and search.brave.com a wildcard like duckduckgo does (so it’ll should be *.brave.com) it will solve lots of problems when people try to redirect forced from one to other subdomain.
DuckDuckGo example:
Both same ssl certificate
It looks like this problem is still appearing for me. I was searching for “office hours” then I typed “office hours trans” (I was trying to write “translation,” but I just typed “trans” and hit enter), and the search result contained some adult content, even though I was setting the safe search to strict. Here is an image for that:
Is it possible to move it on a google way? I mean, using a cname. In this case we cannot interchange the safe search and the usual ones, because they have no a wildcard or a common SSL certificate.
Instead of using a *.brave.com ssl certificate
