# Sudden SPF invalid problem relating to Google servers?

**URL:** <https://forum.dmarcian.com/t/sudden-spf-invalid-problem-relating-to-google-servers/1558>\
**Category:** Technical Help\
**Created:** [May 7, 2021, 8:01pm UTC](https://forum.dmarcian.com/t/sudden-spf-invalid-problem-relating-to-google-servers/1558 "2021-05-07T20:01:08Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![aminco](https://avatars.discourse-cdn.com/v4/letter/a/a6a055/32.png) [@aminco](https://forum.dmarcian.com/u/aminco)\
**Post date:** [May 7, 2021, 8:01pm UTC](https://forum.dmarcian.com/t/sudden-spf-invalid-problem-relating-to-google-servers/1558/1 "2021-05-07T20:01:08Z")

</div>

We’ve had our SPF record set up and have been using dmarcian for about a year and it’s been working fine with no problems and no changes.

Starting 2 days ago, we started getting alerts from dmarcian that our SPF record is invalid because **11 DNS lookups required to evaluate the SPF record. The maximum is 10.**

And then, also starting 2 days ago, we started getting these warning message:

![Screen Shot 2021-05-07 at 1.00.38 PM](https://canada1.discourse-cdn.com/flex036/uploads/dmarcian/original/1X/69ca308ee7d768168efa425742e310c790d44d5e.png)

Again, we’ve made no changes to anything recently.

Further research shows more details for the warning: “We recommend you remove the mx mechanism from your SPF record. It is against best practice to have an mx tag in the SPF when using round-robin DNS as it’s likely unnecessary and it also adds an additional DNS look-up.”

This is our SPF record:  
`v=spf1 mx a ip4:70.183.20.242 ip4:205.186.175.107 ip4:104.192.32.80 include:_spf.google.com include:servers.mcsv.net include:_spf.smtp.com include:sendgrid.net include:amazonses.com ~all`

So it seems like I can/should just remove the “mx” text? But I don’t remember why we added it in the first place and whether it will break anything if we remove it. Is that really the best solution?

---

<div class="post-metadata">

**Author:** ![Tomki](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.dmarcian.com/tomki/32/45_2.png) [@Tomki](https://forum.dmarcian.com/u/Tomki)\
**Post date:** [May 11, 2021, 5:07pm UTC](https://forum.dmarcian.com/t/sudden-spf-invalid-problem-relating-to-google-servers/1558/2 "2021-05-11T17:07:25Z")

</div>

Yes, please remove ‘mx’ from the SPF record on that domain; it’s incorrect since you have the include for Google.  
In many cases (and this is one) the use of ‘mx’ is not necessary since it indicates inbound infrastructure, but does not have relation to egress messaging.​

---

<div class="post-metadata">

**Author:** ![aminco](https://avatars.discourse-cdn.com/v4/letter/a/a6a055/32.png) [@aminco](https://forum.dmarcian.com/u/aminco)\
**Post date:** [May 12, 2021, 5:57pm UTC](https://forum.dmarcian.com/t/sudden-spf-invalid-problem-relating-to-google-servers/1558/3 "2021-05-12T17:57:37Z")

</div>

Thank you, @Tomki ! I’ll remove the mx.

---

<div class="post-metadata">

**Author:** ![opvind](https://avatars.discourse-cdn.com/v4/letter/o/e274bd/32.png) [@opvind](https://forum.dmarcian.com/u/opvind)\
**Post date:** [May 18, 2021, 12:59pm UTC](https://forum.dmarcian.com/t/sudden-spf-invalid-problem-relating-to-google-servers/1558/4 "2021-05-18T12:59:05Z")

</div>

You can also remove

> [@aminco](#):
>
> include:servers.mcsv.net

MailChimp use their own servers and domains in the Return-path/EnvelopeFrom, so they should not be included in the SPF record. They’ve recently come to their senses and revised their guidance: [Set Up Email Domain Authentication (mailchimp.com)](https://mailchimp.com/help/set-up-email-domain-authentication/). See also [SPF Problems with MailChimp - dmarcian](https://dmarcian.com/spf_mailchimp_problems/).

Their old advice remains echoed at sites like mxtoolbox. com, though.