How to Check TXT Records for a Domain
A practical guide to checking TXT records for a domain, understanding what they are used for, and spotting the most common SPF, DMARC, and verification mistakes.
TXT records are the junk drawer of DNS.
That is not a criticism. It is just how they are used in practice.
If a domain needs to publish ownership proofs, email policies, or service-verification tokens, there is a good chance a TXT record is involved.
What TXT records are used for
TXT records often carry:
- SPF policies
- DMARC policies
- provider verification tokens
- other service-specific metadata
That is why TXT lookups show up in so many workflows. They matter to email, certificates, SaaS onboarding, and domain ownership checks.
The fastest way to check TXT records
Use Domain Lookup and inspect the TXT section.
From there, ask three basic questions:
- is the expected TXT record present?
- is it published at the right name?
- does the value match what the provider expects?
That simple checklist catches a surprising number of problems.
Why TXT records confuse people
Because “TXT record” is not one thing.
An SPF record is a TXT record. A DMARC policy is a TXT record. A verification token is a TXT record. But each one may sit at a different name and follow different formatting rules.
So if someone says “the TXT record looks right,” that usually is not enough information.
Common TXT record examples
SPF
Published on the domain itself in many setups.
Example shape:
v=spf1 include:provider.example -all
DMARC
Usually published at _dmarc.example.com
Example shape:
v=DMARC1; p=none; rua=mailto:dmarc@example.com
Verification tokens
Often published at the domain apex or a provider-specific label, depending on the product.
The exact name matters as much as the value.
The most common TXT lookup mistakes
1. Publishing the record at the wrong name
This is the classic one.
The value may be correct, but the hostname is wrong. In DNS, that still counts as failure.
2. Adding the record at the wrong DNS provider
If the domain delegates somewhere else, the “correct” TXT record in the wrong dashboard is still invisible to the public internet.
3. Reading one TXT record and assuming that is the whole story
Some domains have multiple TXT records for different services. That is normal.
The job is not “find any TXT.” The job is “find the TXT record that matches this exact purpose.”
4. Forgetting caching and polling delays
The record may be present and still not be picked up immediately by the external service you are dealing with.
TXT records and email
If the domain sends email, TXT checks often matter just as much as MX checks.
MX tells you where mail goes.
TXT often tells you whether the mail posture is trustworthy.
That is why these guides work well together:
A good TXT lookup workflow
If you want a practical order:
- confirm authoritative nameservers
- confirm the exact hostname for the TXT record
- confirm the exact value
- compare against provider instructions
- wait out caching if the change is fresh
That sequence is boring. It also works.
The short version
TXT records are flexible DNS records used for policy and verification data.
When you check them, do not just ask “is there a TXT record?”
Ask:
- is the right TXT record present?
- at the right name?
- with the right value?
That is the difference between a useful TXT lookup and a false sense of confidence.
Continue reading
Stay in the same investigation track with these closely related guides.
Tools mentioned in this article
Run the same diagnostics to follow along with the guide.