What the TXT Record Lookup does
TXT records store arbitrary text in a domain's DNS. In practice they carry critical email-authentication and verification data: SPF policies that list who may send mail for the domain, DKIM public keys that verify message signatures, DMARC policies that tell receivers how to handle failures, and one-off verification tokens from services like Google and Microsoft.
This tool retrieves every TXT record for a domain so you can audit its email security posture and confirm verification strings are in place.
How to read the results
- A record starting with v=spf1 is an SPF policy defining which servers may send mail for the domain.
- v=DMARC1 (usually on _dmarc.domain) sets the DMARC policy — none, quarantine or reject.
- Long base64-looking strings on selector subdomains are DKIM public keys.
- Short tokens like google-site-verification=… prove domain ownership to a third-party service.
Worked example
Input: github.com
v=spf1 ip4:192.30.252.0/22 include:_spf.google.com ~all google-site-verification=xxxxxxxxxxxxxxxxxxxxxxxx
The SPF record authorises GitHub's own ranges plus Google's mail servers to send email as the domain, and ends with ~all (soft-fail) for everything else.
Common use cases
- Audit or debug SPF, DKIM and DMARC email-authentication setup.
- Confirm a domain-ownership verification token is published correctly.
- Investigate why your outbound mail is failing SPF or DMARC.
- Review which third-party services a domain has been verified with.