Email provider

DKIM setup for Brevo

DKIM proves message integrity. Brevo gives you a selector and key or CNAME targets — publish them exactly.

Common mistake: Old Sendinblue DNS snippets cached — always copy current records from Brevo’s domain authentication page.

Step by step

Step 1 Brevo → Senders & IPDomains → authenticate your domain.
Step 2 Copy the exact hostnames and values Brevo shows — do not invent selectors. Typical pattern:
TXT at mail._domainkey (Brevo may also show a record name like brevo._domainkey — use their live values).
Step 3 Add TXT or CNAME at the DNS provider that hosts your domain. Truncated keys fail verification.
Step 4 Query the record from an authoritative resolver or use propagation checker.
Step 5 Google Workspace / some hosts require clicking “enable” after DNS is green.
Step 6 Send a test message; check DKIM-Signature and d=. Run DNS Preflight. Align with DMARC: /fix/dmarc/.

DNS Preflight — verify SPF, DKIM, DMARC in one pass.

Open DNS Preflight →

DMARC alignment — fixes when reports show failures.

DMARC fix guides →

FAQ

Where do I find Brevo DKIM records?

In the provider’s domain authentication / sender settings — copy live values.

CNAME vs TXT?

Use what the provider specifies — both are common.

Why dkim=fail?

Wrong selector, truncated key, or signing not enabled after publish.

Does this fix DMARC?

You need SPF + DKIM alignment for your From domain — DKIM is often the easier path for ESPs.

How to verify?

DNS Preflight for the published key; send test mail for header verification.