khanamaan/domainspyder repository overview

Domain intelligence from one CLI: subdomain enumeration, DNS analysis, port scanning, technology detection and WHOIS, with JSON and HTML reports.

This is the official image of DomainSpyder⁠, also available on PyPI⁠. It needs no local Python install.

⁠Quick start

docker run --rm -it khanamaan/domainspyder dns example.com
docker run --rm -it khanamaan/domainspyder subdomains example.com --alive
docker run --rm -it khanamaan/domainspyder info example.com

Run it with no arguments to see the help, or add --help after any command.

⁠Commands

Full options and example output are in the README⁠.

⁠Saving reports and using wordlists

The container's working directory is /data. Mount a host directory there, and relative paths for --output, --save and --wordlist resolve inside it:

# Write an HTML report to the current directory
docker run --rm -it -v "$PWD:/data" khanamaan/domainspyder info example.com --output report.html

# Use a wordlist from the current directory
docker run --rm -it -v "$PWD:/data" khanamaan/domainspyder subdomains example.com --brute-only --wordlist words.txt

On Linux, add --user "$(id -u):$(id -g)" so the container can write to the mounted directory and the files it creates are owned by you.

To use it like a locally installed command, add an alias to your shell profile:

alias domainspyder='docker run --rm -it -v "$PWD:/data" khanamaan/domainspyder'
domainspyder dns example.com

⁠Scanning your own machine

Inside the container, localhost is the container itself. To scan services on the host, target host.docker.internal on Docker Desktop, or add --network host on Linux.

⁠Tags

The same image and tags are mirrored to GitHub Container Registry as ghcr.io/khanamaan55/domainspyder.

Pin an exact version for repeatable results. Release notes are in the changelog⁠.

⁠Image details

• Platforms: linux/amd64 and linux/arm64
• Base: python:3.13-slim
• User: runs as an unprivileged user (UID 1000), not root
• Entrypoint: domainspyder, so arguments go straight to the CLI
• Supply chain: releases are built from the tagged source by GitHub Actions⁠, with provenance and SBOM attestations
• Source: Dockerfile⁠

⁠Support

Report bugs and request features on GitHub Issues⁠.

Released under the MIT License⁠. Created by Amaan Khan⁠.