Free TXT Record Lookup
Enter a domain or any hostname, including names like _dmarc.example.com, to read its TXT records and see what each one is for.
Reading TXT records...
Could not check
No TXT records were returned for this name.
What a TXT Record Lookup Shows
A TXT record lookup returns the free-text records published at a name. DNS gives TXT no fixed meaning, so it became the place everything else goes: email authentication, proof that you own a domain, and settings for services that need to read them from DNS.
A busy domain can hold a dozen of these with nothing to tell them apart, so this tool labels each record by its prefix and flags more than one SPF record. Names with underscores work too: try _dmarc.example.com or a DKIM name such as selector._domainkey.example.com. To have those records graded rather than listed, use the DMARC checker or the email deliverability checker.
- Enter the exact name. TXT records belong to one name, so example.com and _dmarc.example.com return different records.
- We ask a public resolver for every TXT record at that name.
- Read the label on each record to see what it does.
- After a change, check that resolvers have picked it up before you trigger verification.
What this check settles
- Whether a record is live: what public DNS returns now, not what your provider's dashboard says you saved.
- What each record is for: SPF, DMARC, DKIM, MTA-STS and common verification tokens are named.
- Whether SPF is duplicated: two SPF records at one name is an error receivers act on.
Common TXT Records Explained
Most TXT records you will meet are one of these. The location matters as much as the content.
| Record | Where it lives | What it does | Used by |
|---|---|---|---|
| SPF | The domain itself | Starts with v=spf1 and lists the servers allowed to send mail for the domain. Exactly one per name. | Mail servers |
| DMARC | _dmarc.domain | Starts with v=DMARC1 and tells receivers what to do with mail that fails SPF and DKIM alignment. | Mail servers |
| DKIM | selector._domainkey.domain | Holds the public key receivers use to verify signed mail. Each selector has its own name, and some providers use a CNAME here instead. | Mail servers |
| Verification | Usually the domain itself | A token a service asks you to publish to prove you control the domain, such as google-site-verification=. | SaaS tools |
| Other | Anywhere | Anything else: one-off validation tokens, service settings and notes. A record we cannot label is not automatically a problem. | Varies |
How to Read the Result
A label, then the record exactly as DNS returned it.
The verdict
The headlineWhether the name returned any TXT records, and whether more than one of them is an SPF record.
Each record
The sourceThe full value as published. A long record stored as several quoted strings is shown joined, which is how receivers read it.
The label
The purposeDecided from how the record starts. "Other" only means the prefix is not one we recognise.
TTL
The timingHow many seconds a resolver may keep this answer. It shows how long an edit can take to reach everyone, and the number counts down in a resolver's cache.
What a TXT Record Is
A TXT record stores text at a DNS name. It was designed for human-readable notes, and it became the general-purpose field for anything a service needs to look up about a domain.
A name can hold many TXT records at once. Each service looks for the one that starts with its own prefix and ignores the rest, which is why a verification token and an SPF record can sit side by side.
How to Add One Safely
Adding a TXT record takes a minute. The mistakes come from where it goes and what it replaces.
Before you save:
- Check how your DNS provider wants the host: many append the domain for you, so "_dmarc" is right and the full name is not.
- Add a new record rather than overwriting one, unless you mean to replace it.
- Merge SPF changes into the existing record instead of publishing a second.
- Look the name up afterwards, then check propagation if a service still cannot see it.
Where TXT Records Go Wrong
A TXT record that exists is not always a TXT record that works. The common cases:
- Two SPF records, often after adding a new mail service. SPF evaluation then returns a permanent error, so each new sender belongs in the one existing record.
- The right record at the wrong name, such as DMARC on the domain itself rather than _dmarc, or a name doubled to _dmarc.example.com.example.com.
- A single string over 255 characters. DNS limits each string to that length, so long values such as DKIM keys must be split, and some provider dashboards do not do it for you.
- A CNAME on the name. A name with a CNAME cannot hold a TXT record of its own, and a lookup then returns whatever the target publishes. A DNS lookup shows what else is on the name.
Why TXT Records Matter
They carry your email identity
SPF, DKIM and DMARC all live in TXT records. Losing one can send your mail to spam or leave the domain open to spoofing.
They gate your tools
Search consoles, identity providers and SaaS apps use a TXT token to prove ownership. Some re-check it, so removing one can undo the verification.
They show who you use
Verification tokens reveal which services a domain has connected, which is useful when auditing a domain you inherited.
They pile up
Old tokens and senders stay forever unless someone looks. A read of the whole list is where a tidy-up starts.
Who Looks Up TXT Records
One list of records, read for different reasons.
IT & Email Admins
Confirm a record went live before pressing verify, and debug why a service cannot see it.
For DNS monitoringSecurity Teams
Audit the sending services and connected tools a domain has authorised over the years.
For IT & MSPsMarketers & SEOs
Confirm a search console or email platform token is in place before a launch.
For marketersAgencies
Check a client published exactly what you sent them, without asking for DNS access.
For agenciesRelated Email & DNS Tools
A lookup shows the record. These tell you whether it does its job.
Grade your DMARC
Read the policy tag by tag and see whether it actually stops spoofing.
DMARC checkerCheck SPF, DKIM and MX
Grade the whole mail setup in one pass instead of record by record.
Email deliverability checkerFrequently Asked Questions
Common questions about TXT records and how to check them.
How do I check the TXT records for a domain?
Enter the domain in the tool above. It returns every TXT record public DNS holds at that name and labels each one. On the command line, dig TXT example.com gives the same raw records.
What is a TXT record used for?
Mostly email authentication (SPF, DKIM, DMARC) and proving domain ownership to services such as search consoles and identity providers. It can hold other settings too, because it stores plain text.
Can a domain have multiple TXT records?
Yes. A name can hold many TXT records, and each service reads the one it recognises. The exceptions are SPF and DMARC, which must each appear once at their name.
How do I look up a DMARC or DKIM record?
Enter the full name. DMARC lives at _dmarc.example.com, and DKIM lives at selector._domainkey.example.com, where the selector comes from your mail provider. This tool accepts names with underscores.
Why can't I see the TXT record I just added?
The usual causes are a cached old answer, a record saved at the wrong name, or a provider that appended the domain a second time. Look up the exact name, check for a doubled name, and allow for the TTL.
Is it safe to delete old TXT records?
Often, but check first. Some services re-check their verification token, so removing it can undo the connection. Remove a record once you know the service it belongs to is gone.
What is the maximum length of a TXT record?
Each string inside a TXT record can be up to 255 characters, and one record can hold several strings, which receivers join together. That is how a long DKIM key fits.
Why are two SPF records a problem?
The SPF standard says a check that finds more than one SPF record returns a permanent error, so receivers can treat your mail as having failed SPF. Combine the senders into one record.
What does an "Other TXT record" label mean?
Only that the record does not start with a prefix we recognise. It may be a token from a less common service, or something left over. Search for the value's prefix to find who asked for it.
Start Monitoring & Catching Domains Today
Join founders, agencies, and domainers already protecting their portfolio. Your first 5 domains are free.
No credit card required • Cancel anytime
Guides for domain operators
Deep dives on domain names, DNS, SSL, acquisitions and portfolio management.
All guides →
4 Letter Domains: The Complete LLLL Investing Playbook
4 letter domain names represent one of the most liquid segments of the domain aftermarket. All 456,976 possible .com combinations are registered.
.SI Domain: Slovenia's 30-Year-Old ccTLD Is Suddenly Super Intelligence
What is the .SI domain? Learn how Slovenia's country-code TLD went from 10 registrations in 1992 to a 2,199% surge in September 2026, and why 'super intelligence' made .SI the new .AI.
Infringing Domains: Detecting, Monitoring, and Recovering
Your domain is your storefront. Every day, someone registers a lookalike of it, to skim your traffic, phish your customers, or hold it for ransom. This guide covers what infringing domains are, how to find them before they hurt you, and exactly what to do when you do.