# Install findomain with Homebrew, Nix, pacman Cross-platform subdomain enumerator. Version 10.0.1 via Homebrew; verified 2026-06-22. Also installable with nix: nix profile install nixpkgs#findomain. ## Install ```sh sudo av install brew:findomain ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install findomain ``` Evidence: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#findomain ``` Evidence: nixpkgs package indexes: pkgs/by-name/fi/findomain/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - pacman (92%): ```sh sudo pacman -S findomain ``` Evidence: Arch Linux sync databases: findomain from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz ## Package facts - **Package key:** brew:findomain - **Package manager:** Homebrew - **Version:** 10.0.1 - **Source summary:** Cross-platform subdomain enumerator - **Homepage:** - **Repository:** - **Last updated:** 2026-06-22T14:03:20-07:00 - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - findomain (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 10.0.1 ## Project history and usage Findomain is a Rust-based subdomain enumeration and reconnaissance tool for security testing, bug bounty work, and domain monitoring. Its official README presents it as a complete domain-recognition tool that combines Certificate Transparency logs, public APIs, optional API keys, resolution, screenshotting, port scanning, imports from other tools, and alerting integrations. ### Project history The public GitHub repository was created in April 2019, and its first GitHub release was tagged 0.1.2 later that month. The project quickly defined itself around speed and breadth rather than brute force alone: the README describes a CT-log and API-driven approach, with later feature growth around monitoring, webhooks, resolver behavior, and multiple output modes. Findomain's implementation choice matters to packagers because the README emphasizes cross-platform Rust builds and official binaries for Linux, Windows, macOS, AArch64, ARMv7, NixOS, and Docker. That made it easy to distribute as a single CLI in security-focused environments. ### Adoption history Findomain's adoption is mostly in the offensive-security and reconnaissance niche. Its own documentation names Homebrew, pacman, Nix, Pentoo, Docker, and direct release downloads as installation paths, which fits a tool used from disposable workstations, CI-style monitoring jobs, and bug-bounty toolchains. The project also added premium and monitoring-oriented features, such as webhook alerts, database-backed subdomain monitoring, and imports from other tools. That shifted it from a one-shot enumerator toward a small domain-observation workflow. ### How it is used Users run Findomain to discover subdomains from Certificate Transparency logs and public APIs, optionally resolve the results, write target-specific output files, import findings from other tools, and monitor for newly observed subdomains. Because several sources require API tokens, Findomain usage ranges from zero-configuration public lookups to richer authenticated enumeration using providers such as VirusTotal, SecurityTrails, Facebook Certificate Transparency, and C99. ### Why package nerds care Findomain is package-interesting because it is a modern security CLI with the familiar shape of a single executable, but with a workflow that spans SaaS APIs, CT logs, local resolution, notifications, and optional persistence. It also reflects a common pattern in security packaging: fast-moving niche tools become useful to package managers when they provide repeatable release artifacts and simple CLI installation, even if most of their culture lives in README examples rather than formal manuals. ### Timeline - 2019: Public GitHub repository is created. - 2019: First GitHub release, 0.1.2, is published. - 2020s: README documents monitoring, webhook alerts, imports, brute-force support, and multiple API integrations. - 2026: Repository metadata shows continued maintenance activity. ### Related projects - Certificate Transparency logs are a primary data source for Findomain's enumeration strategy. - crt.sh, Certspotter, VirusTotal, Sublist3r, SecurityTrails, urlscan.io, Threatminer, and related APIs are documented as data sources. - Other subdomain enumeration tools are part of the same ecosystem because Findomain can import and work with data discovered by other tools. ### Sources - - - - ## Security Notes narrow executable package without higher-risk signals. - **Geiger risk:** green / low - narrow executable package without higher-risk signals ## Other Package-Manager Records - Nix - findomain: normalized package name match | nixpkgs package indexes: pkgs/by-name/fi/findomain/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - pacman - findomain - 10.0.1-2: normalized package name match | Arch Linux sync databases: findomain from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | The fastest and cross-platform subdomain enumerator, do not waste your time | https://github.com/Findomain/Findomain ## Combined YAML source View the package source record on GitHub. [combined/findomain.yml](https://github.com/mxcl/pkgdb/blob/main/combined/findomain.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph