What Is a TXT Record
Learn what TXT records are, how they are used for SPF, DKIM, DMARC, domain verification, and common TXT record mistakes.
Introduction
TXT records are flexible containers for text values. They do not route website or email traffic directly, but they power verification and authentication that many services depend on.
You will encounter TXT records when setting up email authentication, proving domain ownership, or configuring third-party services.
Quick answer
A TXT record stores text in DNS. TXT records are used for SPF, DKIM, DMARC, domain verification, and other machine-readable values. Multiple TXT records are allowed on one hostname, but only one SPF record is valid per domain.
What it means
TXT stands for text. Each TXT record holds one or more quoted strings. Receivers and services read these strings to validate configuration.
- SPF — authorized outbound mail servers (one per domain)
- DKIM — public key for signature verification
- DMARC — policy and reporting at _dmarc hostname
- Verification — Google, Microsoft, SaaS ownership proofs
- Long values may need careful quoting in DNS panels
Where you see this:
- Email authentication (SPF, DKIM, DMARC)
- Google Workspace and Microsoft 365 setup
- Domain verification for analytics, search consoles and SaaS tools
- Some security and anti-abuse configurations
example.com TXT "v=spf1 include:_spf.google.com ~all"
_dmarc.example.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@example.com"
default._domainkey.example.com TXT "v=DKIM1; k=rsa; p=..."Why this matters
Missing or incorrect TXT records break email authentication, block domain verification, and can cause mail to fail or land in spam. Duplicate SPF TXT records are a frequent cause of SPF permerror.
How to check it
- Run DNS Lookup and filter for TXT records on the domain.
- Use SPF, DKIM and DMARC checkers for email-specific TXT records.
- Confirm hostnames: root for SPF, _dmarc for DMARC, selector._domainkey for DKIM.
- Run dig +short example.com TXT for command-line inspection.
- After edits, wait for TTL and re-check from public resolvers.
Look up TXT records
Use DNS Lookup to list TXT records used for verification and email authentication.
Common mistakes
Multiple SPF TXT records
HighMore than one v=spf1 record on a domain causes SPF errors.
Next step: Merge senders into one SPF record and delete duplicates.
TXT added at wrong hostname
HighDMARC on root instead of _dmarc, or DKIM on wrong selector name.
Next step: Publish each TXT record at the hostname the service specifies.
DKIM value split incorrectly
MediumLong DKIM keys broken across lines or quotes incorrectly.
Next step: Republish the full key exactly as your provider documents.
Verification TXT deleted during migration
MediumGoogle, Microsoft or SaaS verification fails after DNS move.
Next step: Restore verification TXT records from provider documentation.
Example
; SPF at root domain
example.com TXT "v=spf1 include:_spf.google.com ~all"
; Google site verification
example.com TXT "google-site-verification=abc123"Frequently asked questions
Can a domain have multiple TXT records?
Yes. Multiple TXT records are allowed on the same hostname, except SPF — only one v=spf1 record is valid per domain.
Where does DMARC TXT go?
At _dmarc.yourdomain.com, not the root domain.
What is the difference between TXT and CNAME for DKIM?
Some providers use TXT for the public key; others use CNAME to delegate the key. Use the format your provider requires.
Do TXT records affect website loading?
Not directly. They are used for verification and authentication rather than routing web traffic.
Related tools
Use these free tools to verify your configuration after applying changes.
Related guides
Browse all Glossary guides →Need help applying this fix?
Send us your domain, report link or issue details. CheckDomainHealth will review the request and route it to the right technical team if hands-on support is needed.
Was this guide helpful?
Your feedback helps us improve our guides for everyone.
Thanks for your feedback!