TXT Record (Text Record) (TXT Record)
The Importance of TXT Record
TXT records carry some of the most important security configurations for your domain. SPF records (which authorize email senders) are TXT records. DMARC policies are TXT records. DKIM public keys are TXT records. Google Search Console verification, Let's Encrypt DNS challenges, and many SaaS integrations use TXT records for domain ownership proof.
Because TXT records serve so many purposes, they can accumulate over time. Old verification records for services you no longer use, duplicate SPF records, or conflicting DMARC policies can cause problems. Having multiple SPF TXT records is a specific violation of the SPF specification and will cause authentication failures.
TXT record management requires attention to syntax. SPF records have a strict format with a 10-lookup limit. DMARC records must start with "v=DMARC1". Malformed records are silently ignored by receiving servers, meaning you might think email authentication is configured when it is actually broken.
How to Test for TXT Record
A DNS health checker shows all TXT records for your domain and validates their syntax. It checks that SPF records are properly formatted, DMARC is correctly configured, and there are no conflicting records. Regular auditing helps catch stale or misconfigured TXT records.
Key Parameters
| Common TXT Record | Purpose | Example |
|---|---|---|
| SPF | Email sender authorization | v=spf1 include:_spf.google.com ~all |
| DKIM | Email signature verification | v=DKIM1; k=rsa; p=MIGf... |
| DMARC | Email authentication policy | v=DMARC1; p=reject; rua=mailto:... |
| Domain verification | Prove domain ownership | google-site-verification=abc123 |