Mimecast signs outbound mail with a key at a selector named mimecast followed by the date it was made — mimecast20240101, say — published as a TXT record you add.
| Whose | Mimecast — email security gateway |
| Selector | mimecast<YYYYMMDD> |
| Published as | A TXT with the key, at mimecast followed by the date it was made |
| Key | 1024 or 2048-bit; 2048 is longer than 255 characters |
| Rotation | By hand: a new definition and key |
| Where to find it | Administration Console → Gateway Policies → Definitions → DNS Authentication – Outbound Signing |
| Can it go? | Once no Mimecast policy signs with it. |
Is Mimecast’s key on your domain?
Mimecast makes a selector for each account. Enter a domain and the selector it gave you — or paste the DKIM-Signature header of a message it sent — and we check the key, and name every other key the domain publishes.
The records
What Mimecast asks you to publish, with its own values in place of the placeholders:
mimecast20240101._domainkey.example.com TXT v=DKIM1; k=rsa; p=<public key>
Common mistakes
- Mail signed upstream (Microsoft 365 or on-premises) before Mimecast re-signs it can fail.
- A DNS host that strips the spaces in a long key.
Sources
Checked on 27 September 2026 against these official sources:
- Policies Configuring DNS Authentication Definition — mimecastsupport.zendesk.com