The selector
Every DKIM-Signature header carries s= (the selector) and d= (the signing domain). Together they name the key. A domain can publish many keys, one per provider or per rotation, each under its own selector.
Enter a domain and, if you know it, the selector from one of your emails. The checker looks up the public key in DNS and says whether it is published or revoked. SPF, DMARC and MX are checked too.
Your provider signs each email with a private key. Receivers fetch the matching public key from DNS and check the signature. To find that key, you need its selector.
Every DKIM-Signature header carries s= (the selector) and d= (the signing domain). Together they name the key. A domain can publish many keys, one per provider or per rotation, each under its own selector.
The public key is a TXT record at <selector>._domainkey.<domain>, or a CNAME to your provider's copy. It reads v=DKIM1; k=rsa; p=<key>. An empty p= means the key is revoked and mail signed with it fails.
1024-bit RSA keys still validate, but 2048 bits is the current recommendation and Google Workspace's default. A 2048-bit key is too long for one 255-character TXT string, so DNS splits it into several; that is normal.
DNS cannot list the selectors a domain uses. The checker tries the common ones (google, selector1, selector2, k1, s1, mail, ovh and more). Amazon SES, Resend and many platforms use their own or random selectors: enter the s= value from one of your emails.
Read more: SPF, DKIM and DMARC explained · DKIM key rotation
Mailbase writes SPF, DKIM, DMARC and the reply MX when you add or buy a domain, then raises its volume only while real bounces and complaints stay low.
We respect your privacy. Mailbase uses essential cookies to keep you signed in, and anonymous audience measurement without cookies (PostHog). Only with your consent: full product analytics and advertising measurement (PostHog, Google Analytics, Google Ads). Declining stops all measurement. See our Privacy Policy.