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.
JustChecker tracks your DNS records continuously and alerts you the moment something changes.
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.