Skip to main content

​
Why DKIM needs a selector

DKIM records are not kept at a single predictable address. Each one sits under a selector, at selector._domainkey.yourdomain.com, and the selector is chosen by whichever service sends your mail. Google publishes under one, your marketing platform under another. Finding a DKIM record means knowing, or guessing, the selector.

​
Where to find it

Select DNS Tools in the left navigation, then the DKIM Scanner tab.
Enter your domain and select Scan. The tool tries 19 common selectors, among them google, selector1, selector2, default, k1, and dkim. Start here when you do not know what your senders use.

​
When a record is found

The results are headed by a count — “Found 1 DKIM record(s)” — and each record gets its own card showing:
  • The selector, with a Valid badge and the full address it was found at, for example google._domainkey.yourdomain.com.
  • The record itself, with a copy control.
  • A verdict line confirming the record is valid and properly configured.
  • Key Type and Version — for example rsa and DKIM1.

​
No DKIM records found

A No DKIM Records Found result lists the selectors it tried, so you can see what has been ruled out. It does not mean DKIM is missing — it means none of the common selectors matched, and your provider may use a custom one. When this happens, find the selector in your sending platform’s DNS or setup documentation, then use Manual Lookup.

​
Protected by DMARCeye

When the scanned domain is monitored in your account, a Protected by DMARCeye panel confirms it below the results. To publish a DKIM record rather than look one up, use the DKIM Setup path in the DMARC Configurator.