Authorization

Proving you have permission to test a target.

⚠️ Authorization is Required

You must verify ownership or authorization before scanning any target. Unauthorized testing is illegal and violates our Terms of Service.

Verification Methods

Choose one of these methods to prove authorization:

1. DNS Verification (Recommended)

Add a TXT record to your domain's DNS configuration:

Record Type: TXT
Host/Name: @ (or your subdomain)
Value:
hackerbot-verify=hb_xxxxxxxxxxxx

Verification typically completes within 5 minutes. DNS propagation may take up to 24 hours.

2. File Upload Verification

Upload a verification file to your web server:

  1. Download the verification file from your dashboard
  2. Upload to: /.well-known/hackerbot-verify.txt
  3. Ensure it's accessible via HTTPS
  4. Click "Verify" in your dashboard

3. Repository Verification

For GitHub-connected projects, verify via your repository:

  1. Connect your GitHub repository to Hacker Bot
  2. Add a .hackerbot file to your repo root
  3. Include your target domain in the file
  4. Push to your main branch
# .hackerbot
targets:
  - example.com
  - staging.example.com

Agency & Client Authorization

Testing on behalf of clients requires additional documentation:

  • Signed authorization letter from the client
  • Defined scope and testing window
  • Emergency contact information
  • Upload via Settings → Authorization Documents

We provide authorization templates you can use with your clients. Contact support for templates.

Attack Paths GitHub Actions