Skip to content

TXT Record

A TXT record stores text-based information in DNS and is commonly used for verification, email authentication, and service configuration.

A TXT record stores text-based information within DNS.

TXT records are commonly used by external systems to verify ownership, publish configuration, or support email authentication.

Common Uses

TXT records may be used for:

  • Domain verification
  • SPF
  • DKIM
  • DMARC
  • Search-console verification
  • SaaS verification
  • Security policies
  • Other service-specific configuration

Cloudflare's DNS API documentation describes TXT as a standard DNS record type containing text data. Cloudflare DNS record documentation

What It Looks Like

A TXT record might resemble:

Name: @
Value: service-verification=abc123

Another provider may ask for a record beneath a special hostname such as:

_dmarc.example.com

The exact value should normally be copied from the service requesting it.

Why It Matters

TXT records often look meaningless when viewed outside their original context.

A DNS zone might contain:

google-site-verification=...
v=spf1 ...
v=DMARC1 ...

Each may support a completely different service.

Deleting a record simply because nobody recognizes it can break:

  • Email authentication
  • Domain verification
  • Third-party integrations

TXT Records and Email

TXT records play a particularly important role in email authentication.

Cloudflare's DNS configuration examples include TXT records for SPF, DKIM, and DMARC alongside MX Records. Cloudflare's email DNS configuration examples

Common Problems

Common problems include:

  • Verification record deleted after setup
  • Multiple conflicting SPF records
  • Old vendor verification records never reviewed
  • Record copied to the wrong hostname
  • Quotation or formatting errors
  • Nobody documenting which service owns a value

How to Improve

When adding a TXT record, document:

  • Purpose
  • Provider
  • Date added
  • Owner

Do not modify generated verification or authentication values unless the provider's documentation requires it.