> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/suspicious-sending-domain-with-sender-address-randomization.md).
# Suspicious sending domain with sender address randomization
### Synopsis
| Field | Value |
| -------------------- | ----------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | 30 Minutes |
| Deduplication Period | 1 Day |
| Required Data | Microsoft 365 Emails |
| Detection Modules | Email |
| Detector Tags | Phishing |
| ATT\&CK Tactic | Initial Access (TA0001) |
| ATT\&CK Technique | Phishing (T1566) |
| Severity | Informational |
### Description
Multiple messages from a single sender domain were observed over a short period, each using a unique sender address. This per-message sender randomization is uncommon for legitimate senders and suggests automated behavior.
### Attacker's Goals
Trick the user into clicking a link, while avoiding detection.
### Investigative actions
* Examine the sender's IP address and reputation.
* Verify whether the sender's IP address has appeared in different log sources before, and if it is recognizable.
* If the message contains attachments or links, scrutinize them for any suspicious indications.
* Monitor further actions taken, such as file downloads or access to potentially malicious links.
### Variations
High-volume sender domain with per-message sender randomization
**Synopsis**
| Field | Value |
| ----------------- | ----------------------- |
| ATT\&CK Tactic | Initial Access (TA0001) |
| ATT\&CK Technique | Phishing (T1566) |
| Severity | Informational |
**Description**
A high volume of emails was observed from a single sending domain over a short time period, each using a unique sender address. This high volume per-message sender randomization is uncommon for legitimate senders and suggests automated behavior.
**Attacker's Goals**
Trick the user into clicking a link, while avoiding detection.
**Investigative actions**
* Examine the sender's IP address and reputation.
* Verify whether the sender's IP address has appeared in different log sources before, and if it is recognizable.
* If the message contains attachments or links, scrutinize them for any suspicious indications.
* Monitor further actions taken, such as file downloads or access to potentially malicious links.
---
# 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://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/suspicious-sending-domain-with-sender-address-randomization.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.