OWASP Amass
The OWASP Amass Project performs network mapping of attack surfaces and external asset discovery using open source information gathering and active reconnaissance techniques.
Information Gathering Techniques Used:
| Technique | Data Sources |
|---|---|
| APIs | 360PassiveDNS, Ahrefs, AnubisDB, BeVigil, BinaryEdge, BufferOver, BuiltWith, C99, Chaos, CIRCL, DNSDB, DNSRepo, Deepinfo, Detectify, FOFA, FullHunt, GitHub, GitLab, GrepApp, Greynoise, HackerTarget, Hunter, IntelX, LeakIX, Maltiverse, Mnemonic, Netlas, Pastebin, PassiveTotal, PentestTools, Pulsedive, Quake, SOCRadar, Searchcode, Shodan, Spamhaus, Sublist3rAPI, SubdomainCenter, ThreatBook, ThreatMiner, URLScan, VirusTotal, Yandex, ZETAlytics, ZoomEye |
| Certificates | Active pulls (optional), Censys, CertCentral, CertSpotter, Crtsh, Digitorus, FacebookCT |
| DNS | Brute forcing, Reverse DNS sweeping, NSEC zone walking, Zone transfers, FQDN alterations/permutations, FQDN Similarity-based Guessing |
| Routing | ASNLookup, BGPTools, BGPView, BigDataCloud, IPdata, IPinfo, RADb, Robtex, ShadowServer, TeamCymru |
| Scraping | AbuseIPDB, Ask, Baidu, Bing, CSP Header, DNSDumpster, DNSHistory, DNSSpy, DuckDuckGo, Gists, Google, HackerOne, HyperStat, PKey, RapidDNS, Riddler, Searx, SiteDossier, Yahoo |
| Web Archives | Arquivo, CommonCrawl, HAW, PublicWWW, UKWebArchive, Wayback |
| WHOIS | AlienVault, AskDNS, DNSlytics, ONYPHE, SecurityTrails, SpyOnWeb, WhoisXMLAPI |
Installation 
You can find some additional installation variations in the Installation Guide.
Prebuilt Packages
- Simply unzip the package
- Put the precompiled binary into your path
- Start using OWASP Amass!
Homebrew
brew tap owasp-amass/amass
brew install amassDocker Container
- Install Docker
- Pull the Docker image by running
docker pull caffix/amass - Run
docker run -v OUTPUT_DIR_PATH:/.config/amass/ caffix/amass enum -d example.com
The volume argument allows the Amass graph database to persist between executions and output files to be accessed on the host system. The first field (left of the colon) of the volume option is the amass output directory that is external to Docker, while the second field is the path, internal to Docker, where amass will write the output files.
From Source
- Install Go and setup your Go workspace
- Download OWASP Amass by running
go install -v github.com/owasp-amass/amass/v4/...@master - At this point, the binary should be in
$GOPATH/bin
Documentation 
Use the Installation Guide to get started.
Go to the User's Guide for additional information.
See the Tutorial for example usage.
See the Amass Scripting Engine Manual for greater control over your enumeration process.
Corporate Supporters
Testimonials
Accenture
"Accenture’s adversary simulation team has used Amass as our primary tool suite on a variety of external enumeration projects and attack surface assessments for clients. It’s been an absolutely invaluable basis for infrastructure enumeration, and we’re really grateful for all the hard work that’s gone into making and maintaining it – it’s made our job much easier!"
- Max Deighton, Accenture Cyber Defense Manager
Visma
"For an internal red team, the organisational structure of Visma puts us against a unique challenge. Having sufficient, continuous visibility over our external attack surface is an integral part of being able to efficiently carry out our task. When dealing with hundreds of companies with different products and supporting infrastructure we need to always be on top of our game.
For years, OWASP Amass has been a staple in the asset reconnaissance field, and keeps proving its worth time after time. The tool keeps constantly evolving and improving to adapt to the new trends in this area."
- Joona Hoikkala (@joohoi) & Alexis Fernández (@six2dez), Visma Red Team
References 
Did you write a blog post, magazine article or do a podcast about OWASP Amass? Or maybe you held or joined a conference talk or meetup session, a hacking workshop or public training where this project was mentioned?
Add it to our ever-growing list of REFERENCES.md by forking and opening a Pull Request!
Top Mentions
- Phillip Wylie | Securing APIs Through External Attack Surface Management (EASM)
- Kento Stewart | Mapping Your External Perimeter during an Incident with OWASP Amass
- WhoisXML API | OWASP Amass and WhoisXML API Are Now Integration Partners
- Intigriti | Hacker tools: Amass – Hunting for Subdomains
- Hakluke | Guide to Amass — How to Use Amass More Effectively for Bug Bounties
- SecurityTrails | OWASP Amass: A Solid Information Gathering Tool
- TrustedSec | Upgrade Your Workflow, Part 1: Building OSINT Checklists
- SANS ISC | Offensive Tools Are For Blue Teams Too
- Jason Haddix | LevelUp 0x02 - The Bug Hunters Methodology v3(ish)
- Daniel Miessler | amass — Automated Attack Surface Mapping
- Dionach | How to Use OWASP Amass: An Extensive Tutorial
- nynan | How to Actually Use Amass More Effectively — Bug Bounty
- ToolWar | Extreme Subdomain Enumeration/Scanning on Windows : OWASP Amass
Contributing 
We are always happy to get new contributors on board! Please check CONTRIBUTING.md to learn how to contribute to our codebase, and join our Discord Server to discuss current project goals.
Troubleshooting
If you need help with installation and/or usage of the tool, please join our Discord server where community members can best help you.
:stop_sign: Please avoid opening GitHub issues for support requests or questions!
Licensing
This program is free software: you can redistribute it and/or modify it under the terms of the Apache license. OWASP Amass and any contributions are Copyright © by Jeff Foley 2017-2023. Some subcomponents have separate licenses.
