Free · live registry data · no login
TXT Record Lookup
All TXT records, with SPF and verification strings highlighted.
How it works
See every TXT record on a domain, with SPF and verifications named
TXT records carry your SPF policy, Google, Microsoft and Meta ownership proofs, and many API verification strings. Enter a domain and we fetch all TXT records live, join multi-part strings back together, identify what each one is for and check the two that break email: duplicate SPF records and SPF lookups over the ten-lookup limit. We also look at _dmarc for the DMARC policy so you get the complete picture.
Results appear here after you click Look up TXT records.
How this works
- 1
Fetch and reassemble
TXT answers arrive as quoted chunks; we join them back into the original strings.
- 2
Label each record
Over thirty known prefixes identify SPF, DMARC, DKIM and vendor verification strings.
- 3
Check SPF and DMARC
Duplicate SPF, lookup count, the 'all' qualifier and the DMARC policy are tested against the standards.
Frequently asked questions
- What are TXT records used for?
- TXT records hold arbitrary text that other systems read. The common uses are SPF (which servers may send your email), DMARC and DKIM for email authentication, and one-time ownership proofs such as google-site-verification when you connect a domain to a service.
- Why do I have two SPF records and why is that bad?
- Usually one came with your website host and another with your email provider. The SPF standard requires exactly one v=spf1 record; with two, receivers return permerror and your mail fails authentication. Merge the include terms into a single record ending in ~all.
- Can I delete old verification TXT records?
- Often yes, but some services re-verify periodically (Google Workspace, Microsoft 365, Meta) and will lose access to the domain if the record disappears. Keep records for services you still use and remove the rest.
- How long should TXT records be?
- A single string is limited to 255 characters, but a record can contain several strings which resolvers join. Your DNS host normally splits long values for you. Keep SPF under 255 characters where you can for compatibility.
- How long until a new TXT record is visible?
- Usually within minutes once the record is saved, though resolvers that cached a 'no record' answer keep that for the negative-cache TTL (often 1 to 24 hours). Verification services typically retry automatically.
Every MailShrine domain includes WHOIS privacy, transfer lock, Anycast DNS with DNSSEC and two business mailboxes.