TXT record lookup
Read every TXT record published on a name — SPF, DKIM, DMARC, site-verification strings — exactly as a resolver returns them.
Related tools: DNS lookup · A record lookup · CNAME lookup · NS lookup · CAA record lookup · Reverse DNS lookup · DNS propagation checker · All free tools
The text records a name publishes
TXT records hold free-form text, and over the years they have become the place email authentication and ownership verification live: SPF at the domain, DMARC at _dmarc, DKIM keys at selector._domainkey, and a long tail of google-site-verification and similar strings. This tool asks Cloudflare's 1.1.1.1 resolver for every TXT record on a name and shows each one whole, joining the 255-byte strings a long record is split into.
TXT records are edited often and rarely watched. Upcheck's DNS check focuses on the records that take a site down: A, AAAA, NS, and MX. For those, it re-resolves every website every 6 hours and alerts your team on a change.
Three steps, no signup
- 01
Enter the exact name
example.com for SPF, _dmarc.example.com for DMARC, selector._domainkey.example.com for a DKIM key. TXT records live at specific names.
- 02
We ask a public resolver
The TXT query goes over DNS-over-HTTPS to Cloudflare's 1.1.1.1 from Cloudflare's network.
- 03
Every record comes back intact
Long records are shown as one string, the way receivers read them, with the TTL alongside.
Frequently asked questions
What is a TXT record used for?
Anything that needs a string of text published under a name. In practice that means email authentication (SPF, DKIM, DMARC), proving you control a domain to a service (google-site-verification, MS=, and the like), and occasional configuration hints. A domain can have many TXT records at the same name, and receivers pick out the one they care about by its prefix, such as v=spf1.
Why is my TXT record split into pieces?
A single TXT string is limited to 255 bytes, so longer records, typically DKIM public keys, are published as several strings inside one record. Receivers join them back together before use. Some lookup tools show the pieces with quotes between them, which makes a valid record look broken; this tool shows the joined result, which is what actually gets evaluated.
I added a TXT record but the lookup doesn't show it.
Three things to check. Whether the TTL of the previous answer has run out: a resolver that already looked up the name keeps the old answer until then. Whether you added the record at the right name: DMARC lives at _dmarc.example.com, not at example.com, and DKIM at the selector name. And whether the zone you edited is the one the domain's nameservers actually serve; use the NS lookup to confirm.
Can I check SPF or DMARC with this?
You can read the raw records here, and for the domain itself that is often enough. To have them parsed and validated, with includes followed, lookups counted, and mistakes flagged, use the SPF checker and the DMARC checker. They fetch the same TXT records and then interpret them.
Is this TXT lookup free?
Yes. No account, no limit on lookups by hand; scripted use is rate limited. Upcheck's paid monitoring watches the DNS records your website depends on every 6 hours and alerts your team when one changes.
One lookup reads the record. Monitoring watches the zone.
Add your websites to Upcheck and get alerted by email, Slack, Discord, Teams, or webhook when a record that matters changes.