searxngRebrandZaclys/docs/user/public_instances.rst

36 KiB

Public Searx instances

Useful information

  • Up-to-date health report available on https://stats.searx.xyz<sup>(1)</sup>, for onion (tor) services: https://stats.searx.xyz/tor.html
  • Searx instances mailing list & subscription page.
  • Some of the Searx instances have a CAcert SSL certificate. You can install the missing root cert from here.
  • You can add your own Searx instance to this page by clicking here or by clicking on the "Edit" button in the top right corner (when logged in). A GitHub account is required to make changes.

<sup>(1)</sup> Note that most of the instances with a A+ grade in CSP column in this site are not fully functional - for example auto-completion may not work.

List of public Searx instances

Meta-searx instances

These are websites that source from other searx instances. These are useful if you can't decide which Searx instance to use:

Meta-searx instances

    • clearnet host
    • onion host
    • issuer
    • source selection method
    • extra privacy features
    • Neocities
    • n/a
    • Comodo (verification)
    • Redirects users directly to a random selection of any known running server after entering query. Requires Javascript. Changelog.
    • Excludes servers with user tracking and analytics or are proxied through Cloudflare.

Alive and running

NOTE: Public instances listed here may yield less accurate results as they have much higher traffic and consequently have a higher chance of being blocked by search providers such as Google, Qwant, Bing, Startpage, etc. Hosting your own instance or using an instance that isn't listed here may give you a more consistent search experience.

BEFORE EDITING: Please add your Searx instance by respecting the alphabetic order.

Running in exclusive private walled-gardens

These instances run in walled-gardens that exclude some segment of the general public (e.g. Tor users and users sharing IPs with many other users). Caution: privacy is also compromised on these sites due to exposure of cleartext traffic to a third party other than the website operator.

Running with an incorrect SSL certificate

Offline