---
title: "The DNS records we ask for — and why only DKIM is required"
description: "DKIM is the only required record. SPF is a merge instruction, DMARC is advisory, and both are written that way on purpose."
url: https://help.mails.ai/en/articles/14-the-dns-records-we-ask-for-—-and-why-only-dkim-is-required
collection: "Your own domain"
updated: 2026-10-10
language: en
---

# The DNS records we ask for — and why only DKIM is required

DKIM is the only required record. SPF is a merge instruction, DMARC is advisory, and both are written that way on purpose.

![Mails.ai — The DNS records we ask for — and why only DKIM is required](https://staticfiles.gleap.io/p6a77ce6bbe980ea9dbca1955/2rt0YPAcSBPWS4WI3aiNYIPY5sVt5CmE7sFtzyWcx1PnfQS8FlcRAFW7Ca9WAWSRfggRilOlhyj.png)

Adding a domain returns three records. Only the first is required, and the reason the other two are worded carefully is that a naive version of them can break mail you already send.

![A new domain's three DNS records: DKIM required and still pending, SPF and DMARC recommended, each with its instruction](https://staticfiles.gleap.io/p6a77ce6bbe980ea9dbca1955/HET4E8pf2m2UvGoP4yYBU5mJnfxiYNXQAeeEi5WEJRjfHKFmiwmpffL051T7bm9PfKaDUPfVYwj.png)

## DKIM — required

A `TXT` record carrying a public key generated for your domain alone. This is what actually authenticates your mail: our envelope sender is always our own bounce domain, so DMARC aligns through DKIM, not SPF. Publish this one and you are done.

## SPF — a merge, never a replace

If you already publish SPF (and with Google Workspace or Microsoft 365 you do), adding a second `v=spf1` record at your apex **breaks your existing mail**. So the SPF row comes with a merge instruction and a `merge_token`: the one `ip4:` entry to add to the record you already have, before its final `~all` or `-all`. Publish the full value shown only if you have no SPF record at all. SPF is optional either way, because your mail authenticates through DKIM.

## DMARC — advisory

We suggest a DMARC policy and we point `rua` at **your** address, not ours. A vendor that hands you `p=none; rua=mailto:vendor.com` has quietly downgraded your policy and taken your reports. If you already publish DMARC, leave it exactly as it is.

> The rule behind all three: a record we ask you to publish must never be able to damage mail that has nothing to do with us.

[Add your domain](https://app.mails.ai/domains)
