> For the complete documentation index, see [llms.txt](https://wiki.lucysecurity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.lucysecurity.com/guides/quick-guides/create-your-first-campaign/register-an-attack-domain.md).
# Register an Attack Domain
Why do you need to register an Attack Domain?
Registering an attack domain serves two key purposes:
1. Enables creating domains resembling the targeted organization, enhancing realism (e.g., "mirconsoft.com" instead of "microsoft.com").
2. Prevents blacklisting of the Lucy system domain, safeguarding your server and ensuring effective future campaigns.
Configuring an attack domain in Lucy is simplified with our GoDaddy API integration, which automatically sets up DNS records for email sending and landing page hosting.
{% hint style="info" %}
Navigate to **Settings -> Common System Settings -> Domains**
{% endhint %}
Select "Register"\
\
Enter the modified "spoofed" domain you would like to use and check whether it is available for registration. When the check is complete you will be taken to the registration page.
{% hint style="warning" %}
Provide a valid email address for WHOIS validation, domain expiration alerts, and DNS management access. Ensure accurate details when registering your domain as it is linked to your organization.
{% endhint %}
{% hint style="info" %}
After registering your domain, the automatic DNS configuration typically completes within minutes. However, in very rare cases, it may take 4 to 8 hours for all DNS servers to fully propagate.
{% endhint %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://wiki.lucysecurity.com/guides/quick-guides/create-your-first-campaign/register-an-attack-domain.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
