Lucid Brands Home
©Lucid Brands 2026
Email Marketing resource article: SPF, DKIM and DMARC: Email Authentication Explained

SPF, DKIM and DMARC: Email Authentication Explained

DMARC (Domain based Message Authentication, Reporting and Conformance) is an email security standard that tells inbox providers what to do with messages that claim to come from your domain but fail authentication checks. It builds on SPF, which lists the servers allowed to send your email, and DKIM, which adds a digital signature to each message. You set it up by adding a TXT record at _dmarc.yourdomain.com, starting with a monitoring policy (p=none) and moving to quarantine or reject once all your real email passes.

What is DMARC?

Anyone can put your domain in the "From" line of an email. Criminals use that to send phishing emails that look like they come from your business. DMARC lets you:

  1. Check: inbox providers verify the email passed SPF or DKIM and that the passing domain matches your From address.
  2. Decide: you tell providers what to do with failures: nothing (none), send to spam (quarantine) or block (reject).
  3. Report: providers send you reports about who is sending email using your domain.

Adoption is growing fast. Proofpoint reports DMARC adoption doubled in the past year, with 110,000 new domains implementing it each month.

How SPF, DKIM and DMARC work together

Think of sending email like sending a package from your company.

StandardAnalogyWhat it doesWhere it lives
SPF (Sender Policy Framework)An approved list of couriersLists the servers and services allowed to send email for your domainA TXT record on your domain
DKIM (DomainKeys Identified Mail)A tamper proof sealAdds a cryptographic signature so receivers can verify the message was not changed and came from your domainA public key in a DNS record; the signature is in each email header
DMARCThe instructions on the packageRequires SPF or DKIM to pass and align with the From domain, sets the policy for failures and requests reportsA TXT record at _dmarc.yourdomain.com

You need SPF and DKIM working before DMARC can do its job.

What alignment means

Alignment is the part most people miss. It is not enough for SPF or DKIM to pass. The domain that passed must match the domain in the visible From address.

  • SPF alignment: the domain in the hidden return path matches your From domain.
  • DKIM alignment: the domain in the DKIM signature (the d= value) matches your From domain.

Example: you send a newsletter through an email platform. If the platform signs with its own domain instead of yours, DKIM passes but does not align, so DMARC can fail. The fix is to set up custom DKIM (often called domain authentication) in that platform so it signs with your domain.

DMARC passes if either SPF or DKIM passes and aligns. DKIM is usually the more reliable of the two because it survives forwarding.

Is DMARC required?

For many senders, yes. Proofpoint notes that Google and Yahoo require DMARC for bulk senders sending more than 5,000 emails a day, along with keeping spam rates below 0.3%. Smaller senders also benefit, because:

  • It protects your customers and staff from phishing that uses your name.
  • It helps your real email reach the inbox.
  • It shows you every service sending email as you, including ones you forgot.

Yet many domains stop halfway. Proofpoint reports nearly 75% of senders using p=none have no plans to upgrade their policy, which means they get reports but no protection.

What a DMARC record looks like

A DMARC record is a TXT record at the host _dmarc. A starting record for monitoring:

v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com; fo=1

A stronger record after testing:

v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc-reports@yourdomain.com; adkim=r; aspf=r

A full protection record:

v=DMARC1; p=reject; rua=mailto:dmarc-reports@yourdomain.com; sp=reject

An SPF record example (one per domain):

v=spf1 include:_spf.google.com include:servers.mcsv.net ~all

Replace the include values with the ones your email providers give you. The examples above are illustrations, not values to copy as is.

DMARC tag reference

TagWhat it meansCommon values
vVersion (required, must be first)DMARC1
pPolicy for your domain (required)none, quarantine, reject
spPolicy for subdomainsnone, quarantine, reject
pctPercentage of failing mail the policy applies to1 to 100 (default 100)
ruaWhere to send aggregate reportsmailto:address
rufWhere to send failure (forensic) reports; many providers do not send thesemailto:address
adkimDKIM alignment moder (relaxed, default) or s (strict)
aspfSPF alignment moder (relaxed, default) or s (strict)
foWhen to generate failure reports0, 1, d, s

Relaxed alignment allows subdomains to match the main domain (news.yourdomain.com aligns with yourdomain.com). Strict requires an exact match.

How to set up DMARC

  1. List every service that sends email as your domain. Your mailbox provider (Google Workspace, Microsoft 365), email marketing platform, CRM, help desk, invoicing tool, website forms and booking software.
  2. Set up SPF. Create or update one SPF record that includes each sending service. Keep it under the limit of 10 DNS lookups.
  3. Set up DKIM for each service. In each platform, find "domain authentication" or "DKIM" settings and add the DNS records they provide.
  4. Create a reporting mailbox or sign up for a DMARC reporting tool, because raw reports are hard to read.
  5. Publish a DMARC record with p=none at _dmarc.yourdomain.com.
  6. Check your records with a free lookup tool such as MxToolbox or EasyDMARC.
  7. Read reports for two to four weeks and fix any real sender that fails.
  8. Move to quarantine, then reject using the rollout plan below.

Where to add the record: in the DNS settings wherever your domain is managed, such as your registrar, Cloudflare or your website host. Google Workspace and Microsoft 365 both publish setup guides; follow the current version from your provider, because their screens change.

A rollout plan from none to reject

StageRecord policyHow longGoal
1. Monitorp=none2 to 4 weeksFind every legitimate sender and fix SPF and DKIM
2. Partial quarantinep=quarantine; pct=251 to 2 weeksTest enforcement on a portion of failing mail
3. Full quarantinep=quarantine; pct=1002 to 4 weeksFailing mail goes to spam; watch for complaints
4. Rejectp=rejectOngoingSpoofed mail is blocked

Move to the next stage only when reports show your real email passing. Timelines vary with how many services send for you.

How to read DMARC reports

Aggregate reports (rua) arrive as compressed XML files, usually daily, from providers like Google, Yahoo and Microsoft. Each report lists:

  • The IP addresses that sent email using your domain
  • How many messages each sent
  • Whether SPF and DKIM passed and aligned
  • What the receiver did with the messages

In plain terms, sort every sender into one of three groups:

GroupWhat it meansWhat to do
Known and passingYour real services, set up correctlyNothing
Known but failingYour real services, missing SPF or DKIMFix their authentication
UnknownSpoofing, or a service you forgotInvestigate; if it is not yours, enforcement will block it

A DMARC reporting tool turns the XML into readable dashboards. Many have free tiers for small volumes; check current pricing.

Common problems and fixes

ProblemLikely causeFix
Marketing emails fail DMARCPlatform signs DKIM with its own domainSet up custom domain authentication in the platform
SPF "too many lookups"More than 10 DNS lookups in your SPF recordRemove unused services, or use subdomains for some senders
Two SPF recordsA new tool added a second recordMerge into one record
Forwarded emails failForwarding breaks SPFMake sure DKIM is set up and aligned
Invoices or forms land in spamThe tool sends as your domain without authenticationAuthenticate the tool or send from a subdomain set up for it
Flood of DMARC emails in your inboxrua points to a personal mailboxSend reports to a dedicated mailbox or a reporting tool

Authentication is only one part of reaching the inbox. Read our email deliverability guide and email marketing best practices for list quality, engagement and sending habits. If you send outreach, our cold email guide covers extra precautions.

Authentication checklist

  • Every service that sends email for your domain is listed
  • One SPF record includes all sending services and stays under 10 DNS lookups
  • DKIM is set up with your domain in every sending platform
  • A DMARC record is published at _dmarc.yourdomain.com
  • Reports go to a dedicated mailbox or reporting tool
  • Reports are reviewed weekly during rollout
  • Policy has moved from none to quarantine to reject
  • Subdomains are covered (sp tag) or have their own records
  • Unused domains you own have a DMARC record with p=reject and an SPF record that allows no senders, so they cannot be spoofed
  • Someone owns authentication and checks it when you add a new tool

Using subdomains for different kinds of email

Many businesses send marketing email from a subdomain (such as news.yourdomain.com) and keep the main domain for staff mailboxes. Benefits:

  • Reputation separation: a marketing campaign with high complaints is less likely to affect everyday staff email.
  • Simpler SPF: each subdomain lists only the services that use it.
  • Clearer reports: DMARC reports show which kind of email has problems.

Set up SPF, DKIM and DMARC for each subdomain you send from. With relaxed alignment, a subdomain aligns with the main domain's policy, but giving each sending subdomain its own setup makes troubleshooting easier.

What comes after DMARC

Once you reach p=reject, you have strong protection against direct spoofing of your domain. Keep watching reports, because new tools and staff changes can break authentication without warning. Some brands also set up BIMI (Brand Indicators for Message Identification), which can display your logo next to authenticated emails in supporting inboxes. BIMI requires DMARC at enforcement and, at some providers, a verified mark certificate. Check each inbox provider's current requirements.

FAQ

How do I add DMARC to my email?

Set up SPF and DKIM first, then add a TXT record at _dmarc.yourdomain.com in your DNS settings, starting with v=DMARC1; p=none; rua=mailto:youraddress. Monitor reports and move to quarantine and reject once your real email passes.

Is DMARC really necessary?

For bulk senders, yes: Proofpoint notes Google and Yahoo require it for anyone sending more than 5,000 emails a day. For everyone else, it protects your brand from spoofing and helps deliverability, so it is strongly recommended.

Why am I getting DMARC emails?

Your DMARC record includes a rua address, so inbox providers send you daily reports about email using your domain. To stop them landing in your inbox, point rua to a dedicated mailbox or a reporting service. Do not remove DMARC to stop them.

Does Gmail enforce DMARC?

Yes. Gmail checks DMARC and follows the sending domain's policy, and Google requires DMARC for bulk senders.

Make sure your emails reach the inbox

Lucid Brands' Email Management service, from $500 a month, includes authentication setup and monitoring, list hygiene, campaigns and email automation. We set up SPF, DKIM and DMARC correctly the first time and move you safely to full protection. Contact us to check your setup, or read our guide to email marketing for small business.

Your path to lucidity

Get Started With a Free Website Audit

Not sure where to begin? Start with a free website audit. Our team analyzes your website's SEO, speed, content and user experience to identify what to improve first.