SPF record for Brevo
Type: TXT
Host/Name:
@
Value: v=spf1 include:spf.brevo.com ~all
Jump to section
Before you start
- You need access to the DNS settings for your domain. This is usually at your domain registrar or DNS provider (Cloudflare, Namecheap, GoDaddy, etc.).
- You need admin or settings access to your Brevo account to generate DKIM keys and verify records.
- DNS changes take time to propagate. After saving a record, wait at least 15-30 minutes before testing.
SPF Setup for Brevo
SPF (Sender Policy Framework) is a DNS TXT record that lists which mail servers are allowed to send email on behalf of your domain. Receiving servers check it to decide whether to accept or flag your mail.
Brevo provides all DNS records after you add and verify your domain in Account settings. The SPF record value comes from Brevo's authentication page for your domain.
Steps
- Open your DNS provider and look for an existing TXT record at host
@that starts withv=spf1. - If one exists, edit it and add the new include. Never create a second SPF record. If none exists, create a new TXT record at
@with the value above. - If you send through Brevo and another platform, add both includes in a single record:
v=spf1 include:spf.brevo.com include:_spf.google.com ~all - Use
~all(softfail) while testing. Move to-all(hardfail) only after confirming all legitimate senders are covered. - Save and wait for DNS propagation.
Watch out: Brevo takes up to 24-48 hours to verify records after they are published. Wait for DNS propagation before clicking Authenticate.
DKIM Setup for Brevo
DKIM (DomainKeys Identified Mail) adds a cryptographic signature to outgoing email. Receiving servers verify the signature against a public key you publish as a DNS TXT record. A valid DKIM signature proves the message was not altered in transit and that it came from an authorized sender.
Selector for Brevo: generated by Brevo when you add your domain (shown in Senders & IPs settings)
Steps
- In Brevo, go to Account settings → Senders & IPs → Domains → Add a domain.
- After adding your domain, Brevo shows the SPF, DKIM, and DMARC records you need to publish.
- Add the DKIM TXT record at the host Brevo specifies in your DNS provider.
- Return to Brevo and click Authenticate. Brevo verifies all three records together.
Watch out: Do not click Authenticate before DNS records have propagated. Brevo's verification checks all records at once and fails if any are missing.
Verify DKIM
- Send a test email to a Gmail address and open it. Click the three-dot menu → "Show original". Look for
dkim=passin the authentication results. -
From the command line:
dig TXT mail._domainkey.yourdomain.com +short
- Or use the InboxGreen DKIM checker.
DMARC Setup for Brevo
DMARC (Domain-based Message Authentication, Reporting, and Conformance) ties SPF and DKIM together. It tells receiving servers what to do with mail that fails both checks, and sends you reports about who is sending email on behalf of your domain. DMARC also requires alignment: the domain in your visible From header must match the domain authenticated by SPF or DKIM.
Brevo's domain authentication creates proper DKIM alignment. Run DMARC at p=none for 2-4 weeks and review reports before increasing the policy.
The three-stage approach
| Stage | DNS value | When to use it |
|---|---|---|
| Monitor | v=DMARC1; p=none; rua=mailto:[email protected]; fo=1 |
Start here. Collects reports without blocking any mail. |
| Quarantine | v=DMARC1; p=quarantine; pct=25; rua=mailto:[email protected]; fo=1 |
After 2-4 weeks at p=none with clean reports. Sends some failing mail to spam. |
| Reject | v=DMARC1; p=reject; pct=100; rua=mailto:[email protected]; fo=1 |
Full protection once SPF and DKIM alignment is verified. |
Publish the DMARC record
- Create a TXT record at host
_dmarc(not@) with the p=none value above. - Replace
[email protected]with a real inbox that can receive XML report emails. - Wait for DNS propagation, then verify with
dig TXT _dmarc.yourdomain.com +short. - After 2-4 weeks, review the reports and tighten the policy when alignment looks healthy.
Why DMARC fails even when SPF and DKIM pass: DMARC cares about alignment. The domain
in the visible From header must match the domain SPF or DKIM authenticated. Forwarded mail and
mailing list services often break alignment.
List-Unsubscribe for Brevo
The List-Unsubscribe header gives inbox providers like Gmail and Outlook a machine-readable way to offer a one-click unsubscribe button. When it is present and valid, Gmail shows an "Unsubscribe" link next to the sender name without the recipient needing to scroll to the bottom of the email. This reduces spam complaints and protects your sender reputation.
How to enable it
- In your sending platform or email template, enable the List-Unsubscribe header option. Most platforms (SendGrid, Mailgun, Brevo, Shopify Email) have a toggle or a macro for this.
- Use a one-click HTTPS unsubscribe URL as the primary method. Include a
mailto:address as fallback. - Add the
List-Unsubscribe-Postheader to declare one-click support (required by Gmail's February 2024 guidelines for senders above 5,000 messages/day).
Example headers
List-Unsubscribe: <https://yourdomain.com/unsubscribe/TOKEN>, <mailto:[email protected]?subject=unsubscribe> List-Unsubscribe-Post: List-Unsubscribe=One-Click
Common mistakes
- Using a broken or expired token in the unsubscribe URL. Inbox providers test the link periodically.
- Only providing a
mailto:link without a one-click HTTPS URL. Gmail and Outlook prefer the HTTPS method. - Not honoring the unsubscribe request immediately. Gmail requires that one-click unsubscribes are processed within two business days.
To verify, send a test email to a Gmail address and look at "Show original". You should see the List-Unsubscribe header in the raw message headers.
Verify All Four Records
After publishing all records, run these checks:
| Record | Command | What to look for |
|---|---|---|
| SPF | dig TXT yourdomain.com +short |
One TXT record starting with v=spf1 |
| DKIM | dig TXT mail._domainkey.yourdomain.com +short |
A TXT record starting with v=DKIM1 |
| DMARC | dig TXT _dmarc.yourdomain.com +short |
A TXT record starting with v=DMARC1 |
| All three | InboxGreen Free Check | Green pass on SPF, DKIM, and DMARC |
Common Mistakes with Brevo
- Clicking Authenticate before DNS records have propagated, causing verification to fail.
- Creating two SPF TXT records instead of adding Brevo's include to the existing record.
- Sending from an unverified domain. Brevo blocks sending from domains that have not completed authentication.
Free Deliverability Scan
Check SPF, DKIM, DMARC and List-Unsubscribe for your domain in seconds.
Related Tools
See your live SPF record, count DNS lookups, and spot duplicate records or syntax problems.
Look up any DKIM selector on any domain. Confirms the key exists and shows its length.
Fetch your live DMARC record, validate syntax, and check policy and reporting configuration.
Paste raw email headers to see SPF, DKIM, and DMARC results in one view.
Build a valid SPF record from scratch for any combination of sending services.
Build a DMARC record with the right policy, pct, and rua settings for your stage.
See all TXT records on your domain to catch duplicate SPF records or missing entries.
Generate a 2048-bit DKIM key pair if your ESP requires you to manage your own keys.
Related Reading
PermError, duplicate records, softfail vs hardfail, and alignment failures.
Selector not found, body hash mismatch, key length, and DMARC alignment.
Alignment failures, missing reports, and how to safely move from p=none to p=reject.
Common Questions
What DNS records do I need for Brevo?
For Brevo, find the DNS records in Account settings, then Senders and IPs, then Domains. SPF uses v=spf1 include:spf.brevo.com ~all, and Brevo provides the DKIM TXT record value in the same panel. After publishing all records, click Authenticate in Brevo to verify them. Allow up to 48 hours for DNS propagation before verifying.
How long does it take for SPF, DKIM, and DMARC to start working?
Most DNS changes propagate within 15 to 60 minutes, but the full TTL can extend to 48 hours on some registrars. Always wait at least 30 minutes before testing. If a change isn't showing up after an hour, use the SPF Lookup or DKIM Checker to query live DNS rather than relying on cached results.
Can I have two SPF records?
No. RFC 7208 requires exactly one SPF TXT record at your domain root. Two records cause a PermError regardless of their content. If you send through multiple services, merge all the includes into a single record: v=spf1 include:service1.com include:service2.com ~all. Use the TXT Lookup to confirm you only have one.
What DMARC policy should I start with?
Start with p=none to collect reports without affecting delivery. After 2 to 4 weeks of reports showing all legitimate sources passing alignment, move to p=quarantine at a low percentage (pct=10), then increase gradually. Move to p=reject only when you are confident every legitimate sending source aligns correctly.
Why does DMARC fail even though SPF and DKIM both pass?
DMARC requires alignment, not just a pass. SPF alignment means the envelope sender domain (the Return-Path address) must match your From: domain. DKIM alignment means the d= tag must match your From: domain. If your ESP signs with its own domain or uses its own envelope sender, both protocols pass independently but DMARC alignment fails. Fix this by enabling custom domain authentication at your ESP.