> 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/attack-simulations/attack-types/email-spoofing-test.md).

# Email Spoofing Test

## Overview

Email spoofing is the forgery of an email header, making it appear as though the message originated from someone or somewhere other than its actual source. This tactic is commonly used in phishing and spam campaigns, as individuals are more likely to open emails they believe have been sent by a legitimate source. The goal of email spoofing is to entice recipients to open the email and potentially respond to the solicitation.

## Checklist

* [x] [Register the domain](/application-reference/settings/common-system-settings/domains.md#register-a-domain-via-the-domain-registration-wizard)
* [x] Create a recipient on the domain
* [x] [Create a mail spoofing campaign in the wizard](/application-reference/campaigns/wizard-mode.md)

## Run the Test

To run the mail spoofing test simply enter the domain and recipient in the wizard and click **Start Test**.


---

# 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://wiki.lucysecurity.com/guides/attack-simulations/attack-types/email-spoofing-test.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.