amass-track

Show the difference between the last two enumerations of the specified domain

$ amass track -dir [path/to/database_directory] -d [domain_name] -last 2

$ amass track -dir [path/to/database_directory] -d [domain_name] -since [01/02 15:04:05 2006 MST]

amass track -d [options]

-d
    Required. Specifies the target domain to track.

-config
    Path to the Amass configuration file.

-dir
    Directory for storing Amass output and tracking data.

-interval
    Time interval between Amass scans (e.g., '1h', '30m').

-db
    Path to store the sqlite database used to track the information.
If the database isn't configured, the results won't be persisted across runs.

-passive
    Only perform passive enumeration (no active scanning).

-brute
    Enables brute forcing of subdomain names.

-resolvers
    Path to a file containing a list of custom DNS resolvers.

-log
    Path to write the command output to.

The `amass-track` command is a helper script or function used in conjunction with the `amass` tool. `amass` is an open-source tool used for network mapping and attack surface discovery. `amass-track` specifically focuses on continuously monitoring changes in discovered subdomains over time. It works by periodically running `amass` and comparing the results to previous runs. This allows security professionals and system administrators to identify new subdomains, DNS changes, or potential attack vectors that may have emerged. `amass-track` commonly uses a database to store the results of each scan, which enables efficient comparisons. The output often includes information about newly added subdomains, removed subdomains, and changes in associated DNS records. This proactive monitoring is crucial for maintaining a strong security posture and quickly responding to potential threats that may arise from newly exposed assets. It allows for detection of subdomain takeovers, typosquatting and identification of new or forgotten infrastructure.

The typical workflow for `amass-track` involves the following steps:
1. Configure the `amass` tool and `amass-track` script.
2. Specify the target domain to monitor.
3. Set the desired scanning interval.
4. Run the script, which will then periodically execute `amass`, compare the results, and report any changes.

To track the subdomains of example.com, save the results to database and execute amass every hour, and log the results to a file:
`amass-track -d example.com -interval 1h -db /path/to/amass.db -log /path/to/output.log`

amass(1), dig(1), host(1), nmap(1)