A selector tells the checker where to look for a DKIM public key. A not-found result can mean the selector list is wrong, rather than that the sender has never configured DKIM.

Add the actual selector

1. Open PD Modules → Deliverability → Settings.
2. Find DKIM selectors to look for.
3. Confirm the selector names with the mail administrator or the actual sending platform.
4. Enter the names as a comma-separated list, preserving other selectors still in use.
5. Save and recheck the affected domain through an existing finding’s How to fix → Check this domain now, or the next appropriate batch.

The module normalises, deduplicates and filters selector names, then uses at most twenty. Put the selectors you need within that effective list. The field expects a selector name, not a private key or a complete DNS-record value.

Interpret what was found

A key-like TXT value at a tested selector can be recorded. The module’s usable-key test checks for a nonempty public-key field; it does not verify a real message signature or fully validate the key’s cryptographic properties.

An empty public-key value can produce a revoked-key finding, but other unusable formats also need review. A found selector does not establish that the sending platform currently signs with it. A selector lookup failure can also look like no record found.

Resolve uncertainty

Compare the tested selectors with a real authorised sender’s configuration and message authentication evidence. Do not rotate keys or replace working DNS solely to obtain a better grade. Never include a DKIM private key.

See the PD Email Deliverability Blesta guide for related tasks, or explore PD Email Deliverability.