How to Verify Domains in Brevo Easily 2026
By Impran M NLast checked against official docs
Domain authentication is no longer optional for email marketing. Gmail, Yahoo, and Microsoft all filter or flag mail from unverified domains, and Brevo builds the whole process around adding a small set of DNS records to prove you own the domain you're sending from.
The setting lives in general account settings, not anywhere marketing-related, and the records themselves are specific enough that a typo or the wrong record type breaks verification without an obvious error message. This guide covers where to find the setting and what the underlying DNS records look like, based on Brevo's own help documentation.
Before you start
- Access to your domain's DNS zone editor, through your registrar or whichever service hosts your DNS
01Find domains under account settings
Domain verification isn't under Campaigns or Contacts. It's filed under Settings, in the Organization settings block alongside Users, SMTP & API, and Security.
Brevo's settings sidebar groups it as "Senders, domains, IPs," easy to scroll past if you're expecting it under a marketing-labeled menu. Click into that section to reach the Domains tab, where you add and manage your sending domains.

02Add your domain
In the Domains tab, click Add a domain and enter your root domain, just the domain itself, like yourcompany.com, with no https:// prefix and no trailing path. Save it to move into the verification options.
03Pick automatic or manual authentication
Brevo offers two routes. Automatic authentication signs into your domain registrar directly and lets Brevo add the required DNS entries for you, faster if your registrar is one of the supported partners. The manual route generates the record values so you can add them yourself through your host's DNS zone editor, useful if your registrar isn't supported for automatic setup, or if DNS is managed by someone else on your team.
04Know what the DNS records are
Two records matter here: a Brevo code that proves ownership, and a DKIM record that lets receiving mail servers confirm your messages weren't altered in transit. The Brevo code is always a single TXT record.
DKIM is where accounts differ: Brevo's current default sets up two CNAME records, typically named mail._domainkey and mail2._domainkey, that point at Brevo's own signing infrastructure and rotate their keys automatically without you touching DNS again. Some accounts instead show a single TXT record for DKIM, an older format using a fixed key (1024-bit by default, with 2048-bit available on request) that doesn't rotate on its own.
Which one you see depends on how the domain was set up; the important part is matching the record type Brevo displays exactly. Entering a CNAME's target value into a TXT record, or the reverse, is the most common way this step goes wrong.

05Add the DNS records at your DNS host
If you went the manual route, log into whatever service manages your DNS, your registrar or a separate host, and open the zone editor. Create each record using the exact type, host name, and value Brevo displayed, TXT or CNAME as shown, not assumed. Copy the values instead of retyping them; a single missing character is enough to fail verification.
06Confirm the domain shows as verified
DNS changes don't apply instantly. Propagation can take anywhere from a few minutes to around 48 hours, depending on your host and existing record TTLs. Return to the Domains tab periodically and use Brevo's check configuration option to refresh the status; once every record resolves correctly, the domain becomes available to select as a sender for your campaigns.
When it doesn't work
The domain stays stuck on unverified well past a day
Why: Either DNS propagation is still working through (up to 48 hours is normal), or a record was added as the wrong type, a CNAME value pasted into a TXT record, or vice versa.
Fix: Wait out the propagation window first. If it's still failing after that, reopen the Domains tab, compare each record's type and value character for character against what Brevo shows, and correct any mismatch.
Brevo won't let a domain be added at all
Why: Brevo only authenticates domains you control. Free consumer email domains like gmail.com or yahoo.com can't be authenticated by anyone.
Fix: Use your own custom domain, not a free email provider's domain, as the sending domain.
DKIM shows as a single TXT record instead of the two CNAME records described in setup guides
Why: The domain is using Brevo's older TXT-based DKIM format, not the current CNAME rotation setup, usually because it was authenticated some time ago.
Fix: The TXT format still works and doesn't need to be changed. If automatic key rotation matters, re-authenticate the domain to pick up the current CNAME-based setup.
Frequently asked questions
Where do I go in Brevo to verify a domain?
Settings, then Senders, domains, IPs, then the Domains tab. It's grouped under Organization settings, not under Campaigns or Marketing.
What DNS records does domain verification require?
A Brevo ownership code, always a TXT record, and a DKIM record. DKIM is usually two CNAME records (mail._domainkey and mail2._domainkey) on current accounts, though some older accounts still use a single TXT record instead. Match whichever type Brevo displays for your domain.
What's the difference between automatic and manual verification?
Automatic authentication signs into your domain registrar and adds the records for you. Manual verification generates the record values for you to copy into your DNS host's zone editor yourself.
How long does DNS verification take?
It depends on your host's propagation time and existing record TTLs, anywhere from a few minutes up to roughly 48 hours.
What happens if I don't verify my domain?
Mail from unverified domains is more likely to be filtered, bounced, or marked as spam by Gmail, Yahoo, and Microsoft, all of which now expect authenticated senders.
Sources and last check
Click path and screens come from a recorded walkthrough of Brevo's settings panel. The DNS record description was re-checked against Brevo's own Help Center in September 2026, which corrected a real error: the article previously described DKIM as always a single TXT record. Brevo's current default is two CNAME records that rotate keys automatically, with a single TXT record only on the older format some existing accounts still carry. The article now covers both and flags matching the record type as the step most likely to trip people up.
About the author

Impran M N
I've been hooked on technology for as long as I can remember — especially the new tools and AI apps that seem to land every other week. Easy Tech Tuts is where I write up whatever I've just worked out: I do the task in the real product, record the screen, and turn it into the guide I wish I'd found first.



