What are TXT records used for?

TXT records store text data in DNS. Primary uses include email authentication (SPF, DKIM, DMARC), domain verification (Google Search Console, Microsoft 365, AWS Certificate Manager), security policies, and custom application data.

Can I have multiple TXT records on the same domain?

Yes, but you can only have ONE SPF record (v=spf1). Multiple TXT records for different purposes (verification, DKIM, etc.) are normal and expected.

Why is my TXT record not appearing?

DNS propagation can take up to 48 hours. Also verify you added the record at the correct subdomain (@ for root, or a specific subdomain). Some registrar UIs require removing quotes around the value.

What is the maximum length of a TXT record?

A single TXT string can be up to 255 characters. For longer records (like SPF), the value is split into multiple strings that are concatenated by the resolver. The total record should not exceed 4096 bytes.

How do TXT records relate to email security?

SPF (v=spf1) authorizes mail servers, DKIM (selector._domainkey) provides cryptographic signing, and DMARC (_dmarc) sets policy for failed authentication. Together they form the email authentication triad.

TXT Record Lookup

View TXT records including SPF, DKIM, and domain verification.

How to Use This Tool

What to Enter: Enter a domain name to retrieve all TXT records including SPF, DKIM, verification tokens, and custom entries.
What You Get: Lists all TXT records with content, TTL values, and automatic classification of record types (SPF, DKIM, verification, custom).

How to Interpret Results

TXT records serve multiple purposes. Records starting with "v=spf1" define email sender policy. Records at selector._domainkey contain DKIM public keys. Records like "google-site-verification=" or "MS=" are domain ownership proofs. Multiple TXT records are normal — domains commonly have 5-15 TXT records for various services.

Common Issues & Troubleshooting

Too many TXT records can cause UDP packet truncation (>512 bytes), forcing TCP fallback and slower resolution. Duplicate SPF records (only one v=spf1 is allowed) cause authentication failures. Stale verification records from decommissioned services waste space but are harmless.

Frequently Asked Questions

Invalid SPF Record DKIM Signature Invalid DKIM Body Hash Mismatch