# SPF names a record receivers can't follow

Your SPF record has an `include:` or `redirect=` that receivers can't follow: the name it points to has no SPF record, has more than one, or leads back to a record already on the way. Receivers stop there with an error (permerror), so SPF fails for mail from every service listed after that term. Mail from a service listed before it still passes. A broken `redirect=` is read last, so every message that matched no earlier term fails.

On the result:

```
SPF names a record receivers can't follow
An include or redirect names a record that is missing, has more than one SPF record, or points back to itself, so SPF fails for mail from a service listed after it.
```

[RFC 7208 section 5.2](https://www.rfc-editor.org/rfc/rfc7208.html#section-5.2) says what an include does when the name has no SPF record: a result of `none` makes the include "return permerror". [Section 6.1](https://www.rfc-editor.org/rfc/rfc7208.html#section-6.1) says the same for `redirect=`: "if no SPF record is found … the result is a "permerror" rather than "none"". [Section 4.5](https://www.rfc-editor.org/rfc/rfc7208.html#section-4.5) covers two records: "If the resultant record set includes more than one record, check_host() produces the "permerror" result."

The usual causes:

1. A service you left. It removed the SPF record its include named, or its domain expired.
2. A typing mistake, such as `include:_spf.gogle.com`.
3. A name with two SPF records, often your own subdomain after a second service asked you to add one.
4. A loop: a record that includes itself, directly or through another record. This happens most often with `redirect=` between your own domains.

## Find the term

**See the lookups →** under the finding opens the SPF checker. It lists each term in the order receivers read it and marks the one that fails: "has no SPF record", "finds nothing", "has more than one SPF record" or "includes itself". **Details →** on the result shows your record.

To look it up yourself, put the name from the include in place of `_spf.example-service.com`:

```
dig +short TXT _spf.example-service.com
```

On Windows, use `nslookup -type=TXT _spf.example-service.com`. No line containing `v=spf1` means no SPF record; two such lines mean two records.

## Fix it

1. A service you no longer use: remove its `include:` or `redirect=` from your record.
2. A service you still use: copy the current include from its setup page or support, and replace the old one. Services do rename them.
3. A `redirect=` to a name of your own with no SPF record: publish the record there, or point the `redirect=` at the right name.
4. A name of your own with two SPF records: merge them into one, as [More than one SPF record](/docs/findings/spf-multiple/) explains.
5. A loop: point the `redirect=` or `include:` at a record that doesn't lead back to the one it is in.
6. Run the check again.
