TXT Lookup
See every TXT record published on a name, such as SPF policies and verification codes, exactly as resolvers return them.
What this tool checks
The TXT lookup asks a public resolver (Cloudflare by default, or Google Public DNS or Quad9) for all TXT records on the name you enter. TXT records hold text that other systems read to make decisions. On a typical domain you will find:
- SPF (
v=spf1 ...), the list of servers allowed to send mail for the domain (RFC 7208); - verification codes for search engines, email platforms, certificate authorities and SaaS tools;
- occasionally other policies or notes.
Some important TXT records live on special subdomains rather than on the domain itself:
| Record | Name to look up |
|---|---|
| DMARC | _dmarc.example.com |
| DKIM | <selector>._domainkey.example.com |
| MTA-STS | _mta-sts.example.com |
| TLS-RPT | _smtp._tls.example.com |
| BIMI | default._bimi.example.com |
How to read the result
Each TXT record is shown on its own line with its TTL. The value is displayed in presentation format: each string in double quotes, separated by spaces when a record has several strings. A record that looks like this:
"v=DKIM1; k=rsa; p=MIIBIjANBgkq..." "...IDAQAB"
is one record made of two strings. Applications join them into one value.
The order of TXT records in the answer has no meaning, and it may change from one query to the next.
Reading a domain’s TXT records at a glance
On a typical company domain, a TXT lookup at the apex returns a mix of records. To make sense of them:
- Find the one record starting with
v=spf1. That is the SPF policy; everything else is not about mail sending. - Records with names like
example-site-verification=orexample-domain-verification=are ownership proofs for specific services. The prefix usually names the service. - Records you cannot attribute to any service may be leftovers from tools you no longer use. Ask around before deleting them.
- The TTL is the same for all records of a name only if your DNS provider sets it that way; each record can have its own.
Common problems and fixes
- Two SPF records. If you see two records that start with
v=spf1on the same name, SPF evaluation fails with a permanent error. Merge them into one. The SPF checker flags this and counts DNS lookups. - Extra quotes inside the value. A record shown as
"\"v=spf1 -all\""was entered with quotes that the DNS panel then quoted again. Remove the quotes you typed. - Record on the wrong name. Many DNS panels append the domain automatically, so entering
_dmarc.example.commay create_dmarc.example.com.example.com. Look up both names to find out. - Truncated DKIM key. If a DKIM key ends abruptly, the panel may have cut it at 255 characters instead of splitting it. Re-enter it in strings of at most 255 characters, or use your provider’s dedicated DKIM option.
- A TXT record on a name that has a CNAME. That is not allowed; the CNAME wins and the TXT is ignored or rejected. See the CNAME guide.
- Too many old verification records. They are harmless but make responses large. Remove those you no longer need, after checking that the service does not re-verify periodically.
Going further
For email-related TXT records, the dedicated checkers parse the content and explain what it means:
- SPF checker: evaluates includes and redirects and counts DNS lookups against the limit of 10.
- DMARC checker: explains the policy, alignment and reporting tags.
- DKIM checker: reads the key published for a selector, its type and size.
- Email checker: all of the above plus MX, MTA-STS, TLS-RPT and BIMI, with a score.
Read the TXT record guide for syntax, limits and examples of each use.
Frequently asked questions
Where do I look up DMARC or DKIM records?
On their own names. DMARC lives at _dmarc.example.com and DKIM at selector._domainkey.example.com. A TXT lookup on example.com shows only the records on the domain itself, such as SPF and verification codes.
Why is my record split into several quoted strings?
Each string in a TXT record can hold at most 255 bytes, so long values are split. SPF, DKIM and DMARC join the strings back together without spaces, so splitting is harmless as long as no characters are lost at the boundaries.
My verification TXT record is published, but the service says it cannot find it.
Check that it is on the exact name the service asked for, that the value has no extra quotes or spaces, and that the service's resolver is not still caching an empty answer. The propagation checker shows whether the authoritative servers already have it.