Skip to content

release 1.0 ‐ 1.1

Jump to bottom
alzzdev edited this page Jun 11, 2026 · 1 revision

Release Notes – v1.1

Atdork v1.1 is a major stability and capability upgrade over v1.0.
This release introduces multi‑threaded batch execution, intelligent output validation, a significantly enhanced proxy manager, and several quality‑of‑life improvements that make the tool more robust for professional OSINT workflows.

New Features

Multi‑Threaded Batch Processing

  • Added core/multi_thread_runner.py – a parallel batch runner built on ThreadPoolExecutor.
  • New CLI flag --concurrency (default 1) controls the number of worker threads.
  • When a configurable number of consecutive failures occurs (--max-fallback-failures, default 3), the runner automatically falls back to safe sequential mode, ensuring no query is lost.
  • The progress bar remains fully functional and thread‑safe.

Output Validation Engine

  • New module lib/validator.py filters out low‑quality, spam, or invalid results.
  • Every result is checked for:
    • Valid URL (scheme, hostname, TLD)
    • Spam patterns in title and snippet (casino, porn, SEO spam, suspicious TLDs)
    • Minimum title length (5 characters)
  • Optional strict mode (--strict-filter) further rejects results with empty or very short snippets.
  • Filtering is enabled by default; disable it with --no-validate.
  • After filtering, the console shows how many results were removed.

Advanced Proxy Manager

  • core/proxy_manager.py now includes:
    • Proxy validation – rejects malformed URLs (e.g., missing scheme or port).
    • Strict mode (--strict) – raises an error instead of falling back to a direct connection when all proxies are down.
    • Auto‑removal – permanently removes a proxy after N consecutive failures (--max-failures).
    • Proxy statistics – tracks success/failure counts per proxy, viewable with --debug.
    • Dynamic pool manipulation – methods add_proxy() and remove_proxy() for future runtime adjustments.
  • New CLI flags: --proxy-cooldown, --max-failures, --strict.

User‑Agent Rotation Module

  • Extracted User‑Agent management into core/user_agents_managements.py.
  • A curated list of 15 modern desktop and mobile User‑Agent strings.
  • Every search call (including retries) automatically rotates the User‑Agent, unless a custom one is supplied via --user-agent.

Sequential Batch Runner Preserved

  • Original batch runner remains as core/batch_runner.py and is used when --concurrency is 1 (the default). This ensures backward compatibility and a simple option for users who do not need parallelism.

Enhancements & Changes

  • Codebase reorganisation – new core/ and lib/ modules separate concerns cleanly: scanning, batching, proxy management, display, storage, and validation.
  • Improved error handling – search_dork() now raises RuntimeError with a descriptive message after all retries are exhausted.
  • Better debug logging – detailed logs show which proxy, User‑Agent, and attempt are being used.
  • CLI argument additions – 8 new flags to control the added features (see updated README or --help).
  • Documentation – a complete Wiki and updated README.md covering every feature and use case.

Changes from v1.0

Area v1.0 v1.1
Batch execution Sequential only Sequential + Multi‑threaded with auto‑fallback
Result filtering None Spam/invalid URL removal + strict mode
Proxy handling Basic list with cooldown Validation, strict mode, auto‑removal, stats
User‑Agent Single hardcoded Rotated from pool of 15 modern UAs
File structure Monolithic Modular core/ + lib/
CLI flags 12 20+

Upgrading from v1.0

If you are updating from v1.0:

  1. Pull the latest code from the repository.
  2. Install any new dependencies (pip install -r requirements.txt – no new packages were added).
  3. Review the new CLI flags with python main.py --help.
  4. No changes are required in your existing batch files or proxy lists; all v1.0 flags continue to work identically.

Known Limitations

  • Multi‑threading with --concurrency does not (yet) enforce a global rate‑limit; use --delay inside each thread and set --concurrency wisely.
  • The built‑in spam patterns are a starting point – custom pattern lists may be added in future releases.
  • Tor integration depends on a running Tor service listening on 127.0.0.1:9050.

We welcome feedback and contributions. If you encounter any issues, please open a GitHub issue.

Full documentation: Home · Usage Guide · Command Reference

Clone this wiki locally