DKIM selector list and email provider records
The MX hosts, SPF includes, DKIM selectors and DKIM targets that the checks on this site know, provider by provider. Each value says where it comes from, and all of it is free to download as JSON.
The DKIM selectors
The checks look for a DKIM key at 76 selectors. 73 of them come from the documentation of the service or program that uses them, and the rest were seen in DNS.
googleselector1selector2fm1fm2fm3protonmailprotonmail2protonmail3sig1cf2024-1zohos1s2k1k2k3resendbrevo1brevo2mailsmtpmxpicdefaultdkimmandrillklkl2zendesk1zendesk2mailjetmte1mte2intercomcmkrsmailoxhostingermail-ahostingermail-bhostingermail-cs1-ionoss2-ionoslitesrvacdkim1strong1strong2ctct1ctct2key1key2key3m1squarespacegm1gm2gm3kl1privateemailpurelymail1purelymail2purelymail3mbo0001mbo0002mbo0003mbo0004strato-dkim-0002strato-dkim-0003cf-bouncea1mailpoet1mailpoet2e2ma-k1e2ma-k2e2ma-k3
On 19 November 2026, 67.9% of 2,707 domains with MX in a Tranco sample (list L5KW4) had a DKIM key at one of the 76 selectors. For the rest, the check cannot tell whether they sign with another one. Tranco list L5KW4.
What a selector’s name says
- By its name
- The key is the listed provider’s, by its name alone.
- By its CNAME target
- The key is the provider’s only when its CNAME points under one of the provider’s DKIM targets.
- Never by its name
- The name says nothing about who owns the key.
Providers and their records
31 providers. Each entry is a value the checks use to recognise that provider, with the vendor page that gives it; the few seen only in DNS say so.
Google Workspace
- MX host
smtp.google.com - knowledge.workspace.google.com, read 20 November 2026
The page’s words
The Google Workspace MX record value is smtp.google.com .
- MX host
aspmx.l.google.com - Seen in DNS on
zapier.com,stripe.com,airbnb.com,shopify.comon 20 November 2026 - SPF include
_spf.google.com - knowledge.workspace.google.com, read 20 November 2026
The page’s words
If you use only Google Workspace to send email, copy this line of text: v=spf1 include:_spf.google.com ~all
- DKIM selector
googleGoogle Workspace’s by its name - knowledge.workspace.google.com, read 20 November 2026
The page’s words
The default prefix selector is google .
- DKIM CNAME target None
- knowledge.workspace.google.com gives none, read 20 November 2026.The key is a TXT record, so there is no CNAME target.
Microsoft 365
- MX host
mail.protection. outlook. com - learn.microsoft.com, read 20 November 2026
The page’s words
Target email server: <MX token>.mail.protection.outlook.com
- MX host
mx.microsoft - learn.microsoft.com, read 20 November 2026
The page’s words
This value is the name that the new MX record points to for the domain you're enabling with DNSSEC. For example, contosotest-com.o-v1.mx.microsoft .
- SPF include
spf.protection. outlook. com - learn.microsoft.com, read 20 November 2026
The page’s words
TXT Name @ Values: v=spf1 include:spf.protection.outlook.com -all
- DKIM selector
selector1Microsoft 365’s if the CNAME points under a Microsoft 365 DKIM target - learn.microsoft.com, read 20 November 2026
The page’s words
Points to address or value: selector1-contoso-com._domainkey.contoso.onmicrosoft.com
- DKIM selector
selector2Microsoft 365’s if the CNAME points under a Microsoft 365 DKIM target - learn.microsoft.com, read 20 November 2026
The page’s words
Hostname: selector2._domainkey
- DKIM CNAME target
onmicrosoft.com - learn.microsoft.com, read 20 November 2026
The page’s words
Points to address or value: selector1-contoso-com._domainkey.contoso.onmicrosoft.com
- DKIM CNAME target
dkim.mail.microsoft - learn.microsoft.com, read 20 November 2026
The page’s words
dkim.mail.microsoft : The parent DNS zone that's the same for both selectors.
Fastmail
- MX host
messagingengine.com - fastmail.help, read 20 November 2026
The page’s words
MX @ in1-smtp.messagingengine.com 10
- SPF include
spf.messagingengine. com - fastmail.help, read 20 November 2026
The page’s words
TXT {mydomain.com} v=spf1 include:spf.messagingengine.com ?all
- DKIM selector
fm1Fastmail’s if the CNAME points under a Fastmail DKIM target - fastmail.help, read 20 November 2026
The page’s words
CNAME fm1._domainkey fm1.{mydomain.com}.dkim.fmhosted.com
- DKIM selector
fm2Fastmail’s if the CNAME points under a Fastmail DKIM target - fastmail.help, read 20 November 2026
The page’s words
CNAME fm2._domainkey fm2.{mydomain.com}.dkim.fmhosted.com
- DKIM selector
fm3Fastmail’s if the CNAME points under a Fastmail DKIM target - fastmail.help, read 20 November 2026
The page’s words
CNAME fm3._domainkey fm3.{mydomain.com}.dkim.fmhosted.com
- DKIM CNAME target
dkim.fmhosted.com - fastmail.help, read 20 November 2026
The page’s words
CNAME fm1._domainkey fm1.{mydomain.com}.dkim.fmhosted.com
Zoho Mail
- MX host
zoho.com - zoho.com, read 20 November 2026
The page’s words
@/ Blank/ Domain name mx.zoho.com 10
- MX host
zoho.eu - Seen in DNS on
zoho.euon 20 November 2026 - SPF include
zohomail.com - zoho.com, read 20 November 2026
The page’s words
The Valid SPF records that need to be published are provided below: v=spf1 include:zohomail.com -all
- SPF include
one.zoho.com - zoho.com, read 20 November 2026
The page’s words
In case you are using multiple Zoho services, you can use v=spf1 include:one.zoho.com -all to avoid any SPF lookup failure.
- DKIM selector
zohoZoho Mail’s by its name - zoho.com, read 20 November 2026
The page’s words
zoho._domainkey
- DKIM CNAME target None
- zoho.com gives none, read 20 November 2026.The key is a TXT record, so there is no CNAME target.
Proton Mail
- MX host
protonmail.ch - proton.me, read 20 November 2026
The page’s words
Mail server : mail.protonmail.ch
- SPF include
_spf.protonmail.ch - proton.me, read 20 November 2026
The page’s words
The “include:_spf.protonmail.ch” part of the text string means that you allow Proton Mail servers to send on behalf of your domain.
- DKIM selector
protonmailProton Mail’s by its name - proton.me, read 20 November 2026
The page’s words
Name : protonmail._domainkey
- DKIM selector
protonmail2Proton Mail’s by its name - proton.me, read 20 November 2026
The page’s words
To add a second and third DKIM record, repeat these steps with the appropriate record names protonmail2._domainkey and protonmail3._domainkey .
- DKIM selector
protonmail3Proton Mail’s by its name - proton.me, read 20 November 2026
The page’s words
To add a second and third DKIM record, repeat these steps with the appropriate record names protonmail2._domainkey and protonmail3._domainkey .
- DKIM CNAME target None
- proton.me gives none, read 20 November 2026.The CNAME target is copied from the Proton Mail console; the page does not give it.
iCloud+
- MX host
mail.icloud.com - support.apple.com, read 20 November 2026
The page’s words
Record Type: MX Host: @ Value: mx01.mail.icloud.com.
- SPF include
icloud.com - support.apple.com, read 20 November 2026
The page’s words
Record Type: TXT Host: @ Value: "v=spf1 include:icloud.com ~all"
- DKIM selector
sig1iCloud+’s if the CNAME points under a iCloud+ DKIM target - support.apple.com, read 20 November 2026
The page’s words
Record Type: CNAME Host: sig1._domainkey Value: sig1.dkim.example.com.at.icloudmailadmin.com.
- DKIM CNAME target
at.icloudmailadmin. com - support.apple.com, read 20 November 2026
The page’s words
Record Type: CNAME Host: sig1._domainkey Value: sig1.dkim.example.com.at.icloudmailadmin.com.
Cloudflare Email Routing
- MX host
mx.cloudflare.net - developers.cloudflare.com, read 20 November 2026
The page’s words
Purpose : Route incoming emails to Cloudflare's mail servers. MX yourdomain.com route1.mx.cloudflare.net
- SPF include
_spf.mx. cloudflare. net - developers.cloudflare.com, read 20 November 2026
The page’s words
v=spf1 include:_spf.mx.cloudflare.net ~all
- DKIM selector
cf2024-1Cloudflare Email Routing’s by its name - developers.cloudflare.com, read 20 November 2026
The page’s words
TXT cf2024-1._domainkey.yourdomain.com
- DKIM CNAME target None
- developers.cloudflare.com gives none, read 20 November 2026.The key is a TXT record, so there is no CNAME target.
Amazon SES
- MX host
amazonses.com - docs.aws.amazon.com, read 20 November 2026
The page’s words
subdomain.domain.com MX 10 feedback-smtp.region.amazonses.com
- SPF include
amazonses.com - docs.aws.amazon.com, read 20 November 2026
The page’s words
subdomain.domain.com TXT "v=spf1 include:amazonses.com ~all"
- DKIM selector None
- docs.aws.amazon.com gives none, read 20 November 2026.Easy DKIM gives three CNAME records per domain in the SES console; their names are tokens no list can hold.
- DKIM CNAME target
amazonses.com - docs.aws.amazon.com, read 20 November 2026
The page’s words
Each CNAME record's value is composed of the DKIM token followed by a hosted zone domain (for example, token.dkim.us-west-2.amazonses.com). The hosted zone portion varies by AWS Region and identity.
SendGrid
- MX host
sendgrid.net - twilio.com, read 20 November 2026
The page’s words
MX em[0000].example.com mx.sendgrid.net. MX
- SPF include
sendgrid.net - twilio.com, read 20 November 2026
The page’s words
TXT em[0000].example.com v=spf1 include:sendgrid.net ~all SPF
- DKIM selector
s1SendGrid’s if the CNAME points under a SendGrid DKIM target - twilio.com, read 20 November 2026
The page’s words
s1._domainkey.example.com s1.domainkey.[u00000000].[wl000].sendgrid.net DKIM
- DKIM selector
s2SendGrid’s if the CNAME points under a SendGrid DKIM target - twilio.com, read 20 November 2026
The page’s words
s2._domainkey.example.com s2.domainkey.[u00000000].[wl000].sendgrid.net DKIM
- DKIM selector
m1SendGrid’s if the CNAME points under a SendGrid DKIM target - twilio.com, read 20 November 2026
The page’s words
m1._domainkey.example.com k=rsa; t=s; p=MIG... DKIM
- DKIM CNAME target
sendgrid.net - twilio.com, read 20 November 2026
The page’s words
s1._domainkey.example.com s1.domainkey.[u00000000].[wl000].sendgrid.net DKIM
Mailgun
- MX host
mailgun.org - help.mailgun.com, read 20 November 2026
The page’s words
Mail server mxa.mailgun.org (for the first MX record) mxb.mailgun.org (for the second MX record)
- SPF include
mailgun.org - help.mailgun.com, read 20 November 2026
The page’s words
Content v=spf1 include:mailgun.org ~all
- DKIM selector
smtpIts name says nothing about the owner - help.mailgun.com, read 20 November 2026
The page’s words
pic._domainkey (or, one of several other values such as krs._domainkey , smtp._domainkey , or mailo._domainkey )
- DKIM selector
mxIts name says nothing about the owner - help.mailgun.com, read 20 November 2026
The page’s words
Add another TXT record for mx._domainkey.mail.yourdomain.com .
- DKIM selector
picMailgun’s by its name - help.mailgun.com, read 20 November 2026
The page’s words
pic._domainkey (or, one of several other values such as krs._domainkey , smtp._domainkey , or mailo._domainkey )
- DKIM selector
krsMailgun’s by its name - help.mailgun.com, read 20 November 2026
The page’s words
pic._domainkey (or, one of several other values such as krs._domainkey , smtp._domainkey , or mailo._domainkey )
- DKIM selector
mailoMailgun’s by its name - help.mailgun.com, read 20 November 2026
The page’s words
pic._domainkey (or, one of several other values such as krs._domainkey , smtp._domainkey , or mailo._domainkey )
- DKIM CNAME target None
- help.mailgun.com gives one the checks do not use, read 20 November 2026.Its only DKIM CNAME target is for the pdk1 and pdk2 selectors of Automatic Sender Security, which this check does not look up; none is given for smtp, mx, pic, krs or mailo.
The page’s words
the target where you point back to Mailgun will look something like pdk1._domainkey.9d876.dkim1.mailgun.com
Postmark
- MX host None
- postmarkapp.com gives none, read 20 November 2026.The custom Return-Path is a CNAME to
pm.mtasv.net, not an MX. - SPF include None
- postmarkapp.com gives none, read 20 November 2026.
- DKIM selector None
- postmarkapp.com gives none, read 20 November 2026.The DKIM record, its name included, is shown in the Postmark account.
- DKIM CNAME target None
- postmarkapp.com gives none, read 20 November 2026.The key is a TXT record, so there is no CNAME target.
Resend
- MX host None
- resend.com gives one the checks do not use, read 20 November 2026.The MX and the include on the send subdomain are those of Amazon SES, listed under Amazon SES.
The page’s words
"name": "send", "type": "MX", "ttl": "Auto", "status": "not_started", "value": "feedback-smtp.us-east-1.amazonses.com"
- SPF include None
- resend.com gives one the checks do not use, read 20 November 2026.The MX and the include on the send subdomain are those of Amazon SES, listed under Amazon SES.
The page’s words
"name": "send", "value": "v=spf1 include:amazonses.com ~all"
- DKIM selector
resendResend’s by its name - resend.com, read 20 November 2026
The page’s words
Type `resend._domainkey` for the `Name` of the record.
- DKIM CNAME target None
- resend.com gives none, read 20 November 2026.The key is a TXT record, so there is no CNAME target.
Brevo
- MX host None
- help.brevo.com gives none, read 20 November 2026.
- SPF include None
- help.brevo.com gives none, read 20 November 2026.
- DKIM selector
brevo1Brevo’s by its name - help.brevo.com, read 20 November 2026
The page’s words
DKIM 1 record brevo1._domainkey brevo1._domainkey.yourdomain.com
- DKIM selector
brevo2Brevo’s by its name - help.brevo.com, read 20 November 2026
The page’s words
DKIM 2 record brevo2._domainkey brevo2._domainkey.yourdomain.com
- DKIM CNAME target None
- help.brevo.com gives none, read 20 November 2026.The value of each record is copied from the Brevo account; the page does not give it.
Mailchimp
- MX host None
- mailchimp.com gives none, read 20 November 2026.
- SPF include None
- mailchimp.com gives none, read 20 November 2026.The page asks for 2 CNAME records and 1 TXT record, the DMARC one, and no SPF.
- DKIM selector
k1Mailchimp’s if the CNAME points under a Mailchimp DKIM target - Seen in DNS on
mailchimp.com,intuit.comon 20 November 2026 - DKIM selector
k2Mailchimp’s if the CNAME points under a Mailchimp DKIM target - mailchimp.com, read 20 November 2026
The page’s words
For example, if you enter “k2._domainkey.example.com” and “k2._domainkey.example.com.example.com” is created
- DKIM selector
k3Mailchimp’s if the CNAME points under a Mailchimp DKIM target - Seen in DNS on
mailchimp.com,intuit.comon 20 November 2026 - DKIM CNAME target
mcsv.net - Seen in DNS on
mailchimp.com,intuit.comon 20 November 2026
Klaviyo
- MX host None
- help.klaviyo.com gives none, read 20 November 2026.Only a service sending subdomain gets an MX record, and Klaviyo manages it.
- SPF include None
- help.klaviyo.com gives none, read 20 November 2026.
- DKIM selector
klKlaviyo’s if the CNAME points under a Klaviyo DKIM target - help.klaviyo.com, read 20 November 2026
The page’s words
Existing static domains can use legacy selector pairs such as kl/kl2 or kl1/kl2 .
- DKIM selector
kl2Klaviyo’s if the CNAME points under a Klaviyo DKIM target - help.klaviyo.com, read 20 November 2026
The page’s words
Existing static domains can use legacy selector pairs such as kl/kl2 or kl1/kl2 .
- DKIM selector
kl1Klaviyo’s if the CNAME points under a Klaviyo DKIM target - help.klaviyo.com, read 20 November 2026
The page’s words
your DNS records use the legacy kl1 / kl2 DKIM selectors and continue to work without changes.
- DKIM CNAME target
u161779.wl030. sendgrid. net - help.klaviyo.com, read 20 November 2026
The page’s words
this would make the value u161779.wl030.sendgrid.net.rootdomain.com instead of just u161779.wl030.sendgrid.net.
- DKIM CNAME target
klaviyodns.com - help.klaviyo.com, read 20 November 2026
The page’s words
km1._domainkey.helloworld.com km1._domainkey.1.klaviyodns.com CNAME
Zendesk
- MX host None
- support.zendesk.com gives none, read 20 November 2026.
- SPF include
mail.zendesk.com - support.zendesk.com, read 20 November 2026
The page’s words
Zendesk recommends using the following SPF record: v=spf1 include:mail.zendesk.com -all
- DKIM selector
zendesk1Zendesk’s if the CNAME points under a Zendesk DKIM target - support.zendesk.com, read 20 November 2026
The page’s words
In the Host Record field (or equivalent), enter: zendesk1._domainkey. your_email_domain.com
- DKIM selector
zendesk2Zendesk’s if the CNAME points under a Zendesk DKIM target - support.zendesk.com, read 20 November 2026
The page’s words
In the Host Record field, enter: zendesk2._domainkey. your_email_domain .com
- DKIM CNAME target
zendesk.com - support.zendesk.com, read 20 November 2026
The page’s words
In the Points To field (or equivalent), enter: zendesk1._domainkey.zendesk.com
Mailchimp Transactional
- MX host None
- mailchimp.com gives none, read 20 November 2026.
- SPF include None
- mailchimp.com gives none, read 20 November 2026.Its return path is its own,
mandrillapp.com, unless the sender points it to a domain of theirs. - DKIM selector
mte1Mailchimp Transactional’s if the CNAME points under a Mailchimp Transactional DKIM target - mailchimp.com, read 20 November 2026
The page’s words
Add two new CNAME records with the names mte1._domainkey.example.com and mte2._domainkey.example.com
- DKIM selector
mte2Mailchimp Transactional’s if the CNAME points under a Mailchimp Transactional DKIM target - mailchimp.com, read 20 November 2026
The page’s words
Add two new CNAME records with the names mte1._domainkey.example.com and mte2._domainkey.example.com
- DKIM CNAME target
mandrillapp.com - mailchimp.com, read 20 November 2026
The page’s words
The value for the record should first CNAME should be dkim1.mandrillapp.com , and the value for the second record should be dkim2.mandrillapp.com .
Hostinger Email
- MX host
mx1.hostinger.com - hostinger.com, read 20 November 2026
The page’s words
@ 5 mx1.hostinger.com
- MX host
mx2.hostinger.com - hostinger.com, read 20 November 2026
The page’s words
@ 10 mx2.hostinger.com
- SPF include
_spf.mail. hostinger. com - hostinger.com, read 20 November 2026
The page’s words
TXT @ v=spf1 include:_spf.mail.hostinger.com ~all
- DKIM selector
hostingermail-aHostinger Email’s if the CNAME points under a Hostinger Email DKIM target - hostinger.com, read 20 November 2026
The page’s words
CNAME hostingermail-a._domainkey hostingermail-a.dkim.mail.hostinger.com
- DKIM selector
hostingermail-bHostinger Email’s if the CNAME points under a Hostinger Email DKIM target - hostinger.com, read 20 November 2026
The page’s words
CNAME hostingermail-b._domainkey hostingermail-b.dkim.mail.hostinger.com
- DKIM selector
hostingermail-cHostinger Email’s if the CNAME points under a Hostinger Email DKIM target - hostinger.com, read 20 November 2026
The page’s words
CNAME hostingermail-c._domainkey hostingermail-c.dkim.mail.hostinger.com
- DKIM CNAME target
dkim.mail. hostinger. com - hostinger.com, read 20 November 2026
The page’s words
CNAME hostingermail-a._domainkey hostingermail-a.dkim.mail.hostinger.com
IONOS
- MX host
ionos.com - ionos.com, read 20 November 2026
The page’s words
receiving emails will only be possible using the correct MX record entries mx00.ionos.com / mx01.ionos.com (alternatively mx00.1and1.com / mx01.1and1.com).
- MX host
1and1.com - ionos.com, read 20 November 2026
The page’s words
receiving emails will only be possible using the correct MX record entries mx00.ionos.com / mx01.ionos.com (alternatively mx00.1and1.com / mx01.1and1.com).
- MX host
ionos.de - ionos.de, read 20 November 2026
The page’s words
mx00.ionos.de / mx01.ionos.de (alternativ: mx00.kundenserver.de / mx01.kundenserver.de)
- MX host
kundenserver.de - ionos.de, read 20 November 2026
The page’s words
mx00.ionos.de / mx01.ionos.de (alternativ: mx00.kundenserver.de / mx01.kundenserver.de)
- SPF include None
- ionos.com gives one the checks do not use, read 20 November 2026.The page, on
ionos.com, givesinclude:_spf-us.ionos.com. No page read gives the include of IONOS customers in other countries, so the check does not suggest this one.The page’s words
create a TXT record for your domain with the following value: v=spf1 include:_spf-us.ionos.com ~all
- DKIM selector
s1-ionosIONOS’s if the CNAME points under a IONOS DKIM target - ionos.com, read 20 November 2026
The page’s words
s1-ionos._domainkey s1.dkim.ionos.com 1 hour
- DKIM selector
s2-ionosIONOS’s if the CNAME points under a IONOS DKIM target - ionos.com, read 20 November 2026
The page’s words
s2-ionos._domainkey s2.dkim.ionos.com 1 hour
- DKIM CNAME target
dkim.ionos.com - ionos.com, read 20 November 2026
The page’s words
s1-ionos._domainkey s1.dkim.ionos.com 1 hour
Gandi Mail
- MX host
mail.gandi.net - docs.gandi.net, read 20 November 2026
The page’s words
@ 10800 IN MX 10 spool.mail.gandi.net.
- SPF include
_mailcust.gandi.net - docs.gandi.net, read 20 November 2026
The page’s words
@ 10800 IN TXT "v=spf1 include:_mailcust.gandi.net ?all"
- DKIM selector
gm1Gandi Mail’s if the CNAME points under a Gandi Mail DKIM target - docs.gandi.net, read 20 November 2026
The page’s words
gm1._domainkey 10800 IN CNAME gm1.gandimail.net.
- DKIM selector
gm2Gandi Mail’s if the CNAME points under a Gandi Mail DKIM target - docs.gandi.net, read 20 November 2026
The page’s words
gm2._domainkey 10800 IN CNAME gm2.gandimail.net.
- DKIM selector
gm3Gandi Mail’s if the CNAME points under a Gandi Mail DKIM target - docs.gandi.net, read 20 November 2026
The page’s words
gm3._domainkey 10800 IN CNAME gm3.gandimail.net.
- DKIM CNAME target
gandimail.net - docs.gandi.net, read 20 November 2026
The page’s words
gm1._domainkey 10800 IN CNAME gm1.gandimail.net.
Migadu
- MX host
migadu.com - migadu.com, read 20 November 2026
The page’s words
"value": "aspmx1.migadu.com"
- SPF include
spf.migadu.com - migadu.com, read 20 November 2026
The page’s words
"value": "v=spf1 include:spf.migadu.com -all"
- DKIM selector
key1Migadu’s if the CNAME points under a Migadu DKIM target - migadu.com, read 20 November 2026
The page’s words
"name": "key1._domainkey", "type": "cname", "value": "key1.mydomain.org._domainkey.migadu.com."
- DKIM selector
key2Migadu’s if the CNAME points under a Migadu DKIM target - migadu.com, read 20 November 2026
The page’s words
"name": "key2._domainkey", "type": "cname", "value": "key2.mydomain.org._domainkey.migadu.com."
- DKIM selector
key3Migadu’s if the CNAME points under a Migadu DKIM target - migadu.com, read 20 November 2026
The page’s words
"name": "key3._domainkey", "type": "cname", "value": "key3.mydomain.org._domainkey.migadu.com."
- DKIM CNAME target
migadu.com - migadu.com, read 20 November 2026
The page’s words
"value": "key1.mydomain.org._domainkey.migadu.com."
Namecheap Private Email
- MX host
privateemail.com - namecheap.com, read 20 November 2026
The page’s words
@ MX 10 mx1.privateemail.com
- SPF include
spf.privateemail.com - namecheap.com, read 20 November 2026
The page’s words
@ TXT v=spf1 include:spf.privateemail.com ~all
- DKIM selector
privateemailNamecheap Private Email’s by its name - namecheap.com, read 20 November 2026
The page’s words
Host : privateemail._domainkey Record type : TXT
- DKIM CNAME target None
- namecheap.com gives none, read 20 November 2026.The key is a TXT record, so there is no CNAME target.
Purelymail
- MX host
purelymail.com - purelymail.com, read 20 November 2026
The page’s words
Put @ on the "Name" field and mailserver.purelymail.com on the Mail Server field.
- SPF include
_spf.purelymail.com - purelymail.com, read 20 November 2026
The page’s words
Put @ on the "Name" field and v=spf1 include:_spf.purelymail.com ~all on the Content field.
- DKIM selector
purelymail1Purelymail’s if the CNAME points under a Purelymail DKIM target - purelymail.com, read 20 November 2026
The page’s words
Put purelymail1._domainkey on the "Name" field and key1.dkimroot.purelymail.com on the Content field.
- DKIM selector
purelymail2Purelymail’s if the CNAME points under a Purelymail DKIM target - purelymail.com, read 20 November 2026
The page’s words
Put purelymail2._domainkey on the "Name" field and key2.dkimroot.purelymail.com on the Content field.
- DKIM selector
purelymail3Purelymail’s if the CNAME points under a Purelymail DKIM target - purelymail.com, read 20 November 2026
The page’s words
Put purelymail3._domainkey on the "Name" field and key3.dkimroot.purelymail.com on the Content field.
- DKIM CNAME target
dkimroot.purelymail. com - purelymail.com, read 20 November 2026
The page’s words
Put purelymail1._domainkey on the "Name" field and key1.dkimroot.purelymail.com on the Content field.
mailbox.org
- MX host
mailbox.org - kb.mailbox.org, read 20 November 2026
The page’s words
example-domain.com MX 10 mxext1.mailbox.org.
- SPF include
mailbox.org - kb.mailbox.org, read 20 November 2026
The page’s words
@ TXT v=spf1 include:mailbox.org ~all SPF
- DKIM selector
mbo0001mailbox.org’s if the CNAME points under a mailbox.org DKIM target - kb.mailbox.org, read 20 November 2026
The page’s words
MBO0001._domainkey.example.com CNAME MBO0001._domainkey.mailbox.org.
- DKIM selector
mbo0002mailbox.org’s if the CNAME points under a mailbox.org DKIM target - kb.mailbox.org, read 20 November 2026
The page’s words
MBO0002._domainkey.example.com CNAME MBO0002._domainkey.mailbox.org.
- DKIM selector
mbo0003mailbox.org’s if the CNAME points under a mailbox.org DKIM target - kb.mailbox.org, read 20 November 2026
The page’s words
MBO0003._domainkey.example.com CNAME MBO0003._domainkey.mailbox.org.
- DKIM selector
mbo0004mailbox.org’s if the CNAME points under a mailbox.org DKIM target - kb.mailbox.org, read 20 November 2026
The page’s words
MBO0004._domainkey.example.com CNAME MBO0004._domainkey.mailbox.org.
- DKIM CNAME target
mailbox.org - kb.mailbox.org, read 20 November 2026
The page’s words
MBO0001._domainkey.example.com CNAME MBO0001._domainkey.mailbox.org.
Strato
- MX host
rzone.de - strato.de, read 20 November 2026
The page’s words
MX-Record : smtpin.rzone.de
- SPF include
_spf.strato.com - strato.de, read 20 November 2026
The page’s words
Sollen die STRATO Mailserver weiterhin E-Mails versenden dürfen, nehmen Sie include:_spf.strato.com in Ihren Eintrag auf.
- DKIM selector
strato-dkim-0002Strato’s if the CNAME points under a Strato DKIM target - strato.de, read 20 November 2026
The page’s words
strato-dkim-0002._domainkey.meinedomain.tld CNAME strato-dkim-0002._domainkey.rzone.de.
- DKIM selector
strato-dkim-0003Strato’s if the CNAME points under a Strato DKIM target - strato.de, read 20 November 2026
The page’s words
strato-dkim-0003._domainkey.meinedomain.tld CNAME strato-dkim-0003._domainkey.rzone.de.
- DKIM CNAME target
rzone.de - strato.de, read 20 November 2026
The page’s words
strato-dkim-0002._domainkey.meinedomain.tld CNAME strato-dkim-0002._domainkey.rzone.de.
MailerLite
- MX host None
- mailerlite.com gives none, read 20 November 2026.
- SPF include None
- mailerlite.com gives none, read 20 November 2026.
- DKIM selector
litesrvMailerLite’s if the CNAME points under a MailerLite DKIM target - mailerlite.com, read 20 November 2026
The page’s words
In the Name field box, add litesrv._domainkey .
- DKIM CNAME target
mlsend.com - mailerlite.com, read 20 November 2026
The page’s words
In the Target field box, paste the DKIM value litesrv._domainkey.mlsend.com .
Help Scout
- MX host None
- docs.helpscout.com gives none, read 20 November 2026.
- SPF include None
- docs.helpscout.com gives one the checks do not use, read 20 November 2026.Help Scout says the
include:helpscoutemail.comit once asked for can be removed.The page’s words
You can safely remove include:helpscoutemail.com from your SPF record if you added it previously.
- DKIM selector
strong1Help Scout’s if the CNAME points under a Help Scout DKIM target - docs.helpscout.com, read 20 November 2026
The page’s words
strong1._domainkey.yourdomain.com will point to strong1._domainkey.helpscout.net
- DKIM selector
strong2Help Scout’s if the CNAME points under a Help Scout DKIM target - docs.helpscout.com, read 20 November 2026
The page’s words
strong2._domainkey.yourdomain.com will point to strong2._domainkey.helpscout.net
- DKIM CNAME target
helpscout.net - docs.helpscout.com, read 20 November 2026
The page’s words
strong1._domainkey.yourdomain.com will point to strong1._domainkey.helpscout.net
Constant Contact
- MX host None
- knowledgebase.constantcontact.com gives none, read 20 November 2026.
- SPF include None
- knowledgebase.constantcontact.com gives none, read 20 November 2026.
- DKIM selector
ctct1Constant Contact’s if the CNAME points under a Constant Contact DKIM target - knowledgebase.constantcontact.com, read 20 November 2026
The page’s words
For CNAME, the record name should be input as “ctct1._domainkey” and “ctct2_domainkey”
- DKIM selector
ctct2Constant Contact’s if the CNAME points under a Constant Contact DKIM target - knowledgebase.constantcontact.com, read 20 November 2026
The page’s words
For CNAME, the record name should be input as “ctct1._domainkey” and “ctct2_domainkey”
- DKIM CNAME target
ccsend.com - knowledgebase.constantcontact.com, read 20 November 2026
The page’s words
For CNAME records, it points back to ccsend.com (100._domainkey.dkim1.ccsend.com or 200._domainkey.dkim2.ccsend.com).
Squarespace Email Campaigns
- MX host None
- support.squarespace.com gives none, read 20 November 2026.
- SPF include None
- support.squarespace.com gives none, read 20 November 2026.
- DKIM selector
squarespaceSquarespace Email Campaigns’s if the CNAME points under a Squarespace Email Campaigns DKIM target - support.squarespace.com, read 20 November 2026
The page’s words
CNAME squarespace._domainkey squarespace-domainkey.squarespace-mail.com
- DKIM CNAME target
squarespace-mail.com - support.squarespace.com, read 20 November 2026
The page’s words
CNAME squarespace._domainkey squarespace-domainkey.squarespace-mail.com
MailPoet
- MX host None
- kb.mailpoet.com gives none, read 20 November 2026.
- SPF include None
- kb.mailpoet.com gives none, read 20 November 2026.
- DKIM selector
mailpoet1MailPoet’s by its name - kb.mailpoet.com, read 20 November 2026
The page’s words
leaving them as ” mailpoet1._domainkey”, “mailpoet2._domainkey”, “_mailpoet”, and “_dmarc”
- DKIM selector
mailpoet2MailPoet’s by its name - kb.mailpoet.com, read 20 November 2026
The page’s words
leaving them as ” mailpoet1._domainkey”, “mailpoet2._domainkey”, “_mailpoet”, and “_dmarc”
- DKIM CNAME target None
- kb.mailpoet.com gives none, read 20 November 2026.The page names the selectors but not their target.
Emma
- MX host None
- help.myemma.com gives none, read 20 November 2026.
- SPF include None
- help.myemma.com gives none, read 20 November 2026.
- DKIM selector
e2ma-k1Emma’s if the CNAME points under a Emma DKIM target - help.myemma.com, read 20 November 2026
The page’s words
e2ma-k1._domainkey e2ma-k1.dkim.e2ma.net.
- DKIM selector
e2ma-k2Emma’s if the CNAME points under a Emma DKIM target - help.myemma.com, read 20 November 2026
The page’s words
e2ma-k2._domainkey e2ma-k2.dkim.e2ma.net.
- DKIM selector
e2ma-k3Emma’s if the CNAME points under a Emma DKIM target - help.myemma.com, read 20 November 2026
The page’s words
e2ma-k3._domainkey e2ma-k3.dkim.e2ma.net.
- DKIM CNAME target
dkim.e2ma.net - help.myemma.com, read 20 November 2026
The page’s words
e2ma-k1._domainkey e2ma-k1.dkim.e2ma.net.
Other selectors the checks try
DKIM selectors that are not among the records of any provider above, each with the service or program that uses it and the page or the DNS lookup it comes from. A key at one of them is never credited by its name alone.
mailUsed by Brevo- developers.brevo.com, read 20 November 2026
The page’s words
"dkim_record": { "host_name": "mail._domainkey", "type": "TXT"
defaultUsed by cPanel- support.cpanel.net, read 20 November 2026
The page’s words
By default, cPanel systems use "default._domainkey" as the DKIM selector.
dkimUsed by rspamd- docs.rspamd.com, read 20 November 2026
The page’s words
# Default selector to use selector = "dkim";
mandrillUsed by Mailchimp Transactional (Mandrill)- Seen in DNS on
mandrillapp.comon 20 November 2026 mailjetUsed by Mailjet- dev.mailjet.com, read 20 November 2026
The page’s words
"DKIMRecordName": "mailjet._domainkey.example.com."
intercomUsed by Intercom- intercom.com, read 20 November 2026
The page’s words
Selector : intercom Domain : yourdomain.com
cmUsed by Campaign Monitor- help.campaignmonitor.com, read 20 November 2026
The page’s words
Fourth level domains — For example, cm._domainkey.example.com.
xUsed by DirectAdmin- docs.directadmin.com, read 20 November 2026
The page’s words
dkim_selector=x The selector to be used for dkim records.
acdkim1Used by ActiveCampaign- help.activecampaign.com, read 20 November 2026
The page’s words
like acdkim1._domainkey (most common)
cf-bounceUsed by Cloudflare Email Sending- developers.cloudflare.com, read 20 November 2026
The page’s words
TXT cf-bounce._domainkey.yourdomain.com
a1Used by Aruba- guide.aruba.it, read 20 November 2026
The page’s words
Per la configurazione DKIM del servizio email Aruba descritta in questa guida, il selector utilizzato è a1 .
How the data is checked
Every week, a script checks that each source link still opens, that each provider’s SPF include still publishes an SPF record, and whether an RFC this site cites has been replaced. A page that turns away automated visits is left for a person to open.
A person reads each provider’s page again at least every three months, and each value above shows the day its page was last read, or the day it was seen in DNS.
Last weekly check that passed: 20 November 2026. Data version 2026.11.20.3.
The checker these values feed is tested every week against badmail.dev, a zone of test domains, most of them broken on purpose.
Download and cite
The data as JSON, with its JSON Schema. Every version stays online at its own address, such as /data/archive/2026.11.20.3.json.
The data is licensed under CC BY 4.0. To credit it, name “Postmaster of Puppets, https://postmasterofpuppets.com/data/”.
The words under “The page’s words” are quoted as published on the page each entry links to. They are not covered by the CC BY 4.0 license of this dataset.
The data is provided as is, without warranty of any kind. Check a value against its source before you rely on it.
Changes
Changes to the data, the email standards and the rules of large receivers, newest first. Follow the changes in a feed reader (Atom). What Gmail, Yahoo and Outlook.com ask of senders is in sender requirements.
Two source pages moved: Microsoft 365’s MX and Postmark’s Return-Path
Microsoft moved the page on SMTP DANE that backs mx.microsoft as Microsoft 365’s MX, and Postmark renamed the address of its page on the custom Return-Path. Both sources now link the new addresses, read again on this day. The quote from Microsoft is still on its page, word for word, and Postmark’s page still gives a CNAME to pm.mtasv.net and no SPF include. No value changes.
Sources
- Microsoft, How SMTP DNS-based Authentication of Named Entities (DANE) works, read 20 November 2026
- Postmark, How do I add a custom return-path?, read 20 November 2026
A key at the selectors smtp or mx is no longer credited to Mailgun
Mailgun’s pages name smtp and mx among its DKIM selectors, and both stay in Mailgun’s list. Other services and self-hosted servers sign with these names too, and Mailgun’s pages give no CNAME target for them, so a DKIM key at the selector smtp or mx is no longer credited to Mailgun. A key at Mailgun’s selectors pic, krs and mailo still is.
Sources
- Mailgun, Cloudflare DNS Setup Guide, read 20 November 2026
- Mailgun, Domain Verification Setup Guide, read 20 November 2026
Emma joins the list, and the DKIM selectors go from 73 to 76
Emma publishes its DKIM keys at the selectors e2ma-k1, e2ma-k2 and e2ma-k3, each a CNAME to a name under dkim.e2ma.net. A key at one of these selectors is Emma’s when its CNAME points there.
Sources
- Emma, DKIM Authentication Setup, read 20 November 2026
Versions 2026.11.20.2 and 2026.11.20.3 give a check date that does not cover their data
The archived copies of data versions 2026.11.20.2 and 2026.11.20.3 give 20 November 2026 as the day of their last weekly check (dateVerified). That check ran on older data. It never read the new source page of Amazon SES’s DKIM target in version 2026.11.20.2, nor the moved pages of Microsoft 365 and Postmark in version 2026.11.20.3. No weekly check had passed on the data of either version when it was archived, so in both copies the field should be empty (null).
Each archived copy stays as it was published, so a citation of it keeps pointing at the same file. Versions archived from now on leave the field empty, since a version is cut on the day its data change, before a weekly check can read them. The day of the last weekly check that passed on the current data is on /data/ and in the current JSON.
Sources
- Postmaster of Puppets, data version 2026.11.20.2, read 20 November 2026
- Postmaster of Puppets, data version 2026.11.20.3, read 20 November 2026
Amazon SES gains its DKIM target and Strato its SPF include
A DKIM key whose CNAME points under amazonses.com is now credited to Amazon SES: its page on creating identities gives the CNAME records under that name. The include _spf.strato.com is now Strato’s, from Strato’s page on DNS records.
Sources
- Amazon SES, Creating and verifying identities in Amazon SES, read 20 November 2026
- STRATO, DNS-Einträge bei STRATO verwalten: Alle Infos, read 20 November 2026
The source of Amazon SES’s DKIM target now links the HTML page
The source of amazonses.com as Amazon SES’s DKIM target linked the Markdown copy of its page on creating identities. It now links the HTML page and quotes it as that page shows it. The value does not change.
Sources
- Amazon SES, Creating and verifying identities in Amazon SES, read 20 November 2026
The provider list grows to 30 and the DKIM selector list to 73
Sixteen providers join the list: Klaviyo, Zendesk, Mailchimp Transactional, Hostinger Email, IONOS, Gandi Mail, Migadu, Namecheap Private Email, Purelymail, mailbox.org, Strato, MailerLite, Help Scout, Constant Contact, Squarespace Email Campaigns and MailPoet. The DKIM selector list goes from 31 to 73 selectors, with 44 new ones from the pages below.
Microsoft 365, Fastmail, iCloud+, SendGrid and Mailchimp gain the CNAME targets of their DKIM keys, so a DKIM key whose CNAME points under one of these names is credited to that provider. Mailchimp’s target, mcsv.net, was seen in DNS on mailchimp.com and intuit.com; the others come from the pages below. SendGrid gains the selector m1, and Mailgun gains krs and mailo.
The selectors everlytickey1 and everlytickey2 leave the list, since no Everlytic page that names them could be read. The selector k1 is no longer Mailgun’s, since no Mailgun page names it, and the selector mail is no longer Brevo’s, since other services sign with it too. Both stay in the list.
Sources
- ActiveCampaign, Set up your sending domain, read 20 November 2026
- Aruba, Come usare il protocollo DKIM, read 20 November 2026
- Brevo API reference, Create a new sender domain, read 20 November 2026
- Campaign Monitor, Use your own domain names with Campaign Monitor, read 20 November 2026
- Cloudflare, Domain configuration, read 20 November 2026
- Constant Contact, Update your DNS records through your hosting provider to finish setting up self-authentication, read 20 November 2026
- DirectAdmin, All directadmin.conf values, read 20 November 2026
- Fastmail, Manual DNS configuration, read 20 November 2026
- Gandi, How To Protect Your Email Against Being Spoofed, read 20 November 2026
- Help Scout, Use DKIM to Help With Email Delivery, read 20 November 2026
- Hostinger, What are the DKIM records for Hostinger Email?, read 20 November 2026
- Apple, Set up an existing domain with iCloud Mail, read 20 November 2026
- Intercom, Troubleshooting email authentication issues (DKIM, DMARC, and DNS Setup), read 20 November 2026
- IONOS, Email Authentication with DKIM, read 20 November 2026
- Klaviyo, How to set up a branded sending domain, read 20 November 2026
- mailbox.org, How to improve spam reputation and avoid delivery errors, read 20 November 2026
- Mailchimp Transactional, Authentication and Delivery, read 20 November 2026
- MailerLite, How to authenticate a domain with Cloudflare, read 20 November 2026
- Mailgun, Cloudflare DNS Setup Guide, read 20 November 2026
- Mailjet, SPF and DKIM validation, read 20 November 2026
- MailPoet, Email Authentication: SPF, DKIM, DMARC, read 20 November 2026
- Microsoft, Set up DKIM to sign mail from your cloud domain, read 20 November 2026
- Migadu API, read 20 November 2026
- Namecheap, How to set up a DKIM record for Private Email, read 20 November 2026
- Purelymail, Custom Domain Setup, read 20 November 2026
- Twilio SendGrid, Configure domain authentication, read 20 November 2026
- Squarespace, Verify your third-party domain for use with Email Campaigns, read 20 November 2026
- STRATO, DNS-Einträge bei STRATO verwalten: Alle Infos, read 20 November 2026
- Zendesk, Digitally signing your email with DKIM, read 20 November 2026
Mailchimp no longer has an SPF include
The include servers.mcsv.net leaves Mailchimp’s SPF includes. Mailchimp’s page on domain authentication asks for two CNAME records and a DMARC record, and for no SPF record.
Sources
- Mailchimp, Set Up Email Domain Authentication, read 20 November 2026
DMARC is now RFC 9989, with its reports in RFC 9990 and RFC 9991
RFC 9989 is the DMARC standard and replaces RFC 7489 and RFC 9091. Aggregate reports move to RFC 9990 and failure reports to RFC 9991, which also updates RFC 6591. The three are Proposed Standards, published in May 2026.
Sources
- RFC 9989, Domain-Based Message Authentication, Reporting, and Conformance (DMARC), read 20 November 2026
- RFC 9990, Domain-Based Message Authentication, Reporting, and Conformance (DMARC) Aggregate Reporting, read 20 November 2026
- RFC 9991, Domain-Based Message Authentication, Reporting, and Conformance (DMARC) Failure Reporting, read 20 November 2026
- IETF Datatracker, RFC 9989, read 20 November 2026
Report a mistake
Found a value that is wrong or out of date? Write to hey@postmasterofpuppets.com.