Keep your Brevo contact lists clean. MailTester Ninja checks each address against the recipient's mail server, without sending any email, and writes the verdict into two Brevo contact attributes. You can then exclude invalid addresses from your campaigns, keep your bounce rate low and protect your sender reputation. Verify every new contact automatically, or clean an existing list in one pass.
What you need
- A Brevo account, any plan, and a Brevo API key: in Brevo, open SMTP & API from your account menu, then the API keys tab, and generate one.
- A MailTester Ninja key: a free API token to try it (50 checks a day, one request every 30 seconds) or a paid key for whole lists.
- For the automatic check: n8n with our official MailTester Ninja node (verified by n8n, on n8n Cloud or self-hosted), or Make or Zapier.
Step 1: add two contact attributes in Brevo
In Brevo, open Contacts, then Settings, then Contact attributes, and add two attributes of type Text:
MT_CODE: the verdict code,ok,koormb.MT_VERDICT: the detailed status, for example Accepted, Rejected, Catch-All or Disposable.
Step 2: verify every new contact automatically (n8n)
This workflow runs each time a contact is added to a Brevo list, from a signup form, an import or the API. It verifies the address and saves the verdict on the contact.
- In n8n, install our node from the nodes panel: search for MailTester Ninja, then click Install (details on our n8n page).
- Download the workflow brevo-verify-new-contacts.json, then in n8n choose Workflows, then Import from file.
- Open the two Brevo nodes and create a Brevo credential with your Brevo API key. Open the MailTester Ninja node and create a MailTester Ninja API credential with your key.
- In Save the verdict in Brevo, check that the two attribute names are
MT_CODEandMT_VERDICT. - Publish (or activate) the workflow. The trigger registers a Brevo webhook for the List Addition event on its own.
With Make or Zapier: watch new contacts with the Brevo app, verify the address with an HTTP request as shown on our Make and Zapier pages, then update the Brevo contact with MT_CODE and MT_VERDICT.
Step 3: use the verdict in Brevo
Create a segment for each verdict in Contacts, then Segments, with a condition on MT_CODE.
| MT_CODE | Meaning | What to do in Brevo |
|---|---|---|
ok | Valid and deliverable | Keep the contact in your campaigns. |
ko | Invalid, will bounce | Exclude the segment from your campaigns, or blocklist or delete the contacts. |
mb | Uncertain (catch-all domain, server could not be probed) | Send to them in smaller batches, after your valid contacts, and drop those that never engage. |
-- | No verdict (key problem, or free limit reached) | Verify again later. Never delete a contact on this answer. |
Clean an existing Brevo list
- In Brevo, open the list in Contacts and export it as a CSV file.
- Drop the file on the MailTester Ninja verifier with a paid key, wait for the results, then click Save.
- Open the saved file, delete the explanation lines at the top (everything above the first address), and add this first line:
EMAIL,NAME,DOMAIN,MX,MT_CODE,MT_VERDICT. - In Brevo, import the file into the same list, map
EMAIL,MT_CODEandMT_VERDICT, skip the other columns, and choose to update existing contacts. - Build the segments from step 3 and exclude
kobefore your next campaign.
Developers can do the same through the APIs: read the contacts with GET https://api.brevo.com/v3/contacts, verify each address with https://happy.mailtester.ninja/ninja?email=ADDRESS&key=YOUR_KEY, then write the verdict with PUT https://api.brevo.com/v3/contacts/{email} and the body {"attributes":{"MT_CODE":"ko","MT_VERDICT":"Rejected"}}. Keep about one request per second on a paid key (11 requests per 10 seconds on Pro).
Keep your keys secret
Store both keys in n8n, Make or Zapier credentials rather than in a node field, so an exported workflow never contains them.
Questions
Does the check send an email to my contacts?
No. MailTester Ninja opens a conversation with the recipient's mail server and stops before any message is sent. Your contacts receive nothing.
Is anything stored?
No. Each address is checked in real time and we keep no copy of the addresses you verify. The verdict lives only in your Brevo account.
Why verify contacts that already signed up?
Signup forms collect typos, disposable inboxes and fake addresses, and lists decay as people change jobs. Mailbox providers read a high bounce rate as a sign of a bad sender, so removing these addresses keeps your Brevo campaigns in the inbox.
Try it now
Get a free API token, or see the plans for up to 200,000 checks a day. Full reference: API documentation and OpenAPI specification. Back to all integrations.
