> For the complete documentation index, see [llms.txt](https://docs.emaillabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.emaillabs.io/en/analytics-panel/administrator/sender-authorization/from-domain-authorization-configurator/authorizing-the-domain-hosted-by-cloudflare.md).

# Authorizing the Domain Hosted by Cloudflare

1. Log in to the Cloudflare dashboard, then select your account and domain.<br>

   <figure><img src="/files/p1Vtt2hevcFTpNtnlB8U" alt=""><figcaption></figcaption></figure>
2. From the menu on the left, choose the "DNS" tab, and then select "Records.
3. Click on the "Add New Record" button<br>

   <figure><img src="/files/mTX6SoTrs9IjhoNjSsfO" alt=""><figcaption></figcaption></figure>
4. From the dropdown menu under "Type" select CNAME.
5. In the "Name" field, add `selector._domainkey` \
   **Note! Do not include your domain name.**
6. In the "Target" field, enter the corresponding value generated in the EmailLabs panel.
7. Ensure the "Proxy status" is set to "DNS only.<br>

   <figure><img src="/files/8pU69wdhOm6haKi6uZcU" alt=""><figcaption><p>NOTE! The domain provided in the 'Value' field is generated individually, depending on the EmailLabs' panel version.</p></figcaption></figure>
8. Click 'Save' to update the information.
9. Wait for the DNS system to approve the changes. Depending on DNS record propagation, this **may take a few minutes or up to 24 hours**.
10. Wait for the changes to be approved by the DNS system. Depending on the system’s TTL, it may take a few minutes or hours.
11. You can check the DKIM configuration status by clicking the “Check” button in the EmailLabs panel. If it changes to **"**&#x61;ccepte&#x64;**",** the authorization was correctly completed.

{% hint style="info" %}
Contact your hosting provider's Support Team for more detailed instructions if you need further assistance.
{% endhint %}


---

# 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.emaillabs.io/en/analytics-panel/administrator/sender-authorization/from-domain-authorization-configurator/authorizing-the-domain-hosted-by-cloudflare.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.