Fix SafeSearch That Does Not Enforce
SafeSearch Not Working can interrupt web access, policy enforcement, or evidence collection. Use this runbook to restore service, preserve logs, and prove the corrective action during security review. You have enabled all the entries required for Safe Searches, but you can still access inappropriate content through search engines. Follow the steps below to troubleshoot. Test your configuration once. All required entries must be enabled. Then test your HTTPS Inspection enabled or not. If it is not enabled, see How to configure HTTPS inspection Then check the SSL certificate in the browser. See Test certificate in Firefox. Removes the cache and restart the browser and test it again. You can see block template when “Text Analyzer” and default entry to block pornogrophy in policies and profiles are enabled.Capture useful evidence
Collect evidence before restarting services or changing policy. Keep screenshots, command output, and relevant SafeSquid logs with the incident ticket.[thread or request id] and a module name such as network:.
Record the affected user, source IP address, requested URL, timestamp, browser error, SafeSquid policy section changed, and verification result.
Next steps
- Use Find a complete connection log to trace a specific client transaction.
- Use Troubleshooting for the broader diagnostic checklist.
- Use Enforce SafeSearch to configure SafeSearch enforcement.