Skip to content

Latest commit

 

History

History
129 lines (84 loc) · 4.42 KB

README.md

File metadata and controls

129 lines (84 loc) · 4.42 KB
Raw

Logo

another Google Dorker

An OSINT script, running on Python

Report Bug . Request Feature

Contributors Issues License

Table Of Contents

About The Project

Web capture_11-6-2022_225030_

There are many great Google Dork scripts available on GitHub, however, I didn't find one that really suit my needs so I created this enhanced one. I want to create a Google Dork script so amazing that it'll be the last one you ever need.

Here's why:

  • Your time should be focused on finding information.

  • You shouldn't be doing the same tasks over and over like creating a googling 100 searches per hand

This script is not finished yet and I am actively working on it. You may also suggest changes by forking this repo and creating a pull request or opening an issue.

A list of commonly used resources that I find helpful are listed in the acknowledgements.

Built With

This script is made with Python and would not be possible without the amazing module 'googlesearch'

Getting Started

To get a local copy up and running follow these simple example steps.

Prerequisites

You'll need Python3 and python3-pip

Installation

  1. Clone the repo
git clone https://github.com/SpotlightForBugs/g-dork.git && cd g-dork
  1. Install requirements
pip install -r requirements.txt

Usage

usage: g-dork.py [-h] -q TARGET [-html | -j | -t] [-qty QTY] [-d DELAY]

options:
  -h, --help            show this help message and exit
  -q TARGET, -query TARGET
                        what you want to find
  -html, -webversion    outputs the result as HTML5
  -j, -json             outputs the result as JSON
  -t, -txt              outputs the result as a text
  -qty QTY, -quantity QTY how many results shoud be processed, defaults to 10 results                                           
  -d DELAY, -delay DELAY  how long to wait between searches in seconds, defaults to 1

Roadmap

See the open issues for a list of proposed features (and known issues).

Contributing

Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated.

  • If you have suggestions for adding or removing projects, feel free to open an issue to discuss it, or directly create a pull request after you edit the affected file with necessary changes.
  • Please make sure you check your spelling and grammar.
  • Create individual PR for each suggestion.
  • Please also read through the Code Of Conduct before posting your first idea as well.

Creating A Pull Request

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/AmazingFeature)
  3. Commit your Changes (git commit -m 'Add some AmazingFeature')
  4. Push to the Branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

License

Distributed under the MIT License. See LICENSE for more information.

Authors