Your test is correct and by opening the explanation you whould have avoided asking this question.
gunsafeslab.com does not allow your server
22.214.171.124 to use
Sender ID is like SPF, but it checks the FROM address, not the bounce address.
What we retained as your current SPF record is:
v=spf1 a mx include:websitewelcome.com include:sendgrid.net ~all
More information about this error:
gunsafeslab.com ... _spf.google.com: Maximum DNS-interactive terms
In order to send mail from Sendgrid your SPF record should have
Now it has
include:spf.websitewelcome.com include:spf1.websitewelcome.com include:_spf.google.com having more includes inside them. This will cause more than 10 DNS queries and the SPF checker will stop. Whether the
126.96.36.199 eventually exists in one of these includes doesn't matter, because it won't get there.
One way to sanitize these superfluous queries would be querying
TXT records of what have been included; try to avoid includes that are only doing more includes. Here's a little chart showing all the DNS queries caused by
"v=spf1 a mx include:websitewelcome.com include:sendgrid.net ~all":
All these causes a new DNS query:
- Red label shows every
include: only containing more
- Orange label shows
include: methods also having actual
ip6 methods (green).
- Yellow label are other methods:
mx needs to be queried separately, too.
Moreover, this has nothing to do with
MX records as they are for receiving mail, not for sending. Also, your
MX are eventually the same server, and could be replaced with single
If you only send mail from this one server and Sendgrid, your minimal SPF record would be:
"v=spf1 ip4:188.8.131.52 include:sendgrid.net ~all"`
That would cause only one extra DNS query. If you also send mail from Gmail, that'd be five with
"v=spf1 ip4:184.108.40.206 include:sendgrid.net include:_spf.google.com ~all"