TXT Record Lookup

TXT is text, not executable content

Enter the exact owner name supplied by your service. A verification token at a subdomain will not appear if you only query the domain apex. Owner-name mode accepts labels such as _dmarc and _domainkey.

A single TXT resource record may contain several quoted character strings. These fragments form one logical value with no inserted spaces. Separate resource records remain separate, even when both appear in the same response.

example.com.  300 IN TXT "v=spf1 " "include:mail.example -all"
Logical value: v=spf1 include:mail.example -all

DOCUMENTATION EXAMPLE — not a live DNS response

Keep the original and the logical value

The results show joined text and retain the original resolver representation. Copy value preserves the full logical value; Raw JSON preserves the response’s record boundaries and quoting.

Long verification strings wrap visually instead of being truncated. Wrapping on screen does not insert newlines into the value copied from a record. DNS text is displayed as text, never executed as HTML or JavaScript.

Finding email policies

SPF policies normally live at the sender domain. DMARC uses an _dmarc owner name and has additional discovery rules. DKIM queries require the selector provided by the mail system; this tool cannot enumerate every selector.

Use the dedicated SPF or DMARC checker when you need configuration analysis. Merely seeing a TXT record is not evidence that an email message passed authentication.

Why a token is missing

Confirm the owner name, selected resolver and requested type. DNS providers sometimes append the zone name automatically; entering a full name in a relative-name field can publish a token at the wrong owner.

NOERROR without the expected text is not the same as NXDOMAIN. A cached older response can also explain a temporary difference between two resolvers.