> 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/lucy-wiki-de/anwendungsreferenz/support/systemtests/e-mail-spoofing-test.md).
# E-Mail-Spoofing-Test
Einführung
E-Mail-Spoofing ist die Fälschung eines E-Mail-Headers, sodass die Nachricht so erscheint, als stamme sie von jemandem oder irgendwoanders als der tatsächlichen Quelle. Diese Taktik wird häufig in Phishing- und Spam-Kampagnen verwendet, weil Empfänger eher eine E-Mail öffnen, wenn sie glauben, dass sie aus einer legitimen Quelle stammt. Das Ziel von E-Mail-Spoofing ist es, Empfänger dazu zu verleiten, eine Aufforderung zu öffnen und möglicherweise darauf zu reagieren.
{% hint style="info" %}
Navigieren Sie zu **Support -> Systemtests -> Mail-Spoofing-Test**
{% endhint %}
***
### Testen Ihrer Domains
Um die Anfälligkeit Ihrer Domain für Spoofing zu testen, geben Sie einfach die Domain und einen Empfänger auf derselben Domain ein und klicken Sie dann auf **Test starten**:
***
---
# 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/lucy-wiki-de/anwendungsreferenz/support/systemtests/e-mail-spoofing-test.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.
