ms1 and ms2 are MailerSend’s DKIM selectors since September 2026: two CNAMEs to mailersend.net behind which it rotates 2048-bit keys. Earlier domains used a single CNAME, mlsend2, or a TXT key, whose support ends on 1 February 2027.
| Whose | MailerSend — transactional email |
| Selector | ms1, ms2 |
| Published as | Two CNAMEs, to ms1._domainkey.mailersend.net and ms2._domainkey.mailersend.net |
| Key | 2048-bit |
| Rotation | Automatic, behind the two CNAMEs |
| Where to find it | Email → Domains → the domain |
| Can it go? | The old mlsend2 or TXT key at any time once ms1 and ms2 verify — MailerSend says there is no need to hurry. |
Is MailerSend’s key on your domain?
Enter a domain — or paste the DKIM-Signature header of a message it sent: we look for MailerSend’s key under ms1 and ms2 and mlsend2 and mlsend, check it, and name every other key the domain publishes.
The records
What MailerSend asks you to publish, with its own values in place of the placeholders:
ms1._domainkey.example.com CNAME ms1._domainkey.mailersend.net
ms2._domainkey.example.com CNAME ms2._domainkey.mailersend.net
Common mistakes
- Adding only one of the two CNAMEs: MailerSend needs both to verify the domain.
What changed
- 2025 — TXT keys replaced by a single 1024-bit CNAME (mlsend2).
- 8 September 2026 — Two 2048-bit CNAMEs, ms1 and ms2.
- 1 February 2027 — TXT keys stop working.
Questions
Why does MailerLite’s domain have ms1 too?
MailerSend is MailerLite’s sister product; MailerLite itself uses litesrv.
Sources
Checked on 27 September 2026 against these official sources:
- Updated DKIM keys for more secure, efficient authentication — mailersend.com
- How to Verify and Authenticate a Sending Domain — mailersend.com
- Domains — MailerSend Developers — developers.mailersend.com