Configuration8 min read · Updated Jun 2026

Configuring ClearDKIM

ClearDKIM centralises all your DKIM keys from every sending service in one place, with full visibility into key age, volume, and rotation status.

How ClearDKIM works

ClearDKIM takes ownership of the _domainkey subdomain via a single NS delegation record. From that point, ClearDKIM publishes, rotates, and retires DKIM keys for every sender without any further DNS changes on your part.

DNS delegation: one record
_domainkey.yourdomain.com NS <your ClearDKIM nameserver>

Step 1: Add your domain

Navigate to Managed services → ClearDKIM and click Add domain. ClearDKIM looks for the selectors you already use and lists the ones it finds. You add each one, plus any it missed: DNS can’t list every selector, so the search can miss one.

Step 2: Publish the NS delegation

Add the NS record shown in your ClearDMARC dashboard to your DNS zone. This delegates the _domainkey subtree to ClearDKIM’s nameserver. Add every selector you sign with before you change the NS record. Once the NS record is live, only the selectors listed in ClearDKIM are published, and mail signed with any other selector fails its DKIM check.

Step 3: Register your senders

For each sending service, tell ClearDKIM which selector it uses. ClearDKIM generates a fresh 2048-bit RSA key (or Ed25519 for supported receivers) and publishes the public key. You then paste the corresponding private key into the sending service’s DKIM configuration, or let ClearDKIM push it automatically for natively integrated services.

Step 4: Monitor from the key inventory

The ClearDKIM key inventory shows every active selector with:

  • Key age: days since the key was last rotated.
  • Signing volume: emails signed in the last 7 / 30 / 90 days.
  • Key length: 1024-bit keys are flagged for urgent rotation.
  • Last seen: timestamp of the most recent signature verification seen in DMARC reports.

Step 5: Rotate keys

Click Rotate next to any selector. ClearDKIM publishes the new key alongside the old one, waits for the DNS TTL to expire and signatures to migrate, then retires the old key automatically. No manual DNS edits. See DKIM key rotation for rotation policy recommendations.

Was this guide helpful?