Start typing to search 227 tools.
TXT Record Lookup
TXT Record Lookup retrieves published DNS text records and presents SPF, verification, policy, and other TXT values in a readable report.
What TXT Record Lookup does
TXT Record Lookup retrieves the text records currently published for a domain or hostname. TXT records are used for many unrelated purposes, including SPF email policy, domain ownership verification, service configuration, security policies, and vendor-specific tokens.
Because a domain can publish several TXT values at once, Trexmi presents them as readable record entries with TTL context instead of forcing you to interpret a single raw DNS blob. The raw response remains available when you need the exact structured data.
How to use
Enter a domain such as google.com without https:// or a page path, then select Look Up TXT Records. Review every returned value individually. A domain can legitimately contain multiple TXT records, so do not assume the first record is the one you need.
If you are verifying a service, compare the exact token or policy string with the value provided by that service. DNS text is sensitive to missing characters, quotes, spaces, prefixes, and copied punctuation.
Why use TXT Record Lookup?
Focused controls, predictable output, and a workflow designed around this exact transformation.
Read every published TXT value clearly
See multiple TXT records as separate entries instead of searching through an unformatted DNS response.
Review SPF and verification records
Quickly identify common email-policy strings, ownership tokens, and service-specific verification values.
Use TTL when checking recent changes
Understand why an updated TXT value may not appear immediately through every cached recursive resolver.
Questions about TXT Record Lookup
Practical details about input, output, privacy, limits, and the best way to use this tool.
01 What does TXT Record Lookup show?
It returns the TXT records published for a domain or hostname, including SPF policies, verification tokens, and other text values.
02 Can a domain have several TXT records?
Yes. Multiple unrelated TXT records are common. SPF is one specific use of TXT and should normally have only one applicable SPF policy per domain.
03 Why is my new TXT verification record missing?
Check the authoritative DNS zone, host/name field, exact token, and TTL. Cached recursive resolvers may temporarily return an older answer.
TXT Record Lookup for readable DNS text checks
DNS TXT records were originally designed to associate arbitrary text with a domain name, but today they are widely used by email systems, cloud platforms, analytics providers, certificate workflows, collaboration services, and website-verification tools. A single domain can publish many independent TXT records without those records being related to one another.
Common types of TXT records
An SPF policy normally begins with v=spf1 and describes which systems are authorized to send mail for a domain. Verification records often contain a provider name followed by a token. Other TXT records can publish policy, ownership, configuration, or security metadata. TXT Record Lookup does not guess the business meaning of an unknown value; it shows the live DNS data so you can compare it with the documentation for the relevant service.
DNS TXT record syntax is defined in RFC 1035. Sender Policy Framework is specified in RFC 7208.
7 powerful TXT checks before you finish
Confirm the domain name, locate the expected value, compare the complete token character for character, identify duplicate or obsolete verification entries, check SPF records for unintended duplication, review the TTL, and allow for resolver caching after recent edits. These checks prevent many frustrating verification and email-configuration failures.
TXT records and SPF
SPF is stored in a TXT record. Publishing more than one SPF policy for the same domain can cause SPF evaluation problems because receivers expect a single applicable SPF record. A domain can still have many other TXT records alongside SPF. When using TXT Record Lookup, identify the entry beginning with v=spf1 and review it separately from unrelated verification tokens.
Why TXT values can look split or quoted
DNS libraries and command-line tools can represent long TXT data as multiple quoted character strings. These pieces belong to the same DNS record and are logically concatenated by DNS consumers. A readable tool should preserve the value without misleading the user into thinking each quoted segment is necessarily a separate record.
TXT Lookup after adding a verification token
If a provider says a verification record is missing immediately after you add it, first confirm that you edited the authoritative DNS zone and used the correct host/name field. Then check the live record and its TTL. Recursive caches can continue serving an older answer until the cached lifetime expires.
Related Trexmi DNS tools
Use DNS Lookup for a complete record overview, CNAME Lookup for aliases, MX Lookup for mail exchangers, and NS Lookup to verify authoritative nameservers. For broader DNS standards information, see the IANA root-zone resources.
TXT Record Lookup summary
TXT Record Lookup turns a potentially confusing set of DNS text values into a clear report. You can review the record count, each published value, TTL context, and raw DNS output, making the tool useful for email setup, domain verification, SaaS onboarding, security configuration, and routine DNS troubleshooting.