Skip to content
English
  • There are no suggestions because the search field is empty.

1.07 DNS setup: SPF records and DMARC policy for email deliverability

Set up and verify SPF, DKIM and DMARC in Google Workspace so your prospecting emails don't land in Spam and your domain is protected against spoofing.

📘 What it is

SPF, DKIM and DMARC are three records you publish in your domain's DNS to prove that your emails are legitimate. Without them, Gmail, Yahoo and other servers may block your messages or send them to Spam, and third parties could send fake emails in your company's name.

  • SPF: the list of platforms authorized to send email using your domain.
  • DKIM: an invisible digital signature on every email. It lets the receiver check that the email came from your domain and that no one modified it.
  • DMARC: tells the receiving server what to do when an email fails both SPF and DKIM (let it through, send it to Spam, or reject it) and sends you reports.

SPF and DKIM validate email in two different ways. DMARC uses both results to decide the final action. Together they are the minimum standard for any domain that sends professional email.

📍 Where to find it

This setup is done outside Lymera:

  • In the Google Admin console (to generate the DKIM key).
  • In the DNS panel of your domain provider (GoDaddy, Namecheap, cPanel, Cloudflare, etc.).

You need:

  • Administrator access to Google Admin.
  • Access to your domain's DNS panel.
💡 Tip: DNS changes can take between 15 minutes and 48 hours to propagate. It is usually much less.

🛠️ How to do it

Step 1: Publish the SPF record

  1. Go to the DNS panel of your domain provider.
  2. Go to DNS records or DNS zone and create a record of type TXT.
  3. If you only send email from Google Workspace, Google's standard value is: v=spf1 include:_spf.google.com ~all
  4. Save the changes.
⚠️ Important: a domain can only have one active SPF record. If you also send from other platforms (HubSpot, a CRM, invoicing, etc.), include all of them on that same line. Don't create separate SPF records.
⚠️ Important: the SPF standard allows a maximum of 10 DNS lookups per record, and each include: counts as one. If you use many tools, replace some of them with explicit IP addresses (ip4:) to stay under the limit. If you go over it, SPF fails silently.

Step 2: Generate and activate the DKIM key

  1. Sign in to Google Admin with your administrator account.
  2. Go to Apps ➔ Google Workspace ➔ Gmail ➔ Authenticate email.
  3. Select your domain and click Generate new record.
  4. Leave the key length at 2048 bits and click Generate.
  5. Google shows the host name (selector) and the full TXT value. Don't close that screen.
  6. In your DNS provider, create a new TXT record with that data.
  7. Wait for it to propagate (from 30 minutes to a few hours), go back to Google Admin and click Start authentication.
  8. The status should change to Authenticating email: On.
💡 Tip: if Google can't activate DKIM, it is almost always because the record hasn't propagated yet or was copied incompletely. Check it with MXToolbox.

Step 3: Publish the DMARC policy

DMARC is not configured inside Google Workspace. It is a TXT record that you publish directly in your DNS, and it depends on SPF and DKIM already being active.

  1. Go to your domain's DNS panel.
  2. Create a TXT record with host _dmarc.
  3. As the value, use a monitoring policy (p=none) and specify in rua=mailto:... the mailbox that will receive the reports.
  4. Save and wait for propagation.
  5. Check that mailbox: daily reports arrive there in XML format.

We recommend starting in monitoring mode (p=none) to observe without the risk of rejecting legitimate email, and then tightening the policy gradually.

⚠️ Important: if you migrate email providers (for example, you change hosting or MX) and you already have a strict policy (p=quarantine or p=reject), temporarily lower it to p=none. Once everything works, tighten it again.

Step 4: Verify with MXToolbox

Use the free MXToolbox tool (mxtoolbox.com):

  1. SPF: enter your domain and click SPF Record Lookup. You should see "SPF Record Found". If you see "Too many DNS lookups", reduce the include: entries.
  2. DKIM: enter your domain and the google selector, and click DKIM Lookup. The public key must match the one in Google Admin.
  3. DMARC: enter your domain and click DMARC Lookup. It should show the published policy and the reporting address.
✅ Result: all three records are found and correctly written. Your emails have a better reputation and a lower risk of landing in Spam.

❓ Frequently asked questions

❓ What do I do if MXToolbox says "No SPF Record found"?

The record may not have been published in the right zone of your provider, or propagation may still be pending. Check the syntax in your DNS, wait a few minutes and look it up again.

❓ I set up the "rua" address but the emails I receive are unreadable. Is that normal?

Yes. Reports arrive in XML and are designed for analysis tools, not for reading by hand. Those tools turn them into charts of your domain's usage and health.

❓ Do I need to set up all three records?

Yes. SPF, DKIM and DMARC complement each other, and all three together are the recommended minimum for sending professional email.

❓ Can I have two SPF records?

No. Only one is allowed per domain. If you use several platforms, combine them on a single line.

🔧 If something doesn't work

What you seeLikely causeWhat to do
MXToolbox: "No SPF Record found"The record is in the wrong zone or propagation is pendingCheck the TXT record in your DNS and look it up again in a few minutes
MXToolbox: "Too many DNS lookups"You went over SPF's limit of 10 lookupsReduce the include: entries and use ip4: where you can
Google Admin doesn't activate DKIMThe TXT record hasn't propagated or was copied incompletelyVerify the record with MXToolbox, wait, and click Start authentication again
DMARC reports arrive unreadableThey come in XML formatProcess them with a DMARC analysis tool
Your emails still land in SpamOne of the three records is missing or hasn't propagated yetVerify SPF, DKIM and DMARC; if everything is fine, contact your Customer Success Manager

🚀 Next steps