What is a TXT record lookup?

It queries DNS for TXT records and shows the text strings published at a hostname, with TTL metadata.

What are TXT records used for?

Email authentication (SPF, DKIM, DMARC), domain verification, site ownership proofs, and various security policies.

SPF is published as a TXT record at the domain apex (and sometimes subdomains) starting with v=spf1.

DKIM public keys appear in TXT records at selector._domainkey.example.com. The selector name varies by provider.

DMARC policies are TXT records at _dmarc.example.com beginning with v=DMARC1.

Yes. Resolvers may return several strings; some platforms merge them. Review every value returned.

Typos, wrong hostname, quotes, or stale cache cause failures. Confirm exact token, name, and TTL expiry.

DNS limits apply per string; long DKIM keys may split across multiple strings that clients concatenate.

TXT is not used for HTTP routing. It affects mail authentication and third-party verification workflows.

This tool shows raw TXT strings. The dedicated checker parses and validates common email auth formats.

DMARC lives at _dmarc.yourdomain — enter that full name or use the checker tool for guided queries.

TTL controls cache lifetime. After edits, wait for TTL or flush local resolver cache before retesting.

Yes. IP Checker Online offers TXT lookups without signup.

DKIM public keys and verification tokens are meant to be public in DNS. Never publish private secrets in TXT.

During email migrations, after adding SaaS integrations, when deliverability drops, and before security reviews.

DNS Tools

Read TXT records for email authentication and domain verification.