DNS Tools

TXT Record Lookup

Look up a domain's TXT records - often used for SPF, domain verification, and more.

Enter a domain to look up its TXT records.

More DNS Tools

MX Record Lookup CNAME Lookup AAAA Record Lookup SOA Record Lookup A Record Lookup DNS Propagation Checker DNS Lookup CAA Record Lookup

JustChecker tracks your DNS records continuously and alerts you the moment something changes.

What Is a TXT Record?

TXT records store text for other services to read. They are used for email authentication (SPF, DKIM, DMARC), domain ownership verification for Google Search Console, Microsoft 365 and others, and various security settings.

When to Use It

After adding a verification code, to confirm it is published correctly.
To review a domain's SPF record.
When a service says it "cannot find the TXT record".

How to Use It

Enter the domain (or the exact subdomain, such as _dmarc.example.com).
Look for the value you added in the list.

Understanding the Result

A domain often has several TXT records - that is normal. However it should have only one record starting with v=spf1; two SPF records make SPF fail.

Limitations

Very long TXT values may be split into several quoted strings, which DNS joins together. For SPF and DMARC analysis, use the dedicated SPF Checker and DMARC Checker.

Frequently Asked Questions

A TXT record stores arbitrary text data attached to a domain - originally intended for human-readable notes, it has become the standard place to publish machine-readable verification and policy data, such as SPF, domain-ownership verification tokens, and DKIM public keys.

It's completely normal for a domain to accumulate TXT records over time from multiple unrelated services - Google Workspace verification, SPF, a marketing tool's domain-ownership check, and DKIM keys can all coexist as separate TXT entries.

Some DNS providers and resolvers impose a practical size limit on the total response for a single query - an unusually large number of TXT records on one hostname can occasionally cause truncation issues, though this is rare for typical usage.

A dedicated SPF record type existed briefly but was formally deprecated - TXT is now the standard, universally-supported way every major mail provider expects SPF policy to be published.

It likely belongs to a third-party service that verified domain ownership at some point (analytics, marketing, or productivity tools) - unrecognized TXT records are usually harmless leftovers rather than a security concern, but worth auditing periodically.

The record's value content can be case-sensitive depending on what it encodes (e.g. a verification token), but the hostname the TXT record is attached to follows the same case-insensitive rules as all other DNS names.

A single TXT record string is limited to 255 characters by the DNS specification, though multiple strings can be concatenated within one record - long SPF policies with many included domains sometimes need this.

You should only ever have one active SPF record - multiple "v=spf1" TXT records on the same hostname is invalid per the SPF specification and can cause mail servers to reject or fail to properly evaluate your policy.