Email Workflows / SPF, DKIM and DMARC deliverability basics

SPF, DKIM and DMARC deliverability basics Advanced

If your bot sends mail from your domain, three DNS records help inboxes trust it: SPF, DKIM and DMARC.

What you'll learn

  • What each record does
  • How to add them
  • Big-sender rules

Before you start

1. In plain words

These are DNS records, entries in your domain's settings.

2. Steps

  1. In your sending service, add your domain; it shows the exact SPF and DKIM records.
  2. Add them in your DNS provider.
  3. Add a DMARC record, starting gently, e.g. v=DMARC1; p=none; rua=mailto:[email protected].
  4. Wait for the service to show "verified".
  5. Later, tighten DMARC to quarantine or reject.
Screenshot: A sending service dashboard showing SPF and DKIM verified.

3. Big-sender rules

Google requires bulk senders (5,000+ messages a day to Gmail) to use SPF, DKIM and DMARC, offer one-click unsubscribe for marketing mail, and keep spam rates low. Yahoo and Microsoft have similar requirements. Even small senders benefit from setting them up.

Ideas to try

  • New domain.
    Check my domain's SPF, DKIM and DMARC and explain what's missing. Don't change DNS.
  • Spam problem.
    My invoices land in spam. Help me find out why.
  • Reports.
    Read this DMARC report and explain it simply.
  • Planning.
    What records do I need to send from both Google Workspace and Resend?

Tips

  • Only one SPF record per domain; combine entries.
  • Change DNS carefully; mistakes affect all your mail.
  • Start DMARC at p=none.

Facts about the Grok Bot app come from Cursor's official Grok Bot documentation. Docs: Google email sender guidelines, DMARC.org overview. Menus and services change; if something looks different, check the official docs or ask your bot.