Multiple SPF records: merge authorization without deleting other TXT data

Define the decision

Several TXT records can coexist normally. The conflict is several records beginning with v=spf1 at the domain being evaluated. Deleting every TXT record is unnecessary and can break ownership verification or other services.

Work through the procedure

1. Query TXT at the envelope domain and identify only SPF policies.
2. Map every mechanism to a currently authorized sender.
3. Design one policy containing the needed authorizations and one deliberate final disposition.
4. Check lookup behavior and validate all legitimate services after publication.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

Before: one v=spf1 record for service A and another for service B
Desired: one reviewed policy authorizing both active services
Preserve: unrelated site-verification TXT records
Retest: service A and service B using fresh messages

Read the result

Combining text mechanically can preserve duplicate includes, obsolete vendors or a misplaced all mechanism. Review semantics as well as syntax. Keep an inventory beside the final value so the next administrator understands each authorization.

Check before moving on

1. Check the authoritative answer as well as a recursive resolver.
2. Confirm that exactly one SPF policy remains at the evaluated name.

Limits and next action

Do not remove an unfamiliar sender without identifying its owner. A dormant payroll or invoicing stream may not appear in a short observation window.

Source: RFC 7208: SPF record selection