Skip to content
Standard SMTP codes · permanent error

5.7.24: SPF check error

The receiving server could not complete the SPF check for the sender's domain, either because of a temporary DNS problem or because the SPF record is broken.

Standard
Provider
Permanent (5xx)
Class
Sources checked
Author

At a glance

Code
5.7.24
Temporary or permanent
PermanentRefused for good: the message comes back to the sender, and resending it gets the same answer.
Who has to act
The sender. The fix is on the sending side: your domain, your server or your list.
What the server says
5.7.24 SPF validation error

What it means

X.7.24 replaces two older codes from RFC 7208. A temperror (a transient DNS failure during the check) was to be reported as 451 4.4.3, and a permerror (a record that cannot be interpreted) as 550 5.5.2; RFC 7372 registered X.7.24 for both, with reply 451 or 550. So 4.7.24 means the lookup failed for a moment and the sending server will retry, while 5.7.24 means the record itself is invalid and every message will fail until it is fixed. Common permerror causes are two SPF records on one domain, a syntax error, or more than 10 DNS lookups.

Common causes

  • Two separate SPF records on the same domain.
  • A syntax error in the SPF record, such as a misspelled mechanism.
  • More than 10 DNS lookups through include, a, mx and similar mechanisms.
  • A temporary outage at the domain's DNS provider (4.7.24).

How to fix it

  1. 01Look up the domain's SPF record and check it for errors.
  2. 02Merge multiple SPF records into one.
  3. 03Reduce the number of include mechanisms, or replace some with ip4:/ip6: ranges.
  4. 04For 4.7.24, let the queue retry and check that your DNS servers answer.

Sources

What this page rests on, checked on 20 Oct 2026. The explanation is ours; the reply text is the server's.

  1. 550 5.7.23SPF check failed.The SPF check on the sending server's IP address gave a fail result for the sender's domain, and the receiving server's policy rejects such mail.StandardPermanent
  2. 4.4.3DNS or directory lookup failed.The message could not be passed on because a directory server, most often DNS, did not answer; the lookup and the delivery are retried.StandardTemporary
  3. 5.5.2SMTP syntax error.A command from the sending software could not be understood, because its syntax was wrong or the command was not recognised at all.StandardPermanent

5.7.24 at other providers

  1. 550 5.7.24Suspicious SPF record, blocked.Gmail rejected the message because the SPF record of the sending domain contains entries that Gmail considers suspicious.GmailPermanent

Further reading

All 105 standard codesEvery code in the wikiPaste your own bounce

Beat · paid monitoring

A heartbeat for your email.

Beat runs every check on this site on a schedule: 41 checks, 33 blacklists and real inbox placement. The moment something breaks, it tells you what broke, why it matters, and the exact fix.

example.comWatching
  • SPFpass
  • DKIMpass
  • DMARCp=none
  • Blacklists0 of 33

Illustrative. Your domain, every few hours.

Also from us:Pulse: your own sending infrastructureConsulting: $65/hr, no retainer