Free tool
SPF Record Checker: test your domain's SPF in seconds
Enter a domain below and our free SPF checker fetches its SPF record, explains every mechanism and flags the issues that break email authentication.
An SPF record checker shows you exactly which servers are allowed to send email for your domain. SPF is one of the three pillars of email authentication, next to DKIM and DMARC, and mailbox providers like Gmail check it on every message. A missing, duplicated or overlong SPF record silently pushes your email toward spam. This tool queries your domain's TXT records live, parses each mechanism into plain language and validates the record against the most common mistakes.
How to use our free SPF record checker
- 1
Type your domain, for example yourcompany.com, into the field above. You can paste a full URL or email address and we extract the domain.
- 2
Click on "Check SPF" or press Enter.
- 3
Read the policy verdict first: it tells you how receivers treat servers you did not authorize.
- 4
Review the mechanism list to confirm every listed service still sends email for you.
- 5
Fix any warning shown: add a missing record, merge duplicates or reduce DNS lookups below 10.
SPF record checker FAQ
What is an SPF record?
SPF (Sender Policy Framework) is a TXT record in your domain's DNS that lists the servers allowed to send email on your behalf. When a message arrives, the receiving server looks up the record and checks whether the sending IP is on the list. It is one of the three authentication standards, together with DKIM and DMARC, that Gmail and Yahoo now require from bulk senders.
How do I add an SPF record to my domain?
Create a TXT record at the root of your domain in your DNS provider's dashboard. The value starts with v=spf1, followed by the mechanisms your email provider documents, and ends with ~all or -all. For Google Workspace the standard record is v=spf1 include:_spf.google.com ~all.
Why can I only have one SPF record?
The SPF specification requires exactly one record starting with v=spf1 per domain. If receivers find two or more, the check returns a permanent error and your mail fails authentication, even if each record is individually correct. Merge all mechanisms into one record instead of adding a second one for a new tool.
What does the 10 DNS lookup limit mean?
Evaluating mechanisms like include, a, mx, exists and redirect forces the receiver to make extra DNS queries. The specification caps these at 10 per check to prevent abuse. Records above the limit return a permanent error, which fails SPF silently. Nested includes count too, so this tool's estimate is a lower bound.
Is SPF enough to keep my email out of spam?
No, SPF is necessary but not sufficient. Since 2024 Gmail and Yahoo require SPF or DKIM at minimum for everyone, and both plus DMARC for bulk senders. Content quality, list hygiene and sending volume also weigh into deliverability. Start with correct SPF, DKIM and DMARC records, then keep your bounce and complaint rates low.
Does SPF affect mail merge campaigns sent through Gmail?
Yes, in your favor. When you send a campaign with Mail Merge for Gmail, the messages go out through Google's own servers, which are already covered by Google's SPF when your domain includes _spf.google.com. That means every campaign email is sent from infrastructure your SPF record explicitly authorizes.
SPF sorted? Time to send.
Mail Merge for Gmail sends personalized campaigns through Gmail's own authenticated servers, straight from Google Sheets.