How to Set Up DMARC, SPF, and DKIM to Improve Deliverability

Marios ChaidousisBy 7 min read
How to Set Up DMARC, SPF, and DKIM to Improve Deliverability

To understand how to set up DMARC, first make sure SPF and DKIM are configured for every service that sends email using your domain. Then publish a DMARC record with a monitoring policy, review reports for legitimate senders, and move to a stricter policy only when you know those senders pass authentication.

What SPF, DKIM, and DMARC do

These three DNS-based email authentication methods work together. SPF says which sending servers are allowed to send for your domain. DKIM adds a cryptographic signature that receiving systems can verify. DMARC checks whether SPF or DKIM aligns with the domain your recipient sees in the From address, and tells receiving systems how to handle messages that fail.

Authentication can help protect your domain from spoofing and support deliverability, but it does not guarantee that messages land in the inbox. Consent, list quality, sending patterns, message content, and recipient engagement still matter.

RecordWhat it checksWhere you get the value
SPFWhether the sending server is authorizedYour email provider’s DNS instructions
DKIMWhether a message has a valid domain signatureYour provider’s authentication or domain settings
DMARCWhether SPF or DKIM passes and aligns with your From domainYou create the policy and reporting address

Before you change DNS

Make a list of every system that sends email using your domain. Include your regular business mailbox, newsletter platform, website contact forms, online store receipts, booking reminders, invoicing software, and any CRM or support tool. A forgotten sender is one of the most common reasons a stricter DMARC policy disrupts legitimate mail.

Check the domain in the visible From address, not just the website domain. Your email provider may ask you to authenticate a sending subdomain such as news.example.com. Follow its instructions for the exact domain, record type, host name, and value. DNS control panels use different labels, and some providers automatically append your domain to the host field.

Before editing, save or screenshot the existing DNS records. If a record already exists, update it carefully rather than creating a duplicate. DNS changes can take time to appear across the internet, so do not assume a record is wrong just because it is not visible immediately.

How to set up DMARC: a step-by-step rollout

  1. Inventory your senders. Ask your team and check your website, store, and software settings. Note the From domain and the service used for each message type.
  2. Set up SPF and DKIM. Copy the required DNS records from each provider. Confirm that your domain is verified in each sending service before moving on.
  3. Publish a monitoring DMARC record. Add a TXT record at the host _dmarc, using a reporting address you control. Start with p=none so you can observe authentication results without asking receivers to quarantine or reject failures.
  4. Review reports. Look for sources you recognize, unexpected senders, and messages that fail SPF or DKIM alignment. Some reporting tools turn the XML data into readable summaries; raw reports can be difficult to interpret.
  5. Fix legitimate failures. Correct the sender’s SPF or DKIM configuration, or stop using an unknown service. Recheck the records and send test messages from each legitimate system.
  6. Increase enforcement gradually. Once legitimate sources authenticate consistently, consider p=quarantine and later p=reject. Make a change only when you understand the report data and have tested important mail flows.

A basic monitoring record can look like this. Replace the example domain and reporting address with your own, and check your DNS provider’s format before publishing.

Host: _dmarc.example.com
Type: TXT
Value: v=DMARC1; p=none; rua=mailto:[email protected]

The rua address receives aggregate reports, not ordinary customer emails. Use an inbox or reporting service that is intended to receive them. If you do not want to collect reports, you can omit rua, but monitoring will be more difficult.

Configure SPF and DKIM without breaking other senders

SPF: keep one record per domain

Your SPF record is a TXT record that lists permitted senders. Your email provider supplies the specific include value or IP address to use. Do not copy an include value from another business or guess what it should be.

A simplified example is v=spf1 include:YOUR-PROVIDER-SPF-DOMAIN -all, but the placeholder is not a working value. If multiple services send from the same domain, combine their authorized sources into one SPF record. Publishing multiple SPF records for a domain can cause a permanent error. Avoid adding senders you no longer use, and ask your provider before changing the final qualifier.

DKIM: publish the key supplied by your provider

DKIM records are usually provided as a TXT record or as one or more CNAME records. The host often includes a selector, such as selector._domainkey, but both the selector and destination or key value are specific to your provider. Add the record exactly as given, then use the provider’s verification tool to confirm it can find the key.

If you use several sending services, each may require its own DKIM selector. Keep a note of which service owns each record. When you stop using a service, confirm its records are no longer needed before removing them.

Choose a DMARC policy and understand alignment

The p tag sets the requested policy: none for monitoring, quarantine for messages that fail, and reject for stronger enforcement. A strict policy can affect real mail if a sender has not been configured correctly. Start with p=none, identify and fix legitimate failures, and only then consider a stronger policy.

DMARC alignment is what connects authentication to your visible From domain. With relaxed alignment, a related organizational domain can match; strict alignment requires an exact match. Relaxed alignment is the default when you leave adkim and aspf unspecified. Most small businesses should avoid changing alignment settings until they have a reason and understand the effects.

For a small business, take care with messages from your website, booking system, or accounting tool. A customer may rely on a password reset, appointment confirmation, or invoice. Test those flows after DNS changes, not just your regular newsletter.

Verify your records and investigate failures

Use your domain host’s DNS lookup tool or a reputable DNS checker to confirm that the records are publicly visible. Then send test messages from each legitimate platform to a mailbox where you can inspect the authentication results. Look for SPF, DKIM, and DMARC results in the message details or original headers.

If a result fails, check the exact domain being evaluated, the record host name, spelling, quotation marks, and whether a provider expects TXT or CNAME. SPF can fail when a sender is missing from the record or when the domain has multiple SPF records. DKIM can fail if a selector is incorrect or the provider has not finished enabling signing. Forwarding can also affect SPF, which is one reason DKIM is important.

For customer-facing email, test the full journey: submit a website form, place a test order if possible, trigger a password reset, and send a campaign to an internal test address. Authentication is one part of inbox placement, so continue to monitor bounces, complaints, and unsubscribe requests.

DMARC setup checklist for a small business

  • List every service that sends mail using your domain.
  • Authenticate the correct From domain in each provider.
  • Publish one SPF record that includes all required senders.
  • Add the DKIM records supplied by each provider.
  • Create a DMARC TXT record at _dmarc and start with p=none.
  • Use a monitored reporting address and review the reports.
  • Test forms, receipts, booking messages, password resets, and campaigns.
  • Move to quarantine or reject only after legitimate sources pass consistently.

If you need to ask a vendor for the right DNS values, send a direct request like this:

Subject: DNS records needed to authenticate our email domain
Please send the exact SPF and DKIM records required for our From domain, including each record type, host name, and value. Please also confirm whether your service uses a custom return-path domain and how we can verify that authentication is active. We are reviewing DMARC reports before enforcing a stricter policy.

A practical email authentication resource

Free DNS tools and your email provider’s domain settings are enough to publish and check these records. If you use MailFlow for campaigns, its help center is the place to review product setup guidance. Authentication still needs to be configured at your domain host and checked for every service that sends on your behalf.

Keep authentication separate from permission to email. SPF, DKIM, and DMARC do not make an unsolicited list appropriate to contact. Review the anti-spam policy for a reminder of responsible sending practices.

Conclusion: start in monitoring mode

To set up DMARC safely, inventory your senders, publish the SPF and DKIM records they require, and add a DMARC record with p=none. Review reports, fix legitimate failures, and test important customer messages before moving to quarantine or reject. Your next step is to check your domain’s current DNS records and write down every service authorized to send email from it.

Frequently asked questions

Can I set up DMARC without SPF and DKIM?

You can publish a DMARC record without first configuring SPF and DKIM, but it will not provide useful protection if your legitimate mail does not authenticate and align. Set up the records required by your sending providers first, then publish DMARC in monitoring mode and review the results before enforcing a policy.

What should my first DMARC policy be?

For most businesses setting up DMARC for the first time, p=none is a cautious starting point. It lets you collect aggregate reports without requesting that receivers quarantine or reject failing messages. Use the reports to find legitimate senders that need configuration before considering a stricter policy.

How long does it take for DMARC DNS changes to work?

The time varies with your DNS provider, record TTL, and caching by other systems. Check that the record is publicly visible rather than assuming it is active immediately after saving it. If verification fails, confirm the host name and value, then allow time for DNS changes to propagate before troubleshooting further.

Do I need more than one SPF record?

No. A domain should have one SPF record that includes the sending services authorized to use that domain. If several platforms send mail, combine their provider-approved mechanisms into that record rather than publishing multiple SPF records. Ask your providers for their exact values, and remove obsolete entries carefully.

Will DMARC stop my emails from going to spam?

DMARC helps receiving systems verify your domain and apply your requested policy to messages that fail authentication. It can reduce spoofing and address authentication problems, but it cannot guarantee inbox placement. Permission, bounce and complaint rates, sending practices, content, and recipient engagement also affect whether email reaches the inbox.

Author

Founder of MailFlow, software engineer working across the full stack and every major programming language, specialising in AI automation, email deliverability and SEO.

Related articles

Start free with MailFlow

Free plan forever, no card needed. Upgrade when you grow.

See pricing