> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/identity-verification/fraud-prevention/email-intelligence.md).

# Email Intelligence

***

### Overview

Email intelligence evaluates an email address to gauge how likely it is to belong to a real, established person rather than a throwaway or fabricated identity. An email address is one of the first attributes a user provides, which makes it a valuable early signal.

{% hint style="info" %}
A low-reputation email is a risk indicator, not proof of fraud. Legitimate users sometimes use new or privacy-focused addresses, so email signals work best combined with other checks. 
{% endhint %}

### What the check analyzes

The email address is evaluated for attributes such as:

* **Validity and deliverability** — Whether the domain exists, has valid mail (MX) records, and can plausibly receive mail.
* **Disposable or temporary address detection** — Whether the domain provides short-lived, throwaway inboxes commonly used to evade tracking.
* **Domain type and age** — Whether the domain is free webmail, corporate, or custom, and how long it has existed.
* **Online footprint** — Whether the address is associated with established accounts and activity across the web.
* **Breach exposure and history** — Whether the address has appeared in known data breaches or has prior history, which can indicate a real, aged identity.

### Risk signals it surfaces

| Signal                           | What it may indicate                                                     |
| -------------------------------- | ------------------------------------------------------------------------ |
| Disposable or temporary domain   | The user wants to remain untraceable or create a one-time account.       |
| Recently registered domain       | The address may have been created solely to pass this check.             |
| No online footprint              | The address has no history consistent with a real, active person.        |
| Invalid or undeliverable address | The contact point is unusable, blocking later verification and recovery. |
| Mismatch with the claimed name   | The address content is inconsistent with the identity being presented.   |

### Benefits and use cases

* **Synthetic-identity detection** — Fabricated identities often rely on freshly created or disposable email addresses with no real-world history.
* **Fake-account and spam prevention** — Block bulk sign-ups that depend on throwaway inboxes.
* **Cleaner contact data** — Ensuring an address is valid and deliverable protects later steps that depend on email, such as one-time passcodes and account recovery.
* **Lower friction for trusted users** — An established, well-reputed address can support a faster onboarding path.
* **Earlier, cheaper fraud filtering** — Catching bad signups before document capture reduces verification cost and reviewer workload.

### Where it fits in the journey

Email intelligence is typically applied **as soon as the address is collected**, often before document verification, so high-risk applicants can be filtered, challenged, or routed to manual review early.


---

# 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://docs.1kosmos.com/identity-verification/fraud-prevention/email-intelligence.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.