Record current DNS or website settings before editing production systems. Confirm changes with your actual provider and test after deployment. These guides explain common scenarios; individual configurations vary.
In this guide
- What to check before changing SPF
- Common SPF errors and safe fixes
- Step-by-step validation
- What an SPF checker cannot prove
- Frequently asked questions
What to check before changing SPF
Find the published TXT record
Look up TXT records at the root of your sending domain. An SPF policy starts with v=spf1. You should normally publish one SPF policy for that hostname, even when several providers send mail.
Inventory every legitimate sender
List Microsoft 365, Google Workspace, CRM systems, transactional mail, helpdesk platforms and any third-party sending services. A record that omits an active sender can cause SPF failures.
Check the actual sending domain
SPF evaluates the envelope-from (return-path) domain, which can differ from the address visible in the From header. Check a real message header rather than assuming the visible domain is the SPF identity.
Common SPF errors and safe fixes
Multiple SPF records
Publishing two TXT records that both begin v=spf1 at the same hostname can result in an SPF permanent error. Combine the authorized senders into one valid policy, rather than publishing a second SPF record.
Too many DNS lookups
SPF permits at most ten DNS-querying mechanisms and modifiers during evaluation. Nested includes and redirects count toward this limit. Remove unused services or simplify the policy after confirming sender requirements.
Missing or outdated include
An include must be the value documented by the provider. Avoid copying a generic SPF string from another organization. Confirm the current vendor instructions and remove obsolete includes only after verifying they are no longer used.
Incorrect ending mechanism
~all signals a softfail for unauthorized sources; -all signals fail. Choose enforcement based on a verified sender inventory and test before tightening a production policy.
SPF passes but DMARC fails
DMARC requires an SPF pass with alignment to the visible From domain, or an aligned DKIM pass. A third-party bounce domain can make SPF pass without meeting DMARC alignment.
Step-by-step validation
Run a public SPF check
Enter the domain in the free domain health checker and inspect the SPF record, DNS response and reported warnings.
Compare with your sender inventory
Check that every service sending mail has an authorized path. Confirm each provider’s recommended include or dedicated return-path setup.
Update DNS carefully
Edit the existing TXT policy at your authoritative DNS provider. Keep a copy of the previous value, and avoid changing unrelated records.
Send test messages
Send from each legitimate platform to multiple mailbox providers. Inspect Authentication-Results and the return-path domain to confirm SPF and DMARC behavior.
What an SPF checker cannot prove
Inbox placement requires more than SPF
A valid SPF record does not prove DKIM alignment, reputation, list quality, content quality or inbox delivery. Review DMARC, DKIM and real-message headers alongside SPF.
Frequently asked questions
Can I have more than one SPF record?
For the same hostname, publish one SPF policy. Multiple v=spf1 records can cause a permanent error.
Does SPF alone stop spoofing?
No. DMARC uses aligned SPF or DKIM results to guide handling of messages claiming your domain.
How long do SPF changes take?
Resolvers can cache prior TXT responses according to DNS TTL values. Test after caches have had time to refresh.
Use our Free SPF and domain health checker to review public signals. Results are informational and may not capture account-level settings.
Open free toolWhen to request expert support
If you have multiple sending platforms, a live website migration, authentication failures affecting customers, or conflicting DNS settings, document the symptoms and seek help before making risky production changes. See SPF, DKIM and DMARC configuration or contact our IT support team.