A TXT record holds arbitrary text. In practice it carries email authentication and ownership-verification strings that other systems read.
TXT records are the Swiss Army knife of DNS. They store SPF policies that list who may send mail for your domain, DKIM public keys used to sign outgoing messages, DMARC policies that tell receivers what to do with failing mail, and the verification tokens that services like Google, Microsoft, and countless SaaS tools ask you to add to prove you control the domain. Because the content is free-form text, a single stray character or an unclosed quote can silently break authentication.
When you add or rotate one of these strings, receiving systems only see the update once their cached TXT lookup expires, so a verification can fail for minutes even though the record looks correct in your dashboard. This checker fetches every TXT record for your domain from many locations at once, so you can confirm the exact strings are present and identical worldwide before you click 'verify' or enforce a stricter DMARC policy. If locations disagree, the change is still propagating or you have conflicting records that need cleaning up.
Frequently asked questions
- Can I have more than one TXT record?
- Yes, a name can hold many TXT records. Keep only one SPF record, though, or mail authentication breaks.
- Why did my domain verification fail right after adding the TXT?
- The verifying service likely cached an empty answer. Wait for the TTL and retry.