Add a domain-verification TXT record without replacing existing records Print

Quick answer

A verification TXT record proves control to a specific service. Add the exact record at the authoritative DNS provider and preserve unrelated TXT records, especially existing mail authentication.

Before you start

Confirm the service requesting verification and the account you intend to connect. Obtain the hostname and token from that trusted service, identify the authoritative DNS zone, and record the existing TXT values.

Steps

1. Create a TXT record using the requested name and exact value. Follow the DNS provider's hostname format so the domain is not accidentally appended twice.
2. Do not replace SPF, DKIM, DMARC, or another verification value unless that specific replacement is documented and approved. Several TXT records can serve different purposes.
3. Save the record, read it back, and check the exact hostname through a DNS query. Wait for the relevant caches before asking the requesting service to verify again.
4. After successful verification, follow that service's retention instructions. Some records must remain in place for continued ownership or service checks.

Verify the result

The requesting account should show the intended domain as verified, and existing email authentication should remain intact. Keep the token out of public support screenshots when it could authorize an unintended account link.

Troubleshooting and recovery

If verification fails, check authority, spelling, duplicate domain suffixes, quoting, conflicting record types, and cache timing. Do not delete every TXT record to start over.

Email authentication uses its own exact records

For SPF, DKIM and DMARC, use the sending service's requirements and the dedicated SPF, DKIM or DMARC guide. Several unrelated TXT values can coexist at a name, but duplicate SPF policies or duplicate DMARC policies at their respective exact names can cause errors.

Related help

• Find where your domain's DNS is managed before changing records
• Understand SPF, DKIM and DMARC for your business domain
• Change nameservers without losing email and verification records

Official references

• Cloudflare DNS records

Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.