Look up a domain's TXT records
TXT records hold text that other services read: SPF, DMARC, verifications… Enter the domain to see them.
What are TXT records for?
A TXT record holds free text that other services read to check something about the domain. The most important uses are:
- SPF (“v=spf1 …”): which servers may send email on behalf of the domain.
- DMARC (at _dmarc.example.com): what to do with messages that fail SPF or DKIM.
- DKIM (at selector._domainkey.example.com): the public key messages are signed with.
- Verifications: Google Search Console, Microsoft 365 or Facebook ask you to add a TXT record to prove the domain is yours.
To see DMARC or DKIM, enter the full subdomain, for example _dmarc.example.com.
Lookups by record type
Frequently asked questions
Can a domain have several SPF records?
No. There can only be one TXT record starting with “v=spf1”; if there are two, SPF fails. Combine every provider into a single record with several “include:” entries.
How long does a DNS change take to propagate?
As long as the old record's TTL: from a few minutes to 24 or 48 hours. Nameserver (NS) changes usually take longer, because the TTL of the delegation in the TLD is high.
What does NXDOMAIN mean?
That the name you looked up does not exist in DNS: the domain is not registered, has expired or was mistyped.
Which DNS servers does this tool ask?
No middleman: Netlupa runs its own resolver, which starts from the root servers and asks each domain's official DNS servers directly.
Can I do a reverse DNS lookup of an IP?
Yes: look the IP up with the API (/api/dns/ptr/8.8.8.8) or use the WHOIS tool to find out who it belongs to.
Why do I see a different value than in my DNS panel?
Because resolvers still have the previous value cached. Wait for the time shown in the TTL, or check that you edited the zone at the provider listed in the NS records: if the domain uses other DNS servers, changes in your panel have no effect.
What is a record's TTL?
The time, in seconds, other servers may keep the answer before asking again. 3600 is one hour. A low TTL makes changes show up sooner, at the cost of more queries.