Skip to main content
KX Toolkit

TXT Record Lookup

TXT records hold arbitrary text strings attached to a domain. Originally meant for human-readable notes, they now carry critical machine-readable data such as SPF policies, DKIM keys, DMARC rules, domain ownership verifications for Google, Microsoft, Facebook, and many other serv

Domain Tools

TXT records hold arbitrary text strings attached to a domain. Originally meant for human-readable notes, they now carry critical machine-readable data such as SPF policies, DKIM keys, DMARC rules, domain ownership verifications for Google, Microsoft, Facebook, and many other serv

This free TXT Record Lookup from KX Toolkit is part of our all-in-one online toolkit. It runs entirely in your browser, so your data never leaves your device for client-side operations. 100% free, forever - no paywall, no credit card, no trial.

How to use the TXT Record Lookup

  1. Enter the domain or IP address.
  2. Pick the record type if the tool supports filtering.
  3. Run the lookup - most checks return in under a second.
  4. Copy the records for your DNS migration or audit notes.

What you can do with the TXT Record Lookup

  • Audit DNS before a domain migration.
  • Verify SSL certificate expiry and chain.
  • Check domain age and history before buying.
  • Diagnose email-delivery issues (SPF, DKIM, DMARC).

Why use KX Toolkit's TXT Record Lookup

  • Browser-based: Works on Windows, macOS, Linux, iOS and Android - no install, no extension.
  • Privacy-first: Client-side tools never upload your data; server-side tools delete files right after processing.
  • Mobile-friendly: Full feature parity on phones and tablets - not a stripped-down view.
  • Fast: Optimised for instant feedback. No artificial waiting screens, no email-gated downloads.
  • One hub for everything: 300+ tools across SEO, text, image, PDF, code, color, calculators and more - skip switching between sites.

Tips for the best results

DNS changes propagate at different speeds across resolvers - run the same check from Google (8.8.8.8) and Cloudflare (1.1.1.1) before declaring a problem.

Related Domain Tools

If you find this tool useful, explore the full Domain Tools collection or browse our complete tool directory. KX Toolkit is built for marketers, developers, designers, students and anyone who needs a quick utility without signing up for yet another SaaS.

What are TXT records used for?
TXT records hold arbitrary text strings attached to a domain. Originally meant for human-readable notes, they now carry critical machine-readable data such as SPF policies, DKIM keys, DMARC rules, domain ownership verifications for Google, Microsoft, Facebook, and many other services, and miscellaneous configuration tokens. A typical production domain has between five and twenty TXT records covering different purposes. The lookup displays all of them so you can audit what is published.
How do I read SPF, DKIM, and DMARC inside TXT records?
SPF records start with v=spf1 and list the servers allowed to send mail for the domain. DMARC records live at the _dmarc subdomain and start with v=DMARC1. DKIM records sit at selector._domainkey.example.com and contain v=DKIM1 along with a public key. The TXT lookup shows all three, but the dedicated SPF, DKIM, and DMARC checkers provide deeper validation, error reporting, and policy parsing.
Why do I see verification strings from services I no longer use?
Many SaaS platforms ask you to add a TXT record like google-site-verification=abc123 to prove ownership. After verification, they almost never tell you to remove the record, so old strings accumulate over years. Cleaning them up reduces clutter, shortens DNS responses, and prevents stale tokens from being used in spoofing attacks. Use the lookup periodically to identify entries you can safely delete.
Is there a limit on how many TXT records a domain can have?
There is no hard limit on the number of TXT records, but each individual string is capped at 255 characters by the DNS protocol. Longer values must be split into multiple quoted segments that resolvers join together. The full UDP DNS response is also limited to 512 bytes unless EDNS0 is enabled, so very long TXT sets can force fallback to TCP. Keep records concise and remove unused ones.
Can sensitive data be hidden in TXT records?
No. TXT records are public, queryable by anyone, and indexed by passive DNS services. Never store API keys, secrets, or internal hostnames in TXT records, even temporarily. The most you should expose is verification tokens, public keys for DKIM, and policy strings for SPF or DMARC. Treat the contents of every TXT record as if they were posted on your homepage.
Why does my TXT change not show up immediately?
TXT records inherit the TTL of your DNS zone, often 3600 seconds or more. Resolvers continue serving the cached value until the TTL expires, even after the authoritative servers have the new record. If you are racing against a verification deadline, lower the TTL on the record before making the change. The DNS Propagation Checker can confirm when the new value is visible across global resolvers.

No reviews yet

Be the first to share your experience with the TXT Record Lookup.