SparkPost — now part of Bird — generates a DKIM selector for each sending domain and publishes the key as a TXT record. On SparkPost’s and Bird’s own domains every one is scph followed by four digits, such as scph0425.
| Whose | SparkPost (Bird) — sending service |
| Selector | scph<MMYY> |
| Published as | A TXT with the key, at a name SparkPost generates for the domain |
| Key | 2048-bit by default through its API; 1024 if your DNS host cannot take long TXT records |
| Rotation | By hand: a new key and selector through the API |
| Where to find it | The sending domain’s DNS settings in the dashboard, or the sending-domains API |
| Can it go? | An old selector once mail is signed with the new one. |
Is SparkPost (Bird)’s key on your domain?
SparkPost (Bird) 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
Copy the name and value SparkPost shows — its own shape:
scph0425._domainkey.example.com TXT v=DKIM1; k=rsa; h=sha256; p=<public key>
How it works
SparkPost does not document the scph naming; it is what every record on its own domains shows. A selector of your own is possible when you bring your own keys.
Common mistakes
- Typing the record by hand instead of copying it: k= must be rsa and h= sha256.
Sources
Checked on 27 September 2026 against these official sources:
- Sending Domains API — developers.sparkpost.com
- DKIM, SPF & DMARC — bird.com