Email senders
Braze DMARC setup: how SPF and DKIM align
Braze handles SPF and DKIM on your sending domain, and DMARC is yours to publish. See how each one aligns and what to keep off your root SPF record.
SPF include for Braze
Braze does not need an SPF include on your domain.
DKIM for Braze
- Selectors
- Braze does not document this.
- How to enable it
- Records depend on the ESP behind your Braze account: two CNAMEs for SendGrid, one TXT for SparkPost, three CNAMEs for Amazon SES. Selectors vary, so copy the records Braze provides for your account.
Braze signs with your domain
Envelope-from and SPF alignment
SPF counts for DMARC only when this domain matches the domain in your From address. If it is Braze’s own domain, SPF can pass without aligning, and DMARC then depends on an aligned DKIM signature.
- Envelope-from (Return-Path)
- A dedicated Return-Path subdomain, such as bounce.mail.example.com
Sending ranges of Braze
Use these to recognize Braze in your reports. They change over time, so do not copy them into your SPF record.
Braze does not document this.
Does your domain authorize Braze?
Enter your domain. The SPF Checker reads your record and names the senders it authorizes.
Braze documentation
- Braze Docs: Email authentication
- checked 2026-11-09
- Braze Docs: Understanding DNS records
- checked 2026-11-09
- Braze Docs: Set up IPs and domains
- checked 2026-11-09
- Braze Docs: Verified domains
- checked 2026-11-09
- Braze Docs: Email self-serve
- checked 2026-11-09
- Braze Docs: Email guidelines
- checked 2026-11-09
Braze DMARC depends on a sending domain configured in Braze and a DMARC record you publish yourself.
How it authenticates
Braze configures SPF, which authorizes sending servers, on a dedicated Return-Path subdomain for bounces. A From domain of mail.example.com can use bounce.mail.example.com. They align in relaxed mode because both share example.com.
DKIM (DomainKeys Identified Mail) authenticates a message signature using a public key in DNS.
The records depend on the email service provider behind your account. Amazon SES, for example, also needs an MX record and an SPF TXT record on the bounce subdomain. You add the records Braze shows you, then select Verify. On Amazon SES you can instead delegate a subdomain with NS records, and Braze then manages its DNS.
DMARC is your job. Braze recommends publishing at the root domain to cover subdomains. If no policy exists, add this TXT at _dmarc.example.com. Otherwise, preserve your single existing record:
v=DMARC1; p=none; rua=mailto:dmarc@example.com
Read your reports before you move to a stricter policy.
What to watch for
Keep the From domain equal to your sending domain. Braze warns that a mismatch may cause SPF and DKIM misalignment.
Do not add include:sparkpostmail.com or include:amazonses.com to your root SPF for Braze. If another service of yours already needs one, leave it in place. Braze says these includes count heavily against the 10-lookup limit.
Copy each selector from your own setup, then test it with the DKIM checker. The values in Braze's DNS tables are examples.
If you delegate a subdomain, choose one that is not in use elsewhere and has no conflicting DNS records. Leave its records alone afterwards. Braze creates the sending domain under the delegated subdomain, so that domain needs at least three levels, like e.mail.example.com, and you cannot change it after you submit it.
With strict SPF alignment (aspf=s), a bounce subdomain stops aligning. DMARC can still pass through DKIM.