> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cliqo.io/llms.txt
> Use this file to discover all available pages before exploring further.

# How to set up your sending domain (DNS)

> Authorize Cliqo to send from your domain: DKIM, SPF and DMARC, with guided verification.

## What you will learn

How to authorize Cliqo to send email from your domain, so Gmail, Outlook and Yahoo recognize you as a legitimate sender.

## Before you start

* Access to your domain's DNS panel (Registro.br, Locaweb, GoDaddy, Cloudflare or another provider).
* The **Admin** or **Owner** role on the account.

## Step 1 · Enter your domain

1. Go to **Settings › Domain**.
2. Type the domain that will sign your emails (e.g. `suamarca.com.br`) and click **Confirm** to generate the records.

## Step 2 · Choose your DNS provider

Select your provider — **RegistroBR**, **Locaweb/cPanel**, **GoDaddy**, **Cloudflare** or **Other** — and the screen shows a **Guide for…** link to that provider's help pages. **Other** has no guide: follow your provider's own help.

## Step 3 · Add the records

Copy each record's name and value with the **Copy** button and create it in your DNS. The screen tells you how many records are required; the rest carry the **optional** tag:

| Record | What it's for |
| - | - |
| **DKIM 1, 2 and 3** (3 CNAMEs) | Cryptographic signature that proves the email is yours. **This is the essential one** — DKIM is what authenticates your sends and gets the domain verified. |
| **Return-Path (MX)** and **Return-Path (SPF)** (TXT) | Both live on a return subdomain — the screen shows the exact name (for example, `e.suamarca.com.br`). They route bounces back to Cliqo and authorize sending on behalf of the domain. For the MX, also fill in the **Priority** shown. |
| **Root-domain SPF** (TXT, optional — the screen labels it "SPF (raiz, opcional)") | SPF on your main domain. It's optional: the SPF that authenticates Cliqo's sending is the Return-Path one. |
| **DMARC** (TXT, optional) | Authentication policy and reporting. The screen suggests `p=none`, which is sufficient — including for the AMP registration. |

> **Already have an SPF record on your main domain?** If you add the root SPF, don't create a second one — two SPF records invalidate both. **Edit the existing one** and add `include:amazonses.com` on the same line.

## Step 4 · Verify

1. Click **Verify records**. Each row shows **verified** or **not found**.
2. Propagation can take **up to 48 hours**. Partial records are normal at first — come back and verify again.
3. Once the records are published, the domain badge may sit at **Confirming…** or **Finalizing…** for a while: the DNS is already right and the sending provider still has to confirm DKIM. The badge changes to **Verified** when that confirmation arrives.

## Result

The domain shows as **Verified**, the "DKIM inactive" warning disappears from campaign setup, and the Needs attention bell stops listing the domain. From then on you can send from **any address** on the verified domain (ofertas@, news@, contato@…).

## Common problems

* **"Not found" after 48 h** — check that the record was created on the right domain (without duplicating the domain in the record name, a common mistake in some panels) and that there are no extra spaces in the pasted value.
* **DKIM won't verify** — the 3 CNAMEs must exist exactly as generated; some panels append the domain to the end automatically.

## Next steps

* [Checklist before your first send](https://docs.cliqo.io/en/entregabilidade/checklist-primeiro-envio.md)
* [How to register your sender for AMP emails](https://docs.cliqo.io/en/email-interativo/registro-do-remetente.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.