SubFinder Action makes it easy to orchestrate SubFinder with GitHub Action.

Example Usage

GitHub Action running SubFinder for single domain

      - name: 🔎 SubFinder - DNS Enumeration
        uses: projectdiscovery/subfinder-action@main
        with:
          domain: projectdiscovery.io

GitHub Action running SubFinder for multiple domains

      - name: 🔎 SubFinder - DNS Enumeration
        uses: projectdiscovery/subfinder-action@main
        with:
          list: domain_list.txt

GitHub Action running SubFinder with config file

      - name: 🔎 SubFinder - DNS Enumeration
        uses: projectdiscovery/subfinder-action@main
        with:
          list: domain_list.txt
          config: subfinder.yaml

Workflow: .github/workflows/subfinder.yml

name: 🔎 SubFinder - DNS Enumeration

on:
    schedule:
      - cron: '0 0 * * *'
    workflow_dispatch:

jobs:
  subfinder-scan:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-go@v3
        with:
          go-version: 1.17

      - name: SubFinder - DNS Enumeration
        uses: projectdiscovery/subfinder-action@main
        with:
          domain: projectdiscovery.io

      - name: GitHub Workflow artifacts
        uses: actions/upload-artifact@v2
        with:
          name: subfinder.log
          path: subfinder.log

`domain`	Domain to run subdomain enumeration	true
`list`	List of domains to run subdomain enumeration	false
`config`	Config file to use with subdomain enumeration	false
`output`	File to save output result (default - subfinder.log)	false
`json`	Write results in JSON format	false
`flags`	Additional subfinder CLI flags to use	false
`active`	Filter subdomains with no DNS records	false

subfinder-action

Most Popular

SubFinder Action makes it easy to orchestrate SubFinder with GitHub Action.

Example Usage

Available Inputs