No DKIM signature configured
Your SPF record shows mail is sent through {provider}, but the DKIM key {provider} publishes at `{value}._domainkey.{org_domain}` is not there.
Why it matters
Your SPF record shows mail is sent through {provider}, but the DKIM key {provider} publishes at `{value}._domainkey.{org_domain}` is not there. DKIM is the signature that proves a message genuinely came from you and was not altered in transit. Without it, forwarded mail commonly fails authentication, your messages are more likely to be filtered as spam, and DMARC has only SPF to rely on — which breaks whenever a message is forwarded.
How ShipReady detects it
Email-authentication DNS records (DMARC / SPF). Almost every AI-built SaaS sends transactional email — password resets, magic links, receipts — through Resend, SendGrid or Postmark. Setting that up gets the mail delivered; it does not stop anyone else sending mail that claims to come from the same domain. Without a DMARC policy, a receiving server has no instruction to reject a forgery, so an attacker can send "reset your password" from the product's own domain and the message will land in the inbox looking authentic. This is the only check in the scanner that reads DNS rather than HTTP. It is also the most deterministic: a record either exists or it does not, so there is no heuristic and no false-positive surface. The one place judgement is required is deciding WHICH domain to ask about — see _organizational_domain.
Detection is deterministic. ShipReady reports this only when it observes the condition directly, and prefers to miss a real problem over inventing one. Rule version 1.1.0.
How to fix it
This is the prompt ShipReady puts in your report — written to be pasted straight into Cursor, Claude Code, or whichever assistant built the app.
Mail for {domain} is sent through {provider}, but its DKIM key is not published in your DNS. Open your {provider} dashboard, find the DKIM / domain-authentication section, and add the CNAME or TXT records it gives you for {domain}. Then verify inside the provider until it reports the domain as authenticated. DKIM matters more than SPF once mail is forwarded — SPF breaks on forwarding, DKIM survives it, so without DKIM your DMARC policy effectively stops protecting forwarded messages.Frequently asked questions
- What does "No DKIM signature configured" mean?
- Your SPF record shows mail is sent through {provider}, but the DKIM key {provider} publishes at `{value}._domainkey.{org_domain}` is not there.
- How serious is it?
- ShipReady rates this medium. Fix soon. Meaningfully weakens a defence or degrades how the site works.
- How do I fix it?
- Paste the fix prompt on this page into Cursor, Claude Code or your AI editor. It is the same prompt ShipReady puts in your report.
- Can I check my own site?
- Yes — ShipReady scans up to ten pages of any public site for free and reports this alongside every other check.
Related checks
Does your site have this?
ShipReady checks this and 73 other things across up to ten pages of your site. Free, no signup.
Scan my site