Email Rejected for SPF, DKIM, or DMARC? How to Add a DMARC Record at Your DNS Provider

Email Rejected for SPF, DKIM, or DMARC? How to Add a DMARC Record at Your DNS Provider

Why Your Email Is Being Rejected

Microsoft (Outlook.com, Hotmail, Live, and MSN), Google, Yahoo, and other large mail providers now check every incoming message for proof that it really came from your domain. That proof comes from DNS records on your domain called SPF and DMARC. If one is missing, the receiving server may refuse the message and send you a bounce-back (sometimes called an "undeliverable" or "delivery status notification").

Common bounce messages include:

  • 550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records
  • 550 5.7.515 Access denied, sending domain YourDomainName.com does not meet the required authentication level
  • Wording such as "failed DMARC," "unauthenticated sender," or "SPF/DKIM/DMARC auth records"

The most common cause is a missing DMARC record. Because your domain's DNS is managed by another company (your registrar or a DNS provider such as GoDaddy, Cloudflare, or Network Solutions), we can't add it for you. The record has to be added at that company.

Replace YourDomainName.com with your actual domain name in every record below. It's a placeholder only.

Records Your Domain Needs

Log in to the company that manages your domain's DNS, open the DNS settings (often called DNS Management, Zone Editor, or Advanced DNS), and confirm both of these records are present.

Record Type Host / Name Value
TXT (SPF) YourDomainName.com (or @) v=spf1 include:mfg.siteprotect.com ~all
TXT (DMARC) _dmarc.YourDomainName.com (or _dmarc) v=DMARC1; p=none; adkim=r; aspf=r

What each record does:

  • SPF lists the mail servers allowed to send email for your domain. include:mfg.siteprotect.com authorizes our outgoing mail servers.
  • DMARC tells receiving servers how to treat mail that fails authentication. p=none is monitoring only: no mail is blocked or sent to junk because of this setting. adkim=r; aspf=r use relaxed matching, which is the right setting for our mail service.

About the Host / Name field: Some DNS providers want the full name (_dmarc.YourDomainName.com), while others add your domain automatically and want only _dmarc. For SPF, the root of the domain is usually entered as @ or left blank. If you enter the full name and the provider adds the domain again, the record ends up at the wrong name (for example, _dmarc.YourDomainName.com.YourDomainName.com) and won't work.

Important Rules for These Records

  • Only one SPF record. A domain may have only one TXT record that starts with v=spf1. Two SPF records cause SPF to fail completely. If you already have one, edit it and add include:mfg.siteprotect.com to it instead of creating a second record.
  • Include every service that sends as your domain. If other services also send mail using your address (for example, Microsoft 365, Google Workspace, Constant Contact, Mailchimp, or your website's contact form), each one needs its own include: in the same SPF record. Example: v=spf1 include:mfg.siteprotect.com include:spf.protection.outlook.com ~all. Check with each service for its exact value.
  • Only one DMARC record. If a _dmarc record already exists, edit it rather than adding another.
  • Start with p=none. Don't use p=quarantine or p=reject unless you've confirmed every service that sends as your domain passes authentication. A stricter policy can send your own legitimate mail to junk or block it.

Optional: receive DMARC reports

If you'd like daily summary reports from receiving mail servers, add a rua= address to the end of the DMARC value, using a mailbox you check:

v=DMARC1; p=none; adkim=r; aspf=r; rua=mailto:postmaster@YourDomainName.com

The reports are technical (XML files), so most customers leave this off.

A Note on DKIM

DKIM is a third type of authentication record. SPF and DMARC records alone will pass security tests.  DKIM is not necessary.

If another service sends email as your domain (such as Microsoft 365 or a newsletter service), that service may provide its own DKIM records. Add those as instructed by that service.

After Adding the Records

  1. Wait for the change to take effect. DNS updates usually take a few minutes but can take up to 24–48 hours, depending on your DNS provider.
  2. Check the records. A free lookup tool such as MxToolbox can confirm that your DMARC and SPF records are published and valid.
  3. Resend the message that bounced.

If messages still bounce after the records are confirmed, forward the complete bounce-back message to support@savemyservice.com. The full text of the bounce shows which server rejected it and why, which lets us confirm whether the cause is on your domain or on the receiving provider's side.