Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
saas_enum — Command-line tool for discovering SaaS platforms a company uses via DNS enumeration | Kitploit
Tools/GitLabGitLab/hackinglz/saas_enum
OSINT (Open Source Intelligence)ReconnaissanceDNS & Subdomain EnumerationInformation Gathering
GitLabhackinglz/saas_enum

saas_enum

Command-line tool for discovering SaaS platforms a company uses via DNS enumeration

View Repository
391 year agoNot yet reviewed
Share
Website

SaaS Enum

SaaS Enum is a command line tool for discovering the SaaS platforms a company may be using. The tool looks for DNS entries that match known provider patterns and optionally performs lightweight web checks for confirmation.

Installation

pip install -r requirements.txt

Usage

Basic check

Provide the company short name (subdomain) to test against all providers:

python saas_enum.py -i example

Batch mode

Process multiple companies from a file and save the results as CSV:

python saas_enum.py -b companies.txt -o results.csv -f csv

List providers

Display all provider templates defined in dns_integrations.yaml:

python saas_enum.py --list-providers

Command line options

  • -i, --input SHORT_NAME
    Short name of the company to check.
  • -b, --batch FILE
    File containing multiple short names to check (one per line).
  • -p, --providers NAMES
    Comma separated list of specific providers to check.
  • -j, --json
    Output results in JSON format when used with a single check.
  • -o, --output FILE
    Save output to the specified file.
  • -f, --format {text,json,csv}
    Output format for saved results. Defaults to text.
  • -w, --workers NUM
    Maximum number of concurrent worker threads (default: 10).
  • -l, --list-providers
    List all available providers and exit.
  • -c, --check-providers
    Validate provider patterns for wildcard DNS.
  • -y, --yaml PATH
    Path to the provider definition YAML file (default: dns_integrations.yaml).
  • -t, --timeout SECONDS
    Timeout in seconds for each provider check (default: 20).
  • -v, --verbose
    Show detailed output for all checks.

The supporting modules are located in the modules directory.

Features

  • DNS-based SaaS provider enumeration
  • Optional HTTP verification of provider pages
  • Batch processing with CSV or JSON reporting

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

This project is licensed under the MIT License - see the LICENSE file for details.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    546
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    477
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    377
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    324
  • 5

    estorides

    grisuno/estorides

    Aggregates 99+ free OSINT sources in parallel, resolves entities into a knowledge graph, and exports STIX 2.1, MISP, or GraphML with LLM-assisted analysis.

    269
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    252

Explore all tools

Browse our collection of tools

View all tools →