mte1 and mte2 are Mailchimp Transactional’s — Mandrill’s — DKIM selectors: CNAMEs to dkim1 and dkim2.mandrillapp.com. Since 15 March 2024 Mandrill sends nothing from a domain without them and a DMARC record.
| Whose | Mailchimp Transactional (Mandrill) — transactional email |
| Selector | mte1, mte2 |
| Published as | Two CNAMEs, to dkim1.mandrillapp.com and dkim2.mandrillapp.com, shared by every customer |
| Key | The keys at dkim1 and dkim2.mandrillapp.com are 2048-bit |
| Where to find it | Settings → Domains (Sending Domains) → View DKIM settings → Test DNS Settings |
| Can it go? | Once nothing sends through Mandrill for the domain; the old mandrill TXT can go once mte1 and mte2 verify. |
Is Mailchimp Transactional (Mandrill)’s key on your domain?
Enter a domain — or paste the DKIM-Signature header of a message it sent: we look for Mailchimp Transactional (Mandrill)’s key under mte1 and mte2 and mandrill, check it, and name every other key the domain publishes.
The records
What Mailchimp Transactional (Mandrill) asks you to publish, with its own values in place of the placeholders:
mte1._domainkey.example.com CNAME dkim1.mandrillapp.com
mte2._domainkey.example.com CNAME dkim2.mandrillapp.com
_dmarc.example.com TXT v=DMARC1; p=none
How it works
Before March 2024 Mandrill used a TXT key at mandrill._domainkey. It no longer counts for Mandrill’s own check.
Common mistakes
- Leaving out the DMARC record: Mandrill requires one (p=none at least) as well as the two CNAMEs.
What changed
- 15 March 2024 — Mandrill stopped sending from domains without mte1, mte2 and DMARC (announced 19 December 2023); unverified senders fall back to a mandrillapp.com subdomain.
Questions
What was mandrill._domainkey?
Mandrill’s older DKIM key, a TXT record. Its current setup is the mte1 and mte2 CNAMEs; remove the old record once they verify.
Sources
Checked on 27 September 2026 against these official sources:
- Authentication and Delivery Documentation — mailchimp.com
- New sending domain authentication requirements — mailchimp.com