Searx#SearXNG fork

{{Short description|Metasearch engine}}{{For|the currently maintained version of SearX|SearXNG}}{{Infobox software

| name = Searx

| logo = Logo searx a.png

| logo alt = Image of Searx logo

| screenshot = Screenshot-2017-8-31 searx me.png

| screenshot alt = Screenshot of searx.me web interface

| caption = Searx web interface

| developer = Adam Tauber (alias asciimoo){{cite web|url=https://github.com/asciimoo |title=asciimoo (Adam Tauber) |website=GitHub}}

| released = {{start date and age|2014|01|22}}{{cite web|url=https://github.com/searx/searx|title=searx: A privacy-respecting, hackable metasearch engine |first=Adam|last=Tauber|via=PyPI}}

| latest release version = {{wikidata|property|reference|edit|P348}}

| latest release date = {{Start date and age|{{wikidata|qualifier|P348|P577}}|df=no}}

| repo = {{URL|https://github.com/searx/searx}} (archived)

| programming language = Python

| replaced_by = SearXNG

| genre = Metasearch engine

| license = AGPL-3.0-or-later

| website = {{URL|https://searx.space/}} (List of Searx instances; now lists SearXNG instances)

}}

Searx ({{IPAc-en|s|ɜːr|k|s}}; stylized as searX) is a discontinued free and open-source metasearch engine,{{cite web |url=http://www.linux-magazine.com/Issues/2017/194/Charly-s-Column-Searx |title=Peppered with Hits » Linux Magazine |last=Kühnast |first=Charly |website=Linux Magazine |language=en-US |access-date=2017-08-31}} available under the GNU Affero General Public License version 3, with the aim of protecting the privacy of its users.{{cite web|url=https://nakedsecurity.sophos.com/2017/08/10/self-hosted-search-option-is-a-new-approach-to-bursting-the-filter-bubble/|title=Self-hosted search option is a new approach to bursting the filter bubble|last=Bradbury|first=Danny|date=August 10, 2017|website=Naked Security|archive-url=https://web.archive.org/web/20170904154549/https://nakedsecurity.sophos.com/2017/08/10/self-hosted-search-option-is-a-new-approach-to-bursting-the-filter-bubble/|archive-date=September 4, 2017|url-status=live|access-date=August 30, 2017}}{{cite web|url=https://www.maketecheasier.com/best-search-engine-for-privacy/|title=What Is the Best Search Engine for Privacy?|last=Zak|first=Robert|date=April 3, 2017|work=Make Tech Easier|archive-url=https://web.archive.org/web/20180703190837/https://www.maketecheasier.com/best-search-engine-for-privacy/|archive-date=July 3, 2018|url-status=live|access-date=August 30, 2017}}{{cite web|url=http://tuxdiary.com/2014/12/22/searx/|title=Searx: self-hosted web metasearch engine|last=Sonmez|first=John|date=December 22, 2014|website=Tuxdiary|access-date=2017-08-31|archive-date=2017-07-07|archive-url=https://web.archive.org/web/20170707153307/http://tuxdiary.com/2014/12/22/searx/|url-status=dead}} To this end, Searx does not share users' IP addresses or search history with the search engines from which it gathers results. Tracking cookies served by the search engines are blocked, preventing user-profiling-based results modification.{{cite news |url=http://acc.cv.ua/svit/25296-yak-zakhistiti-svoji-dani-v-interneti-11-korisnikh-dodatkiv |title=Як захистити свої дані в інтернеті: 11 корисних додатків |last=administrator |first=Acc |work=Новини АСС |access-date=2017-08-31 |language=uk-ua}}{{cite news |url=http://t3n.de/news/searx-konfigurierbare-suchmaschine-729236/ |title=Searx: Die konfigurierbare Suchmaschine, die deine Privatsphäre respektiert |work=t3n News |access-date=2017-08-31 |language=de}} By default, Searx queries are submitted via HTTP POST,{{efn|Except on Chromium-based web browsers, where HTTP GET requests are used instead.}} to prevent users' query keywords from appearing in webserver logs. Searx was inspired by the Seeks project,{{cite web |url=https://github.com/searx/searx/blob/master/searx/templates/__common__/about.html |title=about.html |website=GitHub |language=en |access-date=2020-05-23}} though it does not implement Seeks' peer-to-peer user-sourced results ranking.

Each search result is given as a direct link to the respective site, rather than a tracked redirect link as used by Google. In addition, when available, these direct links are accompanied by cached and/or proxied links that allow viewing results pages without actually visiting the sites in question. The cached links point to saved versions of a page on the Wayback Machine, while the proxied links allow viewing the current live page via a Searx-based web proxy. In addition to the general search, the engine also features tabs to search within specific domains: files, images, Information technology, maps, music, news, science, social media, and videos.{{cite news |url=https://www.techspot.com/guides/1292-web-security-anonymizer-primer/ |title=A Primer on Staying Secure and Anonymous on the Dark Web |work=TechSpot |access-date=2017-08-30 |language=en-us}}{{cite news |url=https://www.golem.de/news/searx-0-10-0-die-eigene-suchmaschine-auf-einem-raspberry-pi-1609-123094.html |title=Searx 0.10.0: Die eigene Suchmaschine auf einem Raspberry Pi |trans-title=Searx 0.10.0: Your own search engine on a Raspberry Pi |author=Von Jan Weisensee |access-date=2017-08-31 |language=de-DE |archive-url=https://web.archive.org/web/20200807015803/https://www.golem.de/news/searx-0-10-0-die-eigene-suchmaschine-auf-einem-raspberry-pi-1609-123094.html |archive-date=2020-08-07 |date=2016-09-07 |website=golem.de}}

Users can run private instances of Searx on their own computer, but there are also many public, user-run, Searx instances,{{cite web |url=https://searx.space/ |title=Public Searx instances |website=searx.space}} some of which are available as Tor hidden services. Meta-Searx instances can also be used to forward the search query to a random public instance. A public API is available for Searx,{{cite web |url=https://searx.github.io/searx/dev/search_api.html |title=Search API — searx 0.12.0 documentation |website=searx.github.io |access-date=2017-08-31}}{{cite web|last=Seitz|first=Justin|date=2017-04-18|title=Building a Keyword Monitoring Pipeline with Python, Pastebin and Searx {{!}} Automating OSINT Blog|url=http://www.automatingosint.com/blog/2017/04/building-a-keyword-monitoring-pipeline-with-python-pastebin-and-searx/|access-date=2017-08-31|website=www.automatingosint.com|language=en-US|archive-date=2017-09-16|archive-url=https://web.archive.org/web/20170916125412/http://www.automatingosint.com/blog/2017/04/building-a-keyword-monitoring-pipeline-with-python-pastebin-and-searx/|url-status=dead}} as well as Firefox search provider plugins.{{cite web |url=https://addons.mozilla.org/en-US/firefox/search/?q=searx |title=Search results for "searx" – Add-ons for Firefox (en-US) |website=addons.mozilla.org |access-date=2019-07-15}}

As of 7 September 2023, the Searx GitHub repository has been archived, stating that SearX is no longer maintained.{{Cite web |date=2023-09-07 |title=GitHub - searx/searx: Privacy-respecting metasearch engine |url=https://github.com/searx/searx |access-date=2023-09-17 |website=GitHub}} The SearXNG repository remains open.

Search engines and other settings

Across all categories, Searx can fetch search results from about 82 different engines. This includes major search engines and site-specific searches like Bing, Google, Reddit, Wikipedia, Yahoo, and Yandex.{{cite web|url=https://github.com/searx/searx |title=searx: Privacy-respecting metasearch engine |last=Tauber |first=Adam |website=GitHub |date=2017-08-30 |access-date=2017-08-31}} The engines used for each search category can be set via a "preferences" interface, and these settings will be saved in a cookie in the user's web browser, rather than on the server side, since for privacy reasons, Searx does not implement a user login model. Other settings such as the search interface language and the search results language (over 20 languages are available) can be set the same way.{{cite web |url=https://searx.me/preferences |title=preferences - searx.me |website=searx.me |access-date=2017-09-25 |archive-url=https://web.archive.org/web/20180320084245/https://searx.me/preferences |archive-date=2018-03-20 |url-status=dead}}

In addition to the preferences cookie, it is possible on each query to modify the engines used, search categories selected, and/or languages to search in by specifying one or more of the following textual search operators before the search keywords.{{cite web |url=https://searx.github.io/searx/user/search_syntax.html |title=Search syntax — searx 0.12.0 documentation |website=searx.github.io |access-date=2017-08-30}}

  • !category — Search the specified category instead of the default ones.
  • ?category — Search the specified category in addition to the default ones.
  • !engine — Search the specified engine instead of the default ones.
  • ?engine — Search the specified engine in addition to the default ones.
  • :language — Search for results in the specified language instead of the default one.

The ! and ? operators can be specified more than once to select multiple categories or engines, for example !google !deviantart ?images :japanese cow.

Instances

Any user may run their own instance of Searx,{{cite news |url=https://www.loganmarchione.com/2015/10/my-searx-instance/ |title=My Searx instance - Logan Marchione |date=2015-10-18 |work=Logan Marchione |access-date=2017-08-31 |language=en-US |archive-date=2018-12-08 |archive-url=https://web.archive.org/web/20181208035751/https://www.loganmarchione.com/2015/10/my-searx-instance/ |url-status=dead }} which can be done to maximize privacy, avoid congestion on public instances, preserve customized settings (even if browser cookies are cleared), allow auditing of the source code being run, and more.{{cite web |url=https://searx.github.io/searx/user/own-instance.html |title=Why use a private instance? — searx 0.12.0 documentation |website=searx.github.io |access-date=2017-08-31}} Users may include their Searx instances on the editable list of all public instances, or keep them private. It is also possible to add custom search engines to a self-hosted instance that are not available on the public instances.{{cite web |url=https://searx.github.io/searx/dev/engine_overview.html#general-engine-configuration |title=Engine overview — searx 0.12.0 documentation |website=searx.github.io |access-date=2017-08-31}}

In 2019, Google has begun to block some self-hosted instances. This included some of the IP addresses used by searx.me from queries that result in a google (unexpected crash: CAPTCHA required) error.{{Cite web|title=Google Captcha|url=https://github.com/searx/searx/issues/729|date=2016-10-12|website=GitHub issues|access-date=2020-05-23}} In response, some instances have been modified to silently skip trying to search with Google even when it's the only engine specified.{{cite web |url=https://searx.info/?q=!google%20cow&categories=none&language=en-US |title=!google cow - searx |website=searx.info |quote=Sorry! we didn't find any results. Please use another query or search in more categories. |access-date=2019-07-15 }}{{Dead link|date=August 2023 |bot=InternetArchiveBot |fix-attempted=yes }}{{cite web |url=https://search.disroot.org/?q=!google%20cow&categories=none&language=en-US |title=!google cow - searx |website=search.disroot.org |quote=Sorry! we didn't find any results. Please use another query or search in more categories. |access-date=2019-07-15}}

SearXNG fork

File:SearXNG-wordmark.svg{{Main|SearXNG}}

In the middle of 2021, some contributors of SearX forked the repo to SearXNG with a view to provide faster debugging and fixes of engine errors.{{Cite web |last=master |first=web |date=2022-09-08 |title=SearXNG: A Metasearch Engine With Great Results |url=https://greycoder.com/__trashed-2/ |access-date=2023-08-19 |website=GreyCoder |language=en-US}} SearXNG is for users that need a faster upstream development time with fewer bugs.{{Citation |title=searx/searx |date=2023-08-19 |url=https://github.com/searx/searx |access-date=2023-08-19 |publisher=Searx engine}}{{cite web |title=searxng/searxng |date=2023-08-19 |url=https://github.com/searxng/searxng |access-date=2023-09-19 |website=GitHub}} User theme, engine reliability and anonymous metrics are the most notable changes in SearXNG.

See also

Footnotes

{{notelist}}

References

{{reflist}}