The TXT Lookup tool allows you to query the Domain Name System and instantly view all text records associated with any domain name. It retrieves valuable policy, security, and verification strings directly from authoritative name servers without caching delays.
What is it
A TXT (Text) record is a type of resource record in the Domain Name System that lets domain administrators associate arbitrary text strings with a domain. Originally intended for human-readable notes, TXT records now serve as the foundational building block for modern email authentication protocols like SPF and DMARC, as well as domain ownership verification for web services and SSL certificates. Unlike other DNS records that route traffic or point to IP addresses, TXT records convey metadata and policy instructions to external applications, mail servers, and security auditors.
Why it matters
Properly configured TXT records are essential for email deliverability, domain security, and service integrations. Without accurate SPF and DMARC text records, receiving mail servers will often reject your outbound messages or send them straight to the spam folder. Furthermore, cloud providers, certificate authorities, and web platforms rely on TXT records to verify that you actually own the domain before granting access to critical infrastructure. Regularly auditing your text records ensures that deprecated security policies are removed and unauthorized access tokens are purged.
How to use this tool
- Locate the input field on the TXT Lookup page.
- Type or paste the target domain name into the box, ensuring you omit any leading protocols like https://.
- Click the Check button to initiate a direct query against the domain's authoritative name servers.
- Review the returned list of text records displayed on your screen.
How to read the results
When you query a domain such as example.com, the tool returns a list of all active text records found in the zone file. Each record typically contains a host or name (which may be blank or @ for the root domain, or a specific subdomain), a Time To Live (TTL) value, and the string value itself enclosed in quotation marks.
For example, you might see a record with the value v=spf1 include:_spf.example.com ~all. This indicates the Sender Policy Framework configuration for the domain, authorizing specific mail servers to send mail on its behalf. Another common result is a site verification string such as google-site-verification=rX9..., which proves to a third-party service that you control the DNS zone. You may also see DMARC records beginning with _dmarc.example.com containing values like v=DMARC1; p=reject;, which dictate how mail servers should handle messages that fail authentication checks.
Common problems and how to fix them
Missing SPF Record
If your email is marked as spam, you likely lack an SPF record. Check your root domain for a text record starting with v=spf1. If it is missing, create a new TXT record at your DNS host with the correct include statements for your email provider.
Type: TXT
Name: @
Value: v=spf1 include:mail.example.com -all
Multiple SPF Records
Having more than one SPF record on a single domain causes validation to fail completely. Merge all authorized IP addresses and include mechanisms into a single TXT record.
Syntax Errors in Policy Strings
Typoes in DMARC or SPF parameters prevent receiving servers from parsing your security policies. Double-check semicolons, spaces, and mechanisms against current protocol specifications.
Best practices
Keep your DNS zone clean by periodically removing obsolete verification TXT records left over from previous web hosts or temporary marketing campaigns. Consolidate your SPF includes to stay well below the ten-lookup limit imposed by receiving mail servers, which prevents permanent DNS lookup failures. Always test your email-related text records after making changes to ensure your messaging infrastructure remains secure and fully operational.