> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/guides/marketing/email-deliverability/how-email-authentication-works-spf-dkim-dmarc.md).

# How Email Authentication Works (SPF, DKIM, DMARC)

### **Simple Explanation**

When you send an email, providers want to confirm:“Is this sender legitimate?”Authentication proves your emails are truly coming from your domain.

### **What This Includes**

* **SPF**: Defines which servers are allowed to send emails for your domain
* **DKIM**: Verifies the email hasn’t been altered
* **DMARC**: Tells providers how to handle suspicious emails

### **Why This Matters**

Without authentication:

* Emails are more likely to go to spam
* Some messages may be blocked entirely

With proper setup:

* Your emails appear more trustworthy
* Inbox placement improves

### **Advanced Details**

When Rechat sends emails on your behalf, it must align with your domain.This is called **DKIM alignment**.To achieve this, Rechat is authorized to send using a subdomain of your domain, improving trust with providers like Gmail and Outlook.

{% content-ref url="/pages/Pk4cvAnkMIjdH0lcBXZa" %}
[DNS Self-Service Setup](/appendix/brokerage-set-up/email-delivery/dns-self-service-setup.md)
{% endcontent-ref %}


---

# 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://help.rechat.com/guides/marketing/email-deliverability/how-email-authentication-works-spf-dkim-dmarc.md?ask=<question>&goal=<user_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.