- Home
- Tools
- Network Tools
- DNS Lookup
- TXT Lookup
TXT Lookup
Read the TXT records of a domain or subdomain: SPF, verification codes and anything else published as text, with long records joined.
What you find in TXT records
A TXT record is a piece of text attached to a name. Nothing in the DNS gives it a meaning; the service that reads it does. A domain usually has several, and they come back in no particular order.
| Starts with | What it is |
|---|---|
v=spf1 | The SPF record: which servers may send mail for the domain |
google-site-verification= | Proof of ownership for Google Search Console or Workspace |
MS=ms | Proof of ownership for Microsoft 365 |
facebook-domain-verification= | Proof of ownership for Meta |
v=DMARC1 | A DMARC policy. Found only at _dmarc. followed by the domain |
v=DKIM1 | A DKIM key. Found only at a selector followed by ._domainkey. and the domain |
So the name matters as much as the type. A lookup of example.com does not show the DMARC policy, and it does not show the record Let's Encrypt asks for either: those sit at _dmarc.example.com and _acme-challenge.example.com. Enter the full name to see them.
A domain may have only one SPF record. A second v=spf1 record does not add to the first; it breaks both, and the two have to be merged.
When the record you expect is not there
- The domain ended up in the name twice. Many control panels add the domain by themselves, so typing
_dmarc.example.comin the host field creates_dmarc.example.com.example.com. Look that name up. - Quotation marks became part of the text. If the answer shows quotes around the value, they were typed into a field that did not need them, and the service that checks the record will not recognise it.
- It is too soon. If the name was looked up before the record existed, resolvers remember for a while that there was nothing. Try again later.
The DNS lookup page asks for all record types of a name at once, and explains TTLs, DNSSEC and which resolver gives the answers.