> For the complete documentation index, see [llms.txt](https://copilot-docs.bugbase.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://copilot-docs.bugbase.ai/enterprise/settings/domain-verification.md).

# Domain Verification

Use **Settings -> Domain Verification** to prove ownership of root domains before running external discovery, external attack phases, browser-session recording, or Manual Crawler flows when verification is required.

The guided **New Assessment** flow also includes a **Verify Domain** step for the same check.

## Verification Flow

1. Open **Settings -> Domain Verification**.
2. Select the root domain that needs verification.
3. Publish the DNS TXT record shown in the challenge.
4. Click **Verify Now**.
5. Wait for the status to change to **Verified**.

If the DNS challenge expires or needs to be regenerated, use **Refresh Challenge** and publish the new TXT value before trying again.

## Statuses

| Status         | Meaning                                                                                |
| -------------- | -------------------------------------------------------------------------------------- |
| **Verified**   | The domain passed ownership verification and can be used for gated external workflows. |
| **Pending**    | A challenge exists, but the TXT record has not been confirmed yet.                     |
| **Unverified** | No valid ownership proof has been completed for the root domain.                       |

## When Verification Blocks Work

Verification may be required before:

* recording browser sessions;
* using Manual Crawler;
* launching external discovery;
* launching external attack phases.

If a flow is blocked, open **Settings -> Domain Verification**, verify the root domain, then return to the scan or browser-session flow.

Enterprise managers can disable verification enforcement for some deployments. Shared trial environments usually require DNS TXT verification unless Bugbase support grants an exception.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://copilot-docs.bugbase.ai/enterprise/settings/domain-verification.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.