In order to implement SPF you will need to have a valid SPF record. DMARC Analyzer provides a SPF Record Checker to validate your SPF record.
We can also pre-validate an update you intend to apply to your record to prevent issues popping up after the update was done. We recommend you to carefully test any updates to your SPF records before applying them.
Check your SPF Record
DMARC Analyzer is a pure play DMARC specialist with over 15 years of email deliverability experience. We provide user friendly DMARC Analyzer software and we act as your expert guide move towards a reject policy as fast as possible. Sign up for free
Logically we require a SPF record in the DNS so we can validate it.
You can only have 1 SPF record in DNS for each SPF version. If you publish multiple SPF records (v=spf1), this will invalidate your SPF record. Therefor always update your SPF record and do not place a new record beside the existing record.
When using SPF, you can only perform 10 (nested) DNS lookups. Please check our knowledgebase article for more information on subject.
We recommend not to use PTR as this is a deprecated mechanism and several senders may (completely) ignore your SPF record if you use this.
We have detected content which is not in the SPF specification.
If you use the mechanism ‘all’ with a “+” qualifier this means you basically allow anybody to send email on your behalf. The record will first try to match the sending source to another mechanism. If this fails, the default behavior is to still allow this source. Therefore, this setup is discouraged.
Our SPF record checker will try to validate SPF macro’s you use. Using some example data we will give examples of the lookups receivers may do based on your macro setup.
An SPF record should always have a ‘default’ fallback mechanism. This can either be an ‘all’ mechanism or a ‘redirect’ modifier. We check if you end your SPF record with either of these.
A SPF record should have 1 fallback scenario. You have defined multiple.
You have published your SPF record in a DNS type SPF. This DNS type ‘SPF’ (/99) was introduced in RFC 4408 in 2006. However, this type became obsolete by RFC 7208 which states: SPF records MUST be published as a DNS TXT (type 16) Resource Record (RR)
You used uppercase characters in your SPF record. Although it is not a requirement, it is a best practice to publish your SPF records lowercase.
After running your SPF record through all these checks you can safely update your SPF record in your DNS!
|all information about the Sender Policy Framework (SPF)|
|learn how to create an SPF record|
|learn how to validate a SPF record|
|everything you need to know about SPF records|