Opens in a new tab

s1._domainkey and s2._domainkey: SendGrid’s DKIM keys

s1 and s2 are Twilio SendGrid’s DKIM selectors: two CNAMEs into sendgrid.net, one of them signing at a time, so SendGrid can rotate the key without you touching DNS. The same names are used by others — Atlassian’s older setup, Freshworks, and many shops — so the CNAME’s target says whose it is.

WhoseTwilio SendGrid — sending service
Selectors1, s2
Published asTwo CNAMEs, to s1.domainkey.u<account>.wl<id>.sendgrid.net and s2…; SendGrid keeps the key. A single TXT at m1 when automated security is off.
KeyRSA; 2048-bit for domains first authenticated after May 2021 — older ones stay 1024 until re-authenticated
RotationAutomatic: SendGrid alternates s1 and s2, with one active at a time
Before you set it upMail shows “via sendgrid.net” until the domain is authenticated
Where to find itSettings → Sender Authentication → Authenticate Your Domain
Can it go?Once nothing sends through SendGrid for the domain. While it does, removing them makes that mail fail DKIM.

Is Twilio SendGrid’s key on your domain?

Enter a domain — or paste the DKIM-Signature header of a message it sent: we look for Twilio SendGrid’s key under s1 and s2 and smtpapi, check it, and name every other key the domain publishes.

The records

What Twilio SendGrid asks you to publish, with its own values in place of the placeholders:

s1._domainkey.example.com  CNAME  s1.domainkey.u1234567.wl123.sendgrid.net
s2._domainkey.example.com  CNAME  s2.domainkey.u1234567.wl123.sendgrid.net

How it works

The u<number> in the target is the SendGrid account, so the same s1 on two domains pointing at one u-number means one account sends for both. Services that send through SendGrid on your behalf use their own account’s number.

You can choose a custom selector of up to three letters or numbers when you authenticate — to use one domain on several SendGrid accounts, or because another service already has s1. The records are then <custom> and <custom>2.

With automated security turned off, SendGrid gives a single TXT key at m1._domainkey instead, which you must update yourself whenever the sending setup changes.

Common mistakes

  • Entering the full name at a DNS host that appends the domain: s1._domainkey.example.com.example.com.
  • Another service’s s1 on the same domain: only one record can have the name, so one of the two stops verifying.

What changed

  • May 2021 — New domain authentications get 2048-bit keys; re-authenticate with a custom selector to upgrade an older one.

Setting up Twilio SendGrid from scratch? Its SPF, DKIM and DMARC records, and a check of all three.

Questions

My s1 CNAME points to sendgrid.net, but I never signed up for SendGrid. Whose is it?

A service that sends through SendGrid for you — Klaviyo’s older setup, Freshworks, Atlassian’s older setup and many shop platforms did. The u-number in the target is the account; the service whose setup page gave you the record is the owner.

Sources

Checked on 27 September 2026 against these official sources:

Know when a DKIM key disappears

Point your DMARC reports at us and we monitor the keys your mail is signed with — and email you when one stops answering, before receivers start failing your mail. Free for your first domain.

Create a free account