SPF Lookup & Analyzer
Check and analyze the SPF record for any domain to prevent email spoofing and improve deliverability.
Get Your Full Domain Health Report
Enter your domain to perform the lookup.
SPF Tag Explanations
| Tag | Description |
|---|---|
| v | The version tag. The only allowed value is "spf1". If it's incorrect or the tag is missing, the SPF record will be ignored. |
| ip4 | This tag should include all the IPv4 addresses that are allowed to send emails on behalf of the domain. |
| ip6 | This tag should include all the IPv6 addresses that are allowed to send emails on behalf of the domain. |
| a | The A record tag allows the SPF to validate the sender by the domain name's IP address. If left unspecified, it takes the value of the current domain. |
| mx | The MX record tag checks the MX record of the mail server(s). If left unspecified, it takes the value of the current domain. |
| ptr (Not recommended) | The PTR tag prompts a PTR check for client IP hostname(s). It's not recommended as per RFC 7208 because it requires many DNS lookups and is unreliable. |
| exists | The exists tag checks if an A record exists for a given domain. It's an advanced mechanism used for more complex validation rules. |
| include | The include tag is crucial for a correct SPF record. It delegates authentication to other domains, allowing you to authorize third-party services (like Google Workspace or Mailchimp) to send email on your behalf. |
| all (required) | This required mechanism acts as a default catch-all. It must be at the end of the record and tells receivers how to treat emails from any sender not explicitly authorized. Qualifiers like `-` (Fail), `~` (SoftFail), or `?` (Neutral) determine the action. |
| redirect | The redirect mechanism points to another domain's SPF record. If present, the current record is abandoned, and the one from the redirected domain is processed instead. It's used to delegate SPF authentication entirely. |
SPF Frequently Asked Questions
Privacy & Usage Notice
The domain you enter is used solely to perform the requested DNS lookup and generate the analysis. We log the domain for internal analytics and to monitor tool usage, but we do not store it with any personal identifiers. For more details, please see our Privacy Policy.