Every parent in our community uses Kagi search and has their respective kids using it. We all use porn blocking through DNS settings. Kagi currently doesn't respect safe search settings configured at the DNS level (e.g., NextDNS, ControlD), unlike all other search engines.
Expected behavior: When safe search is enforced via DNS provider, Kagi should honor these settings.
Current behavior: Kagi bypasses DNS-level safe search controls.
Impact: This prevents network-level content filtering from working effectively with Kagi.
Technical details:
Search engines that support DNS-level safe search provide special safe search subdomains that DNS providers redirect to:
Google: forcesafesearch.google.com
Bing: strict.bing.com
YouTube: restrict.youtube.com or restrictmoderate.youtube.com
Brave: safe.search.brave.com
DuckDuckGo: safe.duckduckgo.com
Parents, schools, and organizations using DNS filtering services (NextDNS, ControlD, CleanBrowsing, etc.) would automatically get safe search enforcement on Kagi without any additional configuration, and with users not being able to disable it. Users who have already configured safe search enforcement at the DNS level expect it to work across all search engines on their network.