TXT Record Lookup
See every TXT record on a domain or subdomain and what each one does: SPF, DMARC, DKIM, MTA-STS, and verification tokens for Google, Microsoft, Meta, Apple and about 40 other services.
TXT Record Lookup
How this lookup works. When you press Get TXT records, your browser sends the question over encrypted DNS-over-HTTPS to Cloudflare's public resolver (1.1.1.1), or to Google Public DNS (8.8.8.8) if you choose it below. The request goes straight from your device to them. It doesn't pass through ToolFeather: we have no server in the path, so we never see or store the names you look up. Requests are sent without cookies or a referrer. Each resolver has its own privacy policy: Cloudflare · Google.
Results appear here.
Queries your browser sent (0)
These are the exact requests, each one a link. Open one to see the raw JSON answer from the resolver.
Live lookup: your browser asks Cloudflare or Google DNS directly. Nothing passes through ToolFeather.
Scratchpad auto-saved
How it works — in four simple steps
No signup and nothing to install — it all runs in your browser.
Enter a name
A domain, or a full host like _dmarc.example.com.
Look it up
Or use a jump button for the usual email records.
Read the labels
Each record is identified and its size shown.
Tidy up
Remove duplicates and tokens you no longer need.
Only one TXT record may start with v=spf1. If you see two, merge them today, because SPF is failing for every message.
Features
Labels every record
Recognises SPF, DMARC, DKIM, MTA-STS, TLS-RPT and BIMI, plus about 40 verification-token formats.
String splits shown
Byte length of each 255-byte string, so badly split long records are easy to spot.
One-click locations
Jump to _dmarc, _mta-sts, _smtp._tls, default._bimi or a DKIM selector.
Duplicate checks
Warns about multiple SPF or DMARC records, which break authentication.
Copy any record
Each value has its own copy button.
About the TXT Record Lookup
TXT records hold free-form text, and they've become the place to publish email-authentication policies and prove domain ownership. SPF lives in a TXT record on the domain itself, DMARC at _dmarc., DKIM keys at selector._domainkey., and MTA-STS and TLS reporting at _mta-sts. and _smtp._tls.. Services such as Google Search Console, Microsoft 365 and Meta ask you to add a token to confirm you control the domain.
Inside DNS a TXT record is one or more character strings of up to 255 bytes each. Long values such as 2048-bit DKIM keys are split into several strings, which receivers join back together. This tool joins them for you and shows how each record was split, so you can tell whether your DNS host broke a value in an odd place.
Use the jump buttons to check the usual email locations in one click. The checks catch the expensive mistakes: two SPF records (SPF then fails everywhere), two DMARC records (DMARC is ignored), and a pile of old verification tokens that bloats every TXT answer.