DKIM Record Not Found or Failing: How to Fix It
DKIM needs a public key in DNS and a sender that signs with the matching key.
A DKIM check fails when the receiving server cannot find the public key in your DNS, or when the key does not match the signature on the email. Mail then lands in spam or fails DMARC.
Step 1: Find the selector

Send a test email to a Gmail address, open it, choose Show original and look at the line DKIM-Signature. The value after s= is the selector, for example google or selector1, and d= is the domain.
Step 2: Build the record name

The record lives at selector._domainkey.yourdomain.com. Many DNS panels add the domain for you, so enter only selector._domainkey as the host.
Step 3: Check the record type

Google and most providers give a TXT record starting v=DKIM1; k=rsa; p=.... Microsoft 365 and some services give two CNAME records instead. Use exactly the type your provider shows.
Step 4: Paste the key whole

A long key must be pasted in one piece with no added spaces or line breaks. Some panels need it split into quoted chunks. Check how the panel saves it.
Step 5: Look it up

Use a DKIM checker or run dig TXT selector._domainkey.yourdomain.com. If nothing returns, the record is on the wrong host name or has not propagated yet.
Step 6: Turn signing on

Publishing the record is not enough. In Google Workspace, Microsoft 365 or your email tool, click Start authentication or Enable signing.
Step 7: Wait and retest

Allow up to an hour, then send a new test email and confirm DKIM shows PASS.
Still stuck?
If these steps do not solve it, we fix it for you for a flat $99. Full refund if we do not solve it within 7 days.
Related guides
- WooCommerce Password Reset Emails Not Arriving
- WooCommerce Order Emails Not Sending or Going to Spam
- WooCommerce Admin New Order Email or Notification Not Arriving
- Outlook 'Cannot Send Message' on Mobile Hotspot or Public Wi-Fi: Port Blocks