Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Squidguard does not enforce Google Safe Search

    Scheduled Pinned Locked Moved Cache/Proxy
    10 Posts 2 Posters 2.6k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • r0utevv3R
      r0utevv3
      last edited by

      How can I enforce google safe search? I have cheked the option that enable it in squidgard and it doesn't work. In openwrt it was as easy as modify the etc/host and redirect google.com to forcesafesearch.google.com, but now that URL doesn't even exist. Thanks in advance

      It's not a bug, it's an undocumented feature

      1 Reply Last reply Reply Quote 0
      • A
        aGeekhere
        last edited by

        Here
        https://forum.pfsense.org/index.php?topic=112335.0

        Never Fear, A Geek is Here!

        1 Reply Last reply Reply Quote 0
        • r0utevv3R
          r0utevv3
          last edited by

          Yes, but I don't know if it's me (my computer, my network?), but 216.239.38.120 is not google safe search anymore, just google.com

          It's not a bug, it's an undocumented feature

          1 Reply Last reply Reply Quote 0
          • A
            aGeekhere
            last edited by

            If you ping forcesafesearch.google.com you get 216.239.38.120.
            Google safe search has not changed and is working.

            Never Fear, A Geek is Here!

            1 Reply Last reply Reply Quote 0
            • r0utevv3R
              r0utevv3
              last edited by

              It's strange, because I get this with forcesafesearch.google.com :

              and with 216.239.38.120. just redirects me to a normal google

              It's not a bug, it's an undocumented feature

              1 Reply Last reply Reply Quote 0
              • A
                aGeekhere
                last edited by

                It's strange, because I get this with forcesafesearch.google.com
                and with 216.239.38.120. just redirects me to a normal google

                You have to first make pfsense your dns server and create a host override for each google domain to 216.239.38.120, follow the first part of the guide and you should have it working in no time.

                Never Fear, A Geek is Here!

                1 Reply Last reply Reply Quote 0
                • r0utevv3R
                  r0utevv3
                  last edited by

                  Yes, I am going to make that, but what I say is that if I go to my browser, and in the hyperlink section I put 216.239.38.120 and type enter, it redirects me to google.com, and does not activate google safe search (I still can see adult content). And that happens in all the LANs I have checked. I think google change the ip or somethinkg like that. But I can't find the new one

                  It's not a bug, it's an undocumented feature

                  1 Reply Last reply Reply Quote 0
                  • A
                    aGeekhere
                    last edited by

                    I do not think you can just use that address in the browser, it is ment for router DNS redirecting.

                    Never Fear, A Geek is Here!

                    1 Reply Last reply Reply Quote 0
                    • r0utevv3R
                      r0utevv3
                      last edited by

                      I am going to check that. But in the past I was capable to use that ip in the browser (Google safe search was activated alone) and then I did something with openwrt to redirect all google domains to 216.239.38.120. After all router DNS redirecting simply assigns a domain name to a different ip address. So that ip address should be a webpage with safe search enabled by default, isn't?

                      It's not a bug, it's an undocumented feature

                      1 Reply Last reply Reply Quote 0
                      • r0utevv3R
                        r0utevv3
                        last edited by

                        Your method doesn't work for me. I have already follow your instructions and still nothing. Please help!

                        It's not a bug, it's an undocumented feature

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.