TXT Record Lookup

Query all publicly visible TXT records for a domain through Google DNS-over-HTTPS and review each returned value with its TTL. TXT records commonly carry SPF policies, domain-ownership verification tokens, and service-specific configuration, but the tool displays the published strings without deciding whether every policy is valid. Use the exact hostname that owns the record, such as example.com or a provider-specified subdomain. Results are read-only, resolver-cached public DNS data and may temporarily differ from an authoritative nameserver after a change.

How to Use the TXT Record Lookup

Look up the TXT values publicly visible for an exact domain or subdomain and review each value with its DNS cache lifetime.

  1. Enter the exact domain or subdomain that should own the TXT record.
  2. Select Run to query TXT records through Google DNS-over-HTTPS.
  3. Review every returned Value; unrelated verification and policy records may appear together.
  4. Use TTL to estimate how long recursive caches may retain the answer.
  5. For protocol validation, take the relevant value to a dedicated checker such as the SPF, DKIM, or DMARC tool.

Interpreting TXT results

TXT is a general-purpose record type. A returned string has meaning only to the service or protocol that defines its prefix and format.

The page displays public resolver output; it does not certify that a verification token is accepted or that an email policy is correctly designed.

Worked example

If a service asks for a TXT record at _verify.example.com, enter that full hostname rather than example.com. Match the returned token exactly, and consider the TTL before assuming a recent edit has reached cached resolvers.

Common mistakes

  • Looking up the apex domain when the provider required a specific subdomain.
  • Assuming all TXT records are SPF records or that multiple general TXT answers are inherently invalid.
  • Expecting a newly published value to appear before the previous TTL has expired.

Limitations and privacy

The lookup uses Google's public recursive DNS cache and cannot see private or split-horizon zones. Recent answers may differ from authoritative DNS while caches expire.

The queried hostname is sent from your browser to Google DNS-over-HTTPS. Public TXT values are not secrets, but confidential internal hostnames should not be submitted.

FAQ

What does the TXT Record Lookup return?

It queries the entered hostname for DNS TXT records and lists every answer returned by Google DNS-over-HTTPS, including each record's TTL and text value.

Can this find SPF records?

Yes. SPF is normally published as a TXT value beginning with v=spf1. This page shows that string alongside other TXT records but does not perform the dedicated SPF syntax checks.

Why are several TXT records shown?

A hostname can publish multiple independent values for email policy, site verification, and other services. Multiple general TXT records are valid; the rules for duplicates depend on the protocol using them.

Why is a long TXT value split or quoted?

DNS can store a TXT record as multiple character strings. Resolver JSON may expose quoting or segments, and the page removes only the outer quote characters when displaying the returned data.

What does TTL mean?

TTL is the number of seconds a recursive resolver may cache that answer. Recently changed records can remain stale at some resolvers until the previous TTL expires.

Why is a verification record missing?

Check the exact hostname required by the service, allow for DNS caching, and confirm the record was published in the authoritative zone. A token placed at the apex will not appear under a different subdomain.

Does this tool change or verify ownership of a domain?

No. It is a read-only public DNS lookup. Add or edit records with your DNS host, then complete verification with the service that issued the token.

Which DNS resolver is used?

The implementation queries Google DNS-over-HTTPS from your browser. Results reflect Google's public recursive cache at lookup time, not a direct authoritative nameserver query.

Are private DNS records available?

No. Public DNS-over-HTTPS cannot see records that exist only in a private, split-horizon, VPN, or corporate DNS zone.

Is it safe to look up TXT records?

TXT answers in public DNS are already publicly queryable, and the lookup is read-only. The hostname you enter is sent to Google DNS, so do not submit confidential internal names.