SPF and DKIM by provider

SPF record for Brevo

Last updated 2026-08-26

Brevo sends campaigns, automations and transactional mail. Here is what to publish so it can do that as your domain, and what has to line up before DMARC will pass.

The SPF record

Add one mechanism to the SPF record on your sending domain:

In a complete record, alongside Google Workspace, that looks like:

Brevo shows the current include on the Senders, Domains screen, and when I last checked it was this one. Accounts set up under the Sendinblue name may still carry include:spf.sendinblue.com, which continues to resolve. Do not keep both: that is a wasted lookup for nothing.

Then count your lookups. SPF allows ten DNS-querying mechanisms across the entire nested chain, and the eleventh turns the record into a permerror that authorises nothing. The record still reads correctly to a human while every check fails. Run the domain through the SPF checker after every change, because the number moves when your providers change their own records, not just when you change yours.

DKIM

Brevo hands you a DKIM TXT record and a separate verification TXT record for the domain, and it names both on the authentication screen. Publish them, press the verify button, and check the tick appears against the domain rather than assuming the DNS change was enough.

DMARC alignment with Brevo

DMARC passes when SPF or DKIM passes and the domain it authenticated matches the domain in your visible From address. A provider can pass both checks for its own domain and leave you failing. These are the Brevo specifics:

• Free and low-tier accounts share sending infrastructure. Authentication makes your mail align, and it does not isolate you from the neighbours' reputation.
• Brevo appends its own footer on the free plan. That happens before signing, so it does not break DKIM, but it does put someone else's branding in your mail.
• Transactional and marketing traffic share the domain unless you separate them onto subdomains, which is the same advice as everywhere else on this site and still worth doing.

The general case is covered in alignment, explained, and the header you read to prove it is on the dmarc=fail page.

Verify it

Substitute your domain, and run these after the TTL on anything you replaced has expired:

Then send one message through Brevo to a Gmail address you control, open Show original, and look for dkim=pass with your domain in header.i. That single check is worth more than any number of DNS lookups, because it tests the thing receivers actually do.

Our SPF checker gives you the lookup count, the DKIM checker confirms a selector resolves and the key is long enough, and the DMARC checker reads your policy back to you. All three are free and none of them ask for an account.

Values here were checked against Brevo's own documentation, at Brevo help centre. Providers change DNS requirements without much announcement, so if their screen disagrees with this page, believe their screen and tell us.

A record can read correctly and still fail alignment once real mail moves through it. Receivers write that verdict into the reports they send. We read them for you, and paid plans email you the same day one names a new sender that failed, instead of holding it for Monday. See whether this sender passes. Your first domain is free.