Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacyΒ© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
DorXNG β€” Next Generation DorX. Built by Dorks, for Dorks. πŸ€“ | Kitploit
Tools/GitHubGitHub/researchanddestroy/dorxng
OSINT (Open Source Intelligence)ReconnaissanceDNS & Subdomain EnumerationInformation GatheringWeb SecurityPrivacy
GitHubresearchanddestroy/dorxng

DorXNG

Next Generation DorX. Built by Dorks, for Dorks. πŸ€“

View Repository
122197017 days agoReviewed by Kitploit
Share

DorXNG πŸ”ŽπŸŒŽ

As seen at Recon Village, DEF CON 31

DorXNG is a modern solution for harvesting OSINT data using advanced search engine operators through multiple upstream search providers. On the backend it leverages a purpose built containerized image of SearXNG, a self-hosted, hackable, privacy focused, meta-search engine.

Our SearXNG implementation routes all search queries over the Tor network while refreshing circuits every ten seconds with Tor's MaxCircuitDirtiness configuration directive. We have also disabled all of SearXNG's client side timeout features. These settings allow for evasion of search engine restrictions commonly encountered while issuing many repeated search queries.

The DorXNG client application is written in Python3, and interacts with the SearXNG API to issue search queries concurrently. It can even issue requests across multiple SearXNG instances. The resulting search results are stored in a SQLite3 database.

DorXNG

We only enable upstream search engines that actually honor advanced search operators. Every general and web engine in SearXNG (91 of them) was tested on 2026-11-01 against operators.lst, a 57 query suite covering every documented operator, both over Tor and directly. Engines that ignore operators, or serve unrelated results, are disabled because they pollute the database with noise.

Enabled over Tor (default):

  • Brave
  • DuckDuckGo (web endpoint)
  • Google CSE
  • GMX
  • s1search
  • Startpage
  • Swisscows

Enabled with --no-tor (direct):

  • Brave
  • DuckDuckGo (web endpoint)
  • Google CSE
  • s1search
  • Swisscows
  • Yahoo

These engines scored 92 to 100% on site: and filetype: dorks. Yahoo is direct only: through Tor it returns results unrelated to the query. Bing, Naver, Yandex, and most smaller engines ignore operators, and Google and Qwant block SearXNG entirely, so they are all disabled.

No engine strictly honors inurl: or allinurl: (they are treated as ranking hints), so expect some noise on those dorks. site:, filetype:, and intitle: are reliable.

For more information about what search engines SearXNG supports See: Configured Engines

Please DO NOT use the DorXNG client application against any public SearXNG instances.

Buy Us A Beer! 🍺

Shout Outs πŸ™Œ

Shout out to the developers of Tor and SearXNG for making this possible. Go donate to both projects!

Shout out to the developer of pagodo for the inspiration and that sweet ghdb_scraper.py script!

Last but certainly not least, shout out to j0hnny. The OG Dork. πŸ§ πŸ΄β€β˜ 

Setup πŸ› οΈ

LINUX ONLY ** Sorry Normies ** πŸ€“

Install DorXNG

git clone https://github.com/researchanddestroy/dorxng
cd dorxng
pip install -r requirements.txt
./DorXNG.py -h

Download and Run Our Custom SearXNG Docker Container (at least one). Multiple SearXNG instances can be used. Use the --serverlist option with DorXNG. See: server.lst

When starting multiple containers wait at least a few seconds between starting each one.

docker run researchanddestroy/searxng:latest

If you would like to build the container yourself:

git clone https://github.com/researchanddestroy/searxng # The URL must be all lowercase for the build process to complete
cd searxng
make container.build # Requires docker buildx (or podman)
docker run localhost/searxng/searxng:latest

No buildx? Freeze the version and build with plain docker build:

./manage pyenv.install
./local/py3/bin/python -m searx.version freeze
docker build -f container/Dockerfile -t localhost/searxng/searxng:latest .

By default DorXNG has a hard coded server variable in parse_args.py which is set to the IP address that Docker will assign to the first container you run on your machine 172.17.0.2. This can be changed, or overwritten with --server or --serverlist.

Start Issuing Search Queries

./DorXNG.py -q 'search query'

Query the DorXNG Database

./DorXNG.py -D 'regex search string'

Host Tor Bypass πŸ§…

Upstream search providers and SearXNG move fast, and our custom container can fall behind. If it breaks, you can skip it and run the official upstream SearXNG container instead. In this mode Tor runs on the host machine rather than inside the container.

Install Tor on the host and set the circuit refresh interval:

sudo pacman -S tor # or: sudo apt install tor
echo 'MaxCircuitDirtiness 10' | sudo tee -a /etc/tor/torrc
sudo systemctl enable --now tor
curl -x socks5h://127.0.0.1:9050 -s https://check.torproject.org/api/ip # Should return {"IsTor":true,...}

Run the latest upstream SearXNG container from the DorXNG directory, using our settings.yml:

docker pull searxng/searxng:latest
docker run --rm \
  --network host \
  -v "$(pwd)/settings.yml:/etc/searxng/settings.yml:ro" \
  searxng/searxng:latest

--network host lets the container reach the host's Tor SOCKS proxy at 127.0.0.1:9050. The provided settings.yml layers on top of the container's own defaults: it routes every upstream request through Tor, enables the json output format, disables SearXNG's engine ban and suspension timers, enables only the validated engines, and includes the direct engines used by --no-tor. SearXNG refuses to start if it cannot reach Tor, so start Tor on the host first.

The upstream container serves plain HTTP on port 8080 (the server.port value in settings.yml is ignored), so point DorXNG at it with --server:

./DorXNG.py -s 'http://127.0.0.1:8080/search' -q 'search query'

To run more than one instance, give each one its own port with -e SEARXNG_PORT=8081 and list them in a --serverlist file. Keep in mind that all of these instances share the host's single Tor circuit, unlike our custom containers, which each run their own.

Change the secret_key value in settings.yml before exposing this instance to anything other than localhost.

Bypassing Tor πŸš€

Tor is the default. If you would rather have SearXNG query the upstream search providers directly, add --no-tor:

./DorXNG.py -q 'site:example.com intext:example' --no-tor

This works with our custom container and with the Host Tor Bypass above. Both SearXNG configurations include a second, Tor free copy of each validated engine (named <engine> direct, disabled by default). With --no-tor, DorXNG asks the server for its direct engines and only uses those. Without it, nothing changes.

--no-tor exposes the public IP address of the machine running SearXNG to every search provider you query.

Direct queries are faster and some engines only work directly (Yahoo), but providers rate limit by IP address, so heavy use will get your IP throttled. SearXNG's own !bang shortcuts override --no-tor. To combine them, use the direct shortcuts: !brd (Brave), !ddgwd (DuckDuckGo), !gocd (Google CSE), !s1d (s1search), !swd (Swisscows), !yhd (Yahoo).

MCP Server πŸ€–

Download Tool

Most Popular

View all β†’

Discover the most used tools by our community.

No popularity data yet.

Explore all tools

Browse our collection of tools

View all tools β†’