What does “451 4.7.24 The SPF record of the sending domain has one or more suspicious entries” mean?
Gmail found entries in your SPF record that it treats as suspicious.
Last read from the sources at the foot of this page.
The SPF record of the sending domain has one or more suspicious entries
What does it mean?
The record lists who may send as your domain. When it lists far more than the services you use, it no longer tells a mail server anything.
What exactly does the source say?
451 4.7.24 The SPF record of the sending domain has one or more suspicious entries. To protect our users from spam, email sent from your IP address has been temporarily rate limited. For more information, go to Email sender guidelines.
Gmail's page writes domain-name and ip-address where your bounce shows your own domain and the sending address.
550 5.7.24 The SPF record of the sending domain has one or more suspicious entries. For more information, go to Email sender guidelines.Why would a small firm see it?
An old entry nobody removed, a very wide range of addresses, or a record that ends in +all, which the standard reads as pass for every server.
How do I fix it?
- Read your SPF record: the TXT record at your domain that starts v=spf1.
- Match each entry to a service you use today.Take out the ones you cannot match.
- End the record with ~all or -all, never +all.
Keep one SPF record. Add the service inside the one record you have, before its last word, and keep every service already in it. A second SPF record makes the check fail for every message.
An SPF record may make at most 10 DNS lookups. Each include counts, and so do the includes inside it. Past 10 the check fails, so take out services you no longer use before adding a new one.
What else do the sources say?
The "all" mechanism is a test that always matches.
possible qualifiers, and the results they cause check_host() to return, are as follows: "+" pass "-" fail "~" softfail "?" neutral
Where does this come from?
- Google Workspace: Gmail SMTP errors and codesknowledge.workspace.google.comRead 14 October 2026
- RFC 7208, Sender Policy Frameworkrfc-editor.orgRead 14 October 2026
See what is open before anyone else does.
We read from outside, find each way in first, and show it with a check anyone can re-run. No access, nothing tested, no obligation.
- We read your firm from outside.
- You see what is open, with the proof for the lead finding.
- If it is worth it, you order.
What happens if you go ahead. More at getleaktrace.com/see-it-first/.
Read the transcript
- 72 hours. One domain. Nothing to install.
- Discover. Every way in, found from outside.
- Validate. Every finding, proven. Dated and checkable by anyone.
- Close. Forged email: one click per step, where we reach your DNS host and you approve it.
- You get the fix for the rest, step by step, and we re-check until it is closed.
- Monitor. On monitoring: email settings, look-alikes and new host names re-checked every hour. Alerts within the hour.
- Every paid assessment is human-verified before release.
- The AI defense layer for businesses. getleaktrace.com/see-it-first/