> ## Documentation Index
> Fetch the complete documentation index at: https://battletest.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# How to add a live battletest target

> Add a domain to BattleTest, set its permission tier, and run your first live infrastructure assessment — prerequisites, target slots, and setup steps.

<Warning>
  **Startup plan or higher required.** Live battletest is not available on Free or Dev plans. [View plans →](https://battletest.dev/pricing)
</Warning>

## Before you start

* You must own or have explicit written authorisation to test the domain
* The domain must be reachable from the public internet (VPN-only and localhost targets are not supported)
* Your plan must have at least one free target slot — check [Tests](https://battletest.dev/tests) to see how many slots you've used. Slot counts and cooldowns per plan are in [Limits & Quotas](/docs/reference/limits-and-quotas#live-battletest-target-slots)
* Your email address must be verified. If you signed up with email and password, check your inbox or resend the verification from [Settings → Account](https://battletest.dev/settings?tab=account)

## Add the target

<Steps>
  <Step title="Open New Environment">
    Go to [Tests → New Environment](https://battletest.dev/tests).
  </Step>

  <Step title="Enter the domain">
    Enter the domain name — for example, `app.example.com` — without a protocol prefix.
  </Step>

  <Step title="Set permission tier">
    Select the initial permission tier. Start with **Read-only** for a first assessment.
  </Step>

  <Step title="Add target">
    Click **Add Target**.
  </Step>
</Steps>

## Activate and run the first scan

<Steps>
  <Step title="Open the environment">
    From the Tests page, click on the environment you just created.
  </Step>

  <Step title="Activate">
    Click **Activate**. The discovery scan begins within a few minutes and the status changes to *Running*.
  </Step>

  <Step title="Wait for discovery">
    Discovery completes in 5–15 minutes depending on the application size. The environment detail page then shows the discovered endpoint inventory.
  </Step>
</Steps>

## Approve active probing

To go beyond passive discovery, approve a higher permission tier:

<Steps>
  <Step title="Open Approvals">
    Go to the environment detail page → **Approvals**.
  </Step>

  <Step title="Review tier description">
    Read what each tier does. See [How Live BattleTest works](/docs/concepts/live-battletest-overview#the-permission-tier-model) for details.
  </Step>

  <Step title="Approve the tier">
    Click **Approve** next to the tier you want to enable and confirm.
  </Step>

  <Step title="Start a new scan">
    Start a new scan from the Tests page.
  </Step>
</Steps>

## Add multiple domains to one environment

An environment can cover multiple domains belonging to the same application — for example, `api.example.com` and `app.example.com`. From the environment detail page, click **Add domain** and enter additional hostnames. All domains in one environment share the same target slot.

## Run a scan immediately (bypass cooldown)

Each plan enforces a minimum time between scans: 4 hours on Startup, 2 hours on Observability. To scan sooner — for example, immediately after a deploy:

<Steps>
  <Step title="Open the environment">
    Go to the environment detail page.
  </Step>

  <Step title="Bypass cooldown">
    Click **Run scan now** (visible when a cooldown is active).
  </Step>

  <Step title="Confirm purchase">
    Confirm the \$49 one-time purchase. The scan starts immediately.
  </Step>
</Steps>

<Note>
  The cooldown bypass applies to a single scan on a single target. The regular cooldown resumes after the bypassed scan completes. If you bypass cooldowns frequently, upgrading to Observability (2-hour cooldown) is more cost-effective.
</Note>