Branded sender identity
Instead of sending from a generic address, you can use professional sender addresses tied to your own domain. This improves consistency across landing pages, outreach emails, and campaign flows.
Brevo Email Infrastructure Guide
Authenticate your sending domain in Brevo the right way
This guide explains how to connect and authenticate a custom sending domain in Brevo by publishing the required DNS records. A correctly configured domain helps you send marketing emails with a branded identity and a more reliable technical setup.
Why domain authentication matters
A verified sender domain helps align your email infrastructure with your brand and gives email providers clearer signals about who is allowed to send on behalf of that domain. It also reduces setup friction when you want to run campaigns through a dedicated sending environment.
Better technical alignment
DNS authentication records make it easier for mailbox providers to validate that your sending platform is authorized to deliver emails for your domain.
Cleaner email operations
Many marketers and businesses prefer using a dedicated domain or subdomain for campaigns so that promotional activity stays organized and easier to manage.
Typical DNS records used in Brevo
Brevo normally generates the exact DNS entries needed for your account and domain. The values below are example formats only, so you should always copy the live values shown in your own Brevo dashboard.
| Record Type | Purpose | Host / Name | Value Format |
|---|---|---|---|
| TXT | Brevo domain verification code | brevo-code.yourdomain.com |
brevo-code:xxxxxxxxxxxxxxxxxxxxxxxx |
| TXT | DKIM signature key | mail._domainkey.yourdomain.com |
v=DKIM1; k=rsa; p=YOUR_PUBLIC_KEY |
| TXT | DMARC policy | _dmarc.yourdomain.com |
v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com |
| TXT | SPF authorization | @ or root domain |
v=spf1 include:spf.brevo.com ~all |
include:spf.brevo.com
If your domain already has an SPF record, do not create a second SPF TXT record. Instead, merge the Brevo include value into the existing SPF record so the domain keeps a single valid SPF policy.
Step-by-step setup
Follow these steps to authenticate your sending domain and complete the Brevo verification process in a clean and structured way.
1
Open Brevo domain settings
Log into your Brevo account, go to the sender and domain settings area, and open the section where you can add a custom sending domain.
2
Add the domain you want to use
Enter the domain that will be used for your marketing emails or sender identities. After saving it, Brevo will generate the DNS records required for verification.
3
Open your DNS manager
Sign in to the provider that manages your DNS zone, such as Cloudflare, Namecheap, GoDaddy, DirectAdmin, or another registrar or hosting panel.
4
Add the verification and authentication records
Publish the TXT records exactly as provided. This usually includes the Brevo verification code, the DKIM record, the DMARC record, and an SPF configuration or SPF update.
5
Check SPF carefully
If an SPF record already exists on the domain, edit that existing record rather than adding a second one. The final domain should have one SPF TXT record with all required includes merged correctly.
6
Return to Brevo and verify
Go back to Brevo and run the authentication check. If the records are correct and propagation has completed, Brevo should confirm the domain as authenticated.
Important practical tips
Allow time for DNS propagation
DNS changes may appear quickly, but some providers take longer to update globally. If verification fails right after you add the records, wait and test again later.
Start with a monitoring DMARC policy
A monitoring policy can help you observe traffic before moving to stricter enforcement. Once your sending sources are confirmed and stable, you can harden the policy.
Use external checking tools
After Brevo shows the domain as authenticated, it is still useful to validate the published SPF, DKIM, and DMARC records through independent lookup tools.
Separate campaign infrastructure when needed
If you send newsletters, cold outreach, or multiple brand campaigns, consider using a dedicated domain or subdomain so your email operations stay clean and easier to manage.
Example host values: mail._domainkey _dmarc @
The safest approach is to copy each DNS record exactly as shown by Brevo, publish it in your DNS panel, wait for propagation, and only then start using the domain for live email campaigns.
Common mistakes to avoid
Creating two SPF records
This is one of the most common DNS mistakes in email setup. The domain should keep a single SPF TXT record that includes all authorized senders.
Publishing records on the wrong host
Small differences in the host field can break validation. Double-check whether the DNS manager expects a full hostname or only the prefix.
Pasting broken DKIM values
Long DKIM public keys should be copied completely and without hidden line breaks or missing characters.
Testing too early
Even if the records are correct, DNS propagation may still be in progress. Give the changes enough time before assuming the setup failed.
Frequently asked questions
Can I use the root domain instead of a subdomain?
Yes, in many cases you can use the main domain, but some senders prefer a dedicated subdomain for better separation between website identity and campaign infrastructure.
What if my DNS provider formats hostnames differently?
Some DNS panels want only the prefix, while others auto-append the domain. Review the final saved hostname carefully after creating each record.
Should I use DMARC immediately?
Yes, but many users begin with a softer monitoring policy first and move to stricter enforcement after confirming that valid email traffic is authenticating correctly.
When can I start sending campaigns?
Start after Brevo confirms authentication and after you have checked that the domain records are published correctly and consistently.
Contact
Contact ontiscal.com if you want to rent quality and aged domain names configured through custom DNS records working for email platforms like Resend or Brevo.