# m3n0sd0n4ld/GooFuzz

GooFuzz is a tool to perform fuzzing with an OSINT approach, managing to enumerate directories, files, subdomains or parameters without leaving evidence on the target's server and by means of advanced Google searches (Google Dorking).

Repository: https://github.com/m3n0sd0n4ld/GooFuzz
Canonical: https://ross.abutalabs.com/products/goofuzz
Language: Shell
License: GPL-3.0
License Family: copyleft
Topics: bash-script, bugbounty, fuzzing, hacking, infosec, osint, penetration-testing, pentesting, recon, red-team, subdomain, google-dorks, reconnaissance, discovery, information-disclosure
Last push: 2025-12-21T07:24:46+00:00

## Health v2 (maintenance only)
Score: 57/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 58, release rhythm 30, longevity 100
- inputs: {"age_days": 1538, "days_push": 255, "days_rel": 256, "gap_med": 214, "n_releases_24m": 2}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1585, forks 158 (observed 2026-08-28T04:05:07.558853+00:00)

## What it is
GooFuzz is a Bash-based CLI tool that performs fuzzing-style reconnaissance using advanced Google searches (Google Dorking) via the Google Custom Search API. It enumerates directories, files, subdomains, and parameters without sending requests to the target's server, leaving no evidence on the target.

## Use cases
- enumerate directories and files on a target without touching its server
- find subdomains using google dorks for bug bounty recon
- discover exposed sensitive files through osint
- fuzz for parameters without leaving traces in target logs
- passive reconnaissance for red team engagements
- find information disclosure leaks via advanced google searches

## When to choose
- you need passive recon that leaves no evidence on the target's server
- you want to leverage Google's index instead of brute-forcing directories
- you're doing bug bounty or red team reconnaissance with OSINT techniques

## When to avoid
- you need active scanning or fuzzing against the live server itself
- you don't want to set up a Google Cloud API key and Programmable Search Engine
- the target content isn't indexed by Google

## Facets
- artifact type: cli-tool
- maturity: active
- function: osint, search-engine, web-scraping, security, cli
- domain: security, osint, penetration-testing, crawlers
- platform: cli
- tags: google-dorks, reconnaissance, bug-bounty, red-team, bash-script, information-disclosure, subdomain-enumeration, command-line, linux, macos

## Member repositories
- m3n0sd0n4ld/GooFuzz (main) score 57

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:05:07.558853+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T03:55:37.649694+00:00, confidence not recorded.
  - readme: https://github.com/m3n0sd0n4ld/GooFuzz (fetched 2026-08-28T04:05:07.558853+00:00, sha 6136e2008a17)
- Data as of 2026-08-30T08:39:29.467469+00:00.
