Free Trial

SPF Records

Table of Contents

Although the SPF record type is deprecated, it’s still supported by DNSimple name servers. We will discontinue serving SPF records in the future, so we will create a TXT record with the same content for you.

What’s an SPF record?

An SPF record is a Sender Policy Framework record. It’s used to indicate to mail exchanges which hosts are authorized to send mail for a domain.

SPF record format

SPF records are defined as a single string of text. Here’s an example record:

v=spf1 a mx ip4:69.64.153.131 include:_spf.google.com ~all

The SPF record always starts with the v= element. This indicates the SPF version that is used. Right now, the version should always be spf1 as this is the most common version of SPF that is understood by mail exchanges.

One or more terms follow the version indicator. These define the rules for which hosts are allowed to send mail from the domain, or provide additional information for processing the SPF record. Terms are made up of mechanisms and modifiers.

SPF mechanisms

The following mechanisms define which IP addresses are allowed to send mail from the domain:

  • a
  • mx
  • ip4
  • ip6
  • exists

A mail server will compare the IP address of the sender against the IP addresses defined in the mechanisms. If the IP address matches one of the mechanisms in the SPF record then follow the result handling rule. The default handling rule is + or pass.

The include mechanism allows you to authorize hosts outside of your administration by specifying their SPF records.

The all mechanism matches any address. This is usually used as the last mechanism which defines how to handle any sender IP that did not match the previous mechanisms.

All mechanisms may specify qualifiers for how to handle a match:

  • + for pass
  • - for fail
  • ~ for soft fail
  • ? for neutral

As previously mentioned, the default handling rule is pass, which is the same as the + qualifier.

SPF modifiers

Modifiers are name/value pairs (separated by an = sign) that provide additional information. Modifiers should appear at the end of the SPF record. A modifier may not appear more than once and unrecognized modifiers are ignored.

The redirect modifier is used to point to another SPF record to use for processing. This is used when you have multiple domains and want to apply the same SPF content across those multiple domains. Redirects should only be used if you control both domains, otherwise an include is used.

The exp modifier is used to provide an explanation in case of a - (fail) qualifier is present on a mechanism that is matched.

Note that we currently do not support modifiers in our SPF editing UI, but you may always add them if you are managing your SPF TXT record directly.

Tips for SPF records

Since you may only have one SPF record per fully-qualified name, if you need to add additional modifiers you should add them to your existing SPF record if it’s present.

SPF records are most often specified on your naked domain name. If you need to exceed the number of modifiers allowed in a single SPF record, you may need to send some of your messages from subdomains below your naked domain. For example, if a third-party SaaS sends mail on your behalf, you may need to send email from something.example.com for that provider. This is especially true if you have multiple SaaS providers that send email on your behalf.

If you want to test your SPF records for compliance with the RFCs, you may want to use an online SPF testing tool.

Validation

The reference document for the DNS CAA record is the RFC 4408, clarified by RFC 7208.

Since SPF records are built on top of TXT records, all the TXT record validations apply to SPF records as well. There are extra validations on top of that, explained below.

Each fully-qualified name may have at maximum one SPF record.

There are various limitations on the number of items and lookups permitted in an SPF record:

  • SPF records may not have more than 10 mechanisms that require DNS lookups. These are the include, a, mx, ptr, and exists mechanisms.
  • When evaluating the mx mechanism, the number of MX records queried is included in the overall limit of DNS lookups. Each mx mechanism must not result in querying more than 10 address records.
  • The ptr mechanism is also included in the overall limit. Each ptr must not result in querying more than 10 address records.

Directives

  • A directive can start with a qualifier character. The supported qualifiers are: +, -, ?, and ~
  • A directive is composed of a mechanism and an optional value (some mechanisms allow providing a value after a : character)
  • This is the list of allowed mechanisms and their expected values if any:
    • all
    • include, exists. Expects a domain name as value as in include:example.com
    • ip4. Expects an IPv4 address as value as in ip4:1.2.3.4
    • ip6. Expects an IPv6 address as value as in ip6:2001:DB8::CD30/96
    • ptr. Expects a domain name as value as in ptr:example.com
    • a, mx. Expects either a domain name or a CIDR as value as in a:example.com

Modifiers

  • modifier terms follow a key=value pattern
  • A modifier key can be any valid text excluding the whitespace character
  • A modifier value is expected to be a domain name