# More than one SPF record

Your domain publishes two or more TXT records starting `v=spf1`. Receivers can't pick one, so SPF gives an error for every message from your domain, even when each record is correct on its own.

[RFC 7208 section 4.5](https://www.rfc-editor.org/rfc/rfc7208.html#section-4.5): "If the resultant record set includes more than one record, check_host() produces the "permerror" result." For DMARC, SPF then doesn't pass, so your mail passes DMARC only through DKIM.

It usually happens when a new service's setup page says "add this SPF record" and it goes in beside the old one.

On the result:

```
More than one SPF record
Receivers treat two SPF records as an error, so SPF fails for all your mail.
```

## Look it up

**Details →** on your result shows the records. To look them up yourself, put your domain in place of `example.com`:

```
dig +short TXT example.com
```

Count the lines containing `v=spf1`. More than one is this finding. On Windows, use `nslookup -type=TXT example.com`.

## Merge them

1. If every record is only `include:`, `ip4:`, `ip6:`, `a` and `mx` entries and an ending, write one record: `v=spf1`, then the entries from all of them, then one ending. For `v=spf1 include:_spf.google.com ~all` and `v=spf1 include:servers.mcsv.net ~all`, that is `v=spf1 include:_spf.google.com include:servers.mcsv.net ~all`.
2. Keep the gentler ending if they differ: `~all` rather than `-all`.
3. If any record has a `redirect=`, or an entry starting `-`, `~` or `?`, copying entries across can change which servers pass. A record can have only one `redirect=`, and one is ignored once the record has an `all` ending. Ask whoever set them up which servers each one is for, and write the merged record from that list.
4. At your DNS provider, change one record to the merged value and delete all the others.
5. Run the check again. Merging can push the record over 10 DNS lookups; if so, the result shows [SPF goes over its lookup limit](/docs/findings/spf-too-many-lookups/).
