m1 is the selector Adobe Marketo Engage uses in its own instructions for a custom DKIM key, published as a TXT record. SendGrid’s manual setup also puts a TXT key at m1, and Freshworks an m1 CNAME to freshpo.com — so the record and the service that gave it to you settle whose it is.
| Whose | Adobe Marketo Engage — marketing automation |
| Selector | m1 |
| Published as | A TXT with the key, at the selector you choose — m1 in Marketo’s own examples |
| Key | 1024 or 2048-bit; Marketo recommends 2048 |
| Rotation | By hand: a new selector or key size means deleting and republishing |
| Before you set it up | Marketo signs everything with a shared signature of its own |
| Where to find it | Admin → Email → SPF/DKIM → Add Domain |
| Can it go? | Marketo warns that changing or removing the record harms deliverability — delete the domain in Marketo first, then the record. |
Is Adobe Marketo Engage’s key on your domain?
Enter a domain — or paste the DKIM-Signature header of a message it sent: we look for Adobe Marketo Engage’s key under m1, check it, and name every other key the domain publishes.
The records
What Adobe Marketo Engage asks you to publish, with its own values in place of the placeholders:
m1._domainkey.example.com TXT v=DKIM1; k=rsa; p=<public key>
Common mistakes
- Another service already using m1 on the domain: choose m2 or another name, or ask Marketo support for a custom selector.
Questions
Is m1 Marketo’s or SendGrid’s?
Look at the value and who gave it to you: Marketo shows the record under Admin → Email; SendGrid’s m1 appears only when its automated security is off. A CNAME to freshpo.com is Freshworks’.
Sources
Checked on 27 September 2026 against these official sources:
- Set up a Custom DKIM Signature — experienceleague.adobe.com
- Custom DKIM Selector or Key — experienceleague.adobe.com
- Configure domain authentication — twilio.com