Brevo + Cloudflare + cPanel SMTP Setup Guide (Complete & Beginner-Friendly)
The definitive guide to correctly configure Brevo SMTP with Cloudflare DNS and cPanel — so your emails land in inbox, not spam. No technical background required.
Introduction: Why Email Setup Fails for Most Websites
Most website owners face at least one of these problems:
Emails going to spam
Contact form emails not arriving
Gmail showing security warnings
Emails working one day and failing the next
The Real Problem
In 90% of cases, the issue is not the email tool — it’s incorrect DNS or SMTP configuration.
This guide shows you exactly how to connect Brevo with Cloudflare DNS and cPanel SMTP, step by step, so your emails are:
Authenticated (SPF, DKIM, DMARC)
Trusted by Gmail, Outlook, Yahoo
Delivered to inbox, not spam
No technical background required.
How Brevo, Cloudflare, and cPanel Work Together (Concept First)
Before configuration, you must understand who does what.
Brevo
- Sends marketing & transactional emails
- Handles SMTP delivery
- Signs emails with DKIM
Cloudflare
- Controls DNS records
- Does NOT send emails
- Can break email if misconfigured
cPanel
- Hosts your website
- Handles email routing
- Connects your site to Brevo SMTP
Correct Flow
Website / Form
Brevo SMTP
Recipient Inbox ✓
Key insight: Cloudflare only tells inbox providers “Brevo is allowed to send for this domain.” It doesn’t send emails itself.
Step 1: Prepare Before You Start (IMPORTANT)
Before touching DNS, make sure:
You own the domain
Domain is active in Cloudflare
You have Brevo account access
You can access cPanel
📌 Golden Rule
Never rush DNS changes — mistakes cause email downtime.
Step 2: Add Sending Domain in Brevo
1
Log in to Brevo
2
Go to Settings → Senders & IP
3
Click Domains
4
Add your domain
Example: example.com
Brevo will generate:
Verification TXT
SPF record
DKIM records (TXT / CNAME)
⚠️ Do NOT click verify yet.
First add all DNS records in Cloudflare, then come back to verify.
Step 3: Cloudflare DNS Configuration (MOST CRITICAL PART)
Open: Cloudflare → Domain → DNS
3.1 Domain Verification TXT
Type: TXT
Name: example.com
Value: brevo-verification-code
TTL: Auto
Purpose: ✔ Proves you own the domain
3.2 SPF Record (VERY IMPORTANT)
Type: TXT
Name: example.com
Value: v=spf1 include:spf.brevo.com ~all
TTL: Auto
⚠️ SPF MERGE RULE
If SPF already exists, merge them:
v=spf1 include:oldprovider.com include:spf.brevo.com ~all
❌ Never create multiple SPF records
❌ Never delete existing providers blindly
3.3 DKIM Record (Email Authentication)
Brevo will give something like:
Type: TXT
Name: mail._domainkey.example.com
Value: DKIM-key-from-brevo
Or CNAME version. Purpose: ✔ Proves email is not modified ✔ Major spam-filter signal
3.4 Cloudflare Proxy Rule (NON-NEGOTIABLE)
For all email DNS records:
☁️
🔴 Orange Cloud = ❌ WRONG
☁️
⚪ Grey Cloud = ✅ CORRECT
Email MUST NOT be proxied by Cloudflare. This breaks email authentication.
Step 4: Verify Domain in Brevo
After adding DNS:
1
Go back to Brevo
2
Click Verify
3
Wait 5–20 minutes
You should see:
Status: Authenticated ✓
If not:
- • Clear Cloudflare cache
- • Re-check spelling
- • Wait up to 1 hour
Step 5: Generate Brevo SMTP Credentials
Go to: Brevo → SMTP & API
You’ll get:
SMTP Host: smtp-relay.brevo.com
Port: 587
Encryption: TLS
Username: Brevo login email
Password: SMTP Key
⚠️ SMTP Key ≠ account password
⚠️ Never share SMTP key publicly
Step 6: Configure cPanel for Remote SMTP
6.1 Email Routing
Go to: cPanel → Email Routing
Select:
Remote Mail Exchanger
Why? Because Brevo handles sending, not your server.
6.2 Create Sender Email (Identity Only)
Create:
no-reply@example.com
This inbox does NOT need to receive mail.
Purpose: ✔ Professional sender identity ✔ Better deliverability
Step 7: Connect Website / WordPress to Brevo SMTP
If WordPress Website
Recommended plugins:
WP Mail SMTP
Fluent SMTP
Choose: Other SMTP
Fill details:
SMTP Host: smtp-relay.brevo.com
Port: 587
Encryption: TLS
Username: Brevo login email
Password: SMTP Key
From Email: no-reply@example.com
From Name: Your Brand Name
→ Send test email to confirm it works.
Step 8: Add DMARC (HIGHLY RECOMMENDED)
DMARC improves trust and visibility.
Type: TXT
Name: _dmarc.example.com
Value: v=DMARC1; p=none; rua=mailto:dmarc@example.com;
Benefits:
Better inbox placement
Spam reporting
Protection from spoofing
Common Problems & Exact Fixes
❌ Emails Going to Spam
Fix:
- SPF merged correctly?
- DKIM verified?
- Same domain used in From email?
❌ SMTP Not Sending
Fix:
- Port = 587
- TLS enabled
- SMTP key used (not password)
❌ Gmail “Be Careful” Warning
Fix:
- Add DMARC
- Avoid free sender emails
- Warm up domain
Email Warm-Up Best Practice (DO THIS)
Day 1–2 → 20 emails
Day 3–4 → 50 emails
Day 5–7 → 100 emails
Increase slowly
Never send bulk emails on day one.
Best Practices for Long-Term Deliverability
Use branded sender email
Send valuable content
Avoid spammy words
Clean inactive subscribers
Monitor bounce rates
Final Checklist (SAVE THIS)
Brevo domain authenticated
SPF merged correctly
DKIM active
DMARC added
Cloudflare proxy OFF
SMTP connected
Test email successful
Final Thoughts
Correct email setup is not optional anymore.
If you:
Authenticate your domain
Configure DNS properly
Use SMTP correctly
Your emails will land in inbox, not spam. ✓
Ready to Start Sending?
Brevo offers a free plan with 300 emails/day — perfect for testing your new email setup.
Get Started with Brevo Free
FAQs (Schema-Ready)
Does Cloudflare block emails?
No, unless email records are proxied. Always ensure email-related DNS records (SPF, DKIM, DMARC, MX) have the orange cloud OFF (grey cloud = DNS only).
Is Brevo SMTP free?
Yes, SMTP is included in all Brevo plans including the free tier. You get 300 emails/day on the free plan.
Do I need cPanel email inbox?
No, only sender identity is required. You don’t need to receive emails at that address — it’s just used as the ‘From’ address for better deliverability.
Is DMARC mandatory?
Not mandatory but strongly recommended. DMARC improves deliverability, provides reporting on email authentication, and protects your domain from spoofing.
Why are my emails going to spam?
Common causes: missing or incorrect SPF/DKIM records, no DMARC policy, using a different domain in ‘From’ email than your authenticated domain, or sending bulk emails without warming up your domain first.
What’s the difference between SMTP key and API key?
SMTP key is specifically for email sending via SMTP protocol (used in WordPress plugins). API key is for programmatic access to Brevo’s full API. For SMTP configuration, always use the SMTP key.