# 550 The SPF signature of your email is not valid or missing

**URL:** <https://community.make.com/t/550-the-spf-signature-of-your-email-is-not-valid-or-missing/70109>\
**Category:** Questions\
**Tags:** email\
**Created:** [February 17, 2025, 9:07am UTC](https://community.make.com/t/550-the-spf-signature-of-your-email-is-not-valid-or-missing/70109 "2025-02-17T09:07:38Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Davidof90](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/davidof90/32/6795_2.png) [@Davidof90](https://community.make.com/u/Davidof90)\
**Post date:** [February 17, 2025, 9:07am UTC](https://community.make.com/t/550-the-spf-signature-of-your-email-is-not-valid-or-missing/70109/1 "2025-02-17T09:07:38Z")

</div>

Hello,

I want to send emails to [paid@payhawk.com](mailto:paid@payhawk.com) with the module “Email”.

I get this error message through email: 550 The SPF signature of your email is not valid or missing. For detailed information check our article here

However, when sending my email through my own application (Spark), it works. Both mailing systems (Spark and the Make module) are being sent through my domain, so why are only my emails from Make being rejected?

---

<div class="post-metadata">

**Author:** ![Paul\_Taylor1](https://avatars.discourse-cdn.com/v4/letter/p/f9ae1b/32.png) [@Paul\_Taylor1](https://community.make.com/u/Paul_Taylor1)\
**Post date:** [February 24, 2025, 7:46am UTC](https://community.make.com/t/550-the-spf-signature-of-your-email-is-not-valid-or-missing/70109/2 "2025-02-24T07:46:18Z")

</div>

The issue is likely due to how Make handles email authentication. Spark may be configured correctly with your domain’s SPF, while Make’s module might not be authorized in your domain’s SPF record. Check your domain’s SPF record and ensure Make’s sending IPs are included. Also, review the linked article for any additional requirements from Payhawk.

---

<div class="post-metadata">

**Author:** ![Davidof90](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/davidof90/32/6795_2.png) [@Davidof90](https://community.make.com/u/Davidof90)\
**Post date:** [February 27, 2025, 7:34am UTC](https://community.make.com/t/550-the-spf-signature-of-your-email-is-not-valid-or-missing/70109/3 "2025-02-27T07:34:34Z")

</div>

@Paul_Taylor1 what are the Make’s sending IPs? Our SPF records are limited to 10.

---

<div class="post-metadata">

**Author:** ![samliew](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/samliew/32/13327_2.png) [@samliew](https://community.make.com/u/samliew)\
**Post date:** [February 27, 2025, 9:16am UTC](https://community.make.com/t/550-the-spf-signature-of-your-email-is-not-valid-or-missing/70109/4 "2025-02-27T09:16:45Z")

</div>

> [@Paul\_Taylor1](#):
>
> ensure Make’s sending IPs are included

This is incorrect advice. Make does not send the actual email.

Make logs into your email server using the established connection credentials, and then your email server sends the emails out.

Therefore, including make.com or Make IP addresses in the SPF records wouldn’t have helped.

For more information, see this duplicate question: [Help me understanding SPF signature please!](https://community.make.com/t/help-me-understanding-spf-signature-please/71567)

Hope this helps! Let me know if there are any further questions or issues.

— @samliew

P.S.: Investing some effort into the [Make Academy](https://academy.make.com) will save you lots of time and frustration using Make.

---

<div class="post-metadata">

**Author:** ![Mark\_Elan](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/mark_elan/32/65767_2.png) [@Mark\_Elan](https://community.make.com/u/Mark_Elan)\
**Post date:** [March 10, 2025, 6:19am UTC](https://community.make.com/t/550-the-spf-signature-of-your-email-is-not-valid-or-missing/70109/6 "2025-03-10T06:19:36Z")

</div>

It sounds like the Make module might not be properly authenticated with your domain’s SPF settings. Since emails sent via Spark work fine, it’s likely that Make is missing authorization in your DNS records. You may need to update your SPF record to include the necessary sending servers.

Also, if you’re using a HTML email signature template, ensure it doesn’t interfere with email authentication. Sometimes, additional content can trigger security checks.

---

<div class="post-metadata">

**Author:** ![Davidof90](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/davidof90/32/6795_2.png) [@Davidof90](https://community.make.com/u/Davidof90)\
**Post date:** [March 10, 2025, 9:12am UTC](https://community.make.com/t/550-the-spf-signature-of-your-email-is-not-valid-or-missing/70109/7 "2025-03-10T09:12:39Z")

</div>

Hello Mark,

What would be the included SPF for the Make module?

---

<div class="post-metadata">

**Author:** ![Mark\_Elan](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/mark_elan/32/65767_2.png) [@Mark\_Elan](https://community.make.com/u/Mark_Elan)\
**Post date:** [March 12, 2025, 5:13pm UTC](https://community.make.com/t/550-the-spf-signature-of-your-email-is-not-valid-or-missing/70109/8 "2025-03-12T17:13:22Z")

</div>

Hello David,

You can update your SPF record by including Make’s sending domain. Typically, you need to add `include:spf.make.com` (or the correct SPF entry provided by Make) to your existing SPF record in your DNS settings. Make sure your full SPF record doesn’t exceed the 10 DNS lookup limit, as that can cause validation issues.

Also, if you’re using a [HTML email signature template](https://exclaimer.com/email-signature-handbook/html-email-signature/), ensure it doesn’t interfere with email authentication. Sometimes, additional content can trigger security checks. "

---

<div class="post-metadata">

**Author:** ![Make\_Bot](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/make_bot/32/14661_2.png) [@Make\_Bot](https://community.make.com/u/Make_Bot)\
**Post date:** [June 10, 2025, 4:27pm UTC](https://community.make.com/t/550-the-spf-signature-of-your-email-is-not-valid-or-missing/70109/9 "2025-06-10T16:27:29Z")

</div>


