DMARC, SPF and DKIM for Brevo

Updated 2026-11-14

Brevo is an email platform; its developer docs cover sending transactional mail through its API or its SMTP relay. You add your domain in Brevo, publish the records it returns at your DNS host and then authenticate the domain. DMARC is a record you publish yourself. This guide follows Brevo's developer documentation only, so console steps described only in Brevo's help center are left out or marked as undocumented. For the background on each standard, see SPF explained, DKIM explained and DMARC explained.

What Brevo sends from

The visible From address is a sender you create in Brevo, for example [email protected]. The Senders API calls this field the "From email to use for the sender" and says "A verification email will be sent to this address." Brevo's transactional email guide says the sender "must be registered and verified".

For the domain, the configuration endpoint returns verified and authenticated as separate true or false values. In our reading, verification proves that you own the domain. The docs mix the two terms: a box headed "How to get your domain verified?" goes on to list "Three ways to authenticate your domain": add "the Brevo record" in DNS, "Host a file in the root directory of the domain", or "Send an email containing a verification code". For the DNS route you then "configure the remaining DNS records". In our reading those are the DKIM record and the suggested DMARC record, since the API lists all three as required and its "Fully authenticated" example shows DMARC with status true. The docs do not say whether authentication requires DMARC.

The envelope sender (Return-Path, also called MAIL FROM or bounce address) is not documented in Brevo's developer docs, and neither is a custom Return-Path. That matters for SPF; see below.

Subdomains: the create-domain reference has an example called "Create a subdomain" that adds newsletter.mycompany.com. Its sample response gives domain_name as mycompany.com, which we read as a slip. Add each sending subdomain as its own domain.

SPF

SPF is checked on the Return-Path domain, which Brevo's developer docs do not document.

The docs contradict each other on whether you publish SPF at all. As of November 2026 the Domains API documents exactly three records: brevo_code, dkim_record and dmarc_record. There is no SPF entry. But the Supabase integration guide tells you to add "the SPF and DKIM DNS records Brevo provides", and the Senders API returns an spfError flag ("true = SPF not well configured"). None of these pages shows an SPF value or a Brevo include, so we print none.

Our advice: if the Brevo app shows you an SPF value, add it to your existing record on example.com instead of creating a second one. Your root domain still needs SPF for services that use example.com in the Return-Path, such as your mailbox provider. A typical record looks like this, where include:_spf.example.net is a placeholder for "another service":

example.com TXT v=spf1 include:_spf.example.net ~all

This record uses 1 DNS lookup in the record itself. The include adds its own nested lookups; for any Brevo include you add, Brevo does not document how many. The limit is 10 lookups for the whole tree (RFC 7208), and the SPF lookup counter counts it. See also too many SPF lookups and multiple SPF records.

End the record with ~all. RFC 9989 warns that -all "could cause a message to be rejected early in the SMTP transaction, before any DMARC processing takes place", even for mail with an aligned DKIM signature.

DKIM

Brevo DKIM is a TXT record under your domain. As of November 2026, every example in the developer docs uses the host name mail._domainkey, which makes the selector mail:

mail._domainkey.example.com TXT v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GN...

The value above is Brevo's own truncated placeholder. Copy the exact value from the Brevo response or app. The examples differ in detail, and the docs do not explain why. The API reference shows v=DKIM1; k=rsa; p=... with host name mail._domainkey. The guide pages show k=rsa;p=... without v=DKIM1 and with host name mail._domainkey. (trailing dot). Enter exactly what Brevo gives you for your domain, and see Common mistakes if your DNS host appends the domain.

The same split exists for the verification record. The API reference shows brevo-code=abc123def456 with host name @. The guide pages show a brevo-code:<hex> value (for example brevo-code:e760f020e6d438149540cfc757e99b5a) with an empty host name. In our reading both mean the root of the domain; copy the exact value Brevo returns:

example.com TXT brevo-code=abc123def456

Brevo's developer docs do not state the DKIM key length, do not document key rotation, and do not say whether mail from an unauthenticated domain is signed with another domain. Check the key you publish with our checker (DKIM not found lists what happens when the selector has no key).

DMARC alignment

DMARC passes when SPF or DKIM passes and that result aligns with the From domain. SPF alignment compares the Return-Path (RFC5321.MailFrom) domain with the From domain. DKIM alignment compares the signature's d= domain with the From domain. Relaxed alignment, the default, means both are in the same organisational domain. Strict alignment (aspf=s, adkim=s) means the domains must be identical.

DKIM is the documented route. The key lives at mail._domainkey.example.com, so in our reading a signature that verifies with it carries d=example.com and aligns under both relaxed and strict alignment. Brevo's developer docs do not print a sample DKIM-Signature header, so this is our reading.

SPF alignment is not documented. Brevo's developer docs do not say what the Return-Path domain is, so we cannot tell you whether SPF aligns. Send a test mail to a mailbox you control and read the headers: look at Return-Path, at d= in DKIM-Signature, and at dmarc= in Authentication-Results. If the Return-Path is not under example.com (and under aspf=s it must be exactly example.com), SPF does not align and DKIM alone carries DMARC. That is enough.

The error list in the API reference includes "DMARC policy requires domain authentication". The docs do not explain when Brevo returns it.

Step by step to p=reject

  1. Add the domain in Brevo. In the app, open Senders, Domains & Dedicated IPs and add the domain, or send POST https://api.brevo.com/v3/senders/domains with {"name": "example.com"}, and note the DNS records Brevo returns.
  2. Publish the Brevo code and DKIM records. At your DNS host, create the brevo_code TXT record at the root and the DKIM TXT record at mail._domainkey, with the exact values Brevo shows you.
  3. Authenticate the domain. Authenticate in the app or send PUT https://api.brevo.com/v3/senders/domains/example.com/authenticate, then confirm with GET https://api.brevo.com/v3/senders/domains/example.com that verified and authenticated are both true; Brevo's Supabase guide says authentication "can take up to 24-48 hours to propagate". If authentication does not complete, publishing the step 5 p=none record early is harmless.
  4. Check SPF on the root domain. Keep one SPF record on example.com ending in ~all, merge in any SPF value the Brevo app shows you, and stay under 10 DNS lookups in total.
  5. Publish DMARC with p=none and a report address. Add a TXT record at _dmarc.example.com with v=DMARC1; p=none; rua=mailto:[email protected], which asks receivers for aggregate reports without changing delivery.
  6. Read the reports and fix other senders. Watch the reports for a few weeks, confirm that Brevo mail passes DKIM with d=example.com, and give every other legitimate sender aligned DKIM or SPF before you tighten the policy.
  7. Move to p=quarantine. Change the policy to p=quarantine and keep reading reports, because failing mail now goes to spam and a sender you missed shows up quickly.
  8. Move to p=reject. When the reports show only legitimate mail passing and nothing legitimate failing, change the policy to p=reject.

The record for step 5:

_dmarc.example.com TXT v=DMARC1; p=none; rua=mailto:[email protected]

That record triggers our DMARC policy none note on purpose; it is the monitoring stage. The final record:

_dmarc.example.com TXT v=DMARC1; p=reject; rua=mailto:[email protected]

Brevo's examples suggest the same first step with rua=mailto:[email protected]; use a report address you read. Some receivers support pct (RFC 7489) or t=y (RFC 9989), but RFC 7489 says "unknown tags MUST be ignored", so a receiver may apply p=reject; t=y as a full reject. Do not treat either tag as a safety net (partial pct).

Common mistakes

  • Copying the DKIM value from another page. The docs show two forms of the key record and two forms of the Brevo code. Copy the exact values Brevo returns for your domain.
  • Domain added twice. If your DNS host appends the domain, mail._domainkey.example.com becomes mail._domainkey.example.com.example.com. Enter only the host part.
  • Mismatched records. The authenticate endpoint answers 400 on "a value mismatch between DKIM records and the Brevo code". Check both records before you retry.
  • A second SPF record. One name may have only one SPF record (RFC 7208). Merge any value into the existing record.
  • Relying on SPF alignment. The Return-Path domain is not documented. Check a test mail's headers before you count on SPF for DMARC.
  • Forgetting subdomains. A sender on news.example.com needs that name added and authenticated in Brevo.
  • A second DMARC record. If you already have DMARC, change it instead of adding Brevo's suggested record next to it (multiple DMARC records).
  • No report address. Without rua you cannot see what fails (DMARC without rua).

How to check it

Run the email security check on example.com to read SPF, DKIM and DMARC together. Use the SPF lookup counter on your root domain to count the full lookup tree, including any include you added for Brevo. Enter the selector mail in the DKIM selector finder to confirm that the key at mail._domainkey.example.com is published. Build your policy with the DMARC record generator. Brevo's own check is the domain configuration endpoint: each record has a status that says "Whether the record is properly configured".

Frequently asked questions

Which DNS records does Brevo ask for?

As of November 2026 the Domains API documents three TXT records for a new domain: a Brevo code (brevo_code) for verification, a DKIM record at mail._domainkey and a DMARC record at _dmarc. Brevo's developer docs show no SPF record in that list.

Do I need to add Brevo to my SPF record?

Brevo's developer docs do not say. The Domains API lists no SPF record, but a Supabase integration page tells you to add "the SPF and DKIM DNS records Brevo provides". Copy whatever SPF value the Brevo app shows you, merge it into your one existing SPF record, and rely on DKIM for DMARC.

What is the Brevo DKIM selector?

In every developer docs example the DKIM host name is mail._domainkey, so the selector is mail and the record is a TXT record under your domain. The docs do not say whether every account gets the same selector, so use the host name Brevo shows you.

Does Brevo publish DMARC for me?

No. Brevo suggests a DMARC record, v=DMARC1; p=none; rua=mailto:[email protected] at _dmarc in its examples, but you publish it at your DNS host and replace the report address with one you read.

Sources