---
title: "Multiple SPF TXT records"
description: "Why multiple SPF TXT strings break validation and how to merge includes into a single record."
translationKey: "ts-multiple-spf"
tags: [spf, dns, txt]
publishedAt: "2026-05-01"
lastReviewedAt: "2026-05-01"
indexable: true
faq:
  - question: "What breaks when two SPF TXT records exist at one hostname?"
    answer: "Many receivers treat SPF as invalid or undefined, so legitimate streams may fail SPF-dependent filters even when content looks fine."
  - question: "How do I merge multiple includes without exceeding TXT limits?"
    answer: "Remove obsolete mechanisms, deduplicate redundant includes, and shorten IP lists where possible—some DNS hosts split long TXT across quoted chunks per RFC guidance."
---
> **Canonical:** https://formreceipt.com/docs/troubleshooting/multiple-spf-records

## The rule

Only **one** SPF TXT record should exist at each fully qualified name that sends mail (often the root domain or a subdomain label).

## Merge strategy

Combine every authorized `include`, `ip4`, and other mechanisms into a single `v=spf1 ...` string that stays under DNS TXT size limits.

## Verification

Query live DNS from multiple resolvers after edits—stale caches can hide duplicate TXT strings briefly.