DNS
TXT Record Lookup
List every TXT record on a domain
Tool features
4 checks
Text Record Analysis
Comprehensive lookup and analysis of DNS TXT records
Security Records
Identify SPF, DMARC, DKIM and other security-related records
Domain Verification
Detect verification records for Google, Microsoft, and other services
Fast Categorization
Automatically categorize and validate different types of TXT records
What is a TXT record & how it works
TXT records store arbitrary text on a domain's DNS. They aren't used for routing — instead they let a domain publish machine-readable policy and verification data that other systems read, such as SPF, DKIM and DMARC for email, or ownership-verification tokens.
This lookup returns every TXT record at the domain apex, joins multi-string records, and classifies each by purpose so you can see what a domain is publishing at a glance.
SPF
A
v=spf1 TXT record listing which servers may send mail for the domain.DKIM
A public key (in a selector subdomain) used to verify signed email.
Verification
Tokens that prove domain ownership to Google, Microsoft and other services.
How to use this tool
1
Enter a domain
Type the domain whose TXT records you want to list, e.g.
example.com.2
Pick a resolver (optional)
Open Advanced Settings to query a specific public resolver such as Google (8.8.8.8) or Cloudflare (1.1.1.1).
3
Run the lookup
Click Check TXT Records to query the authoritative nameservers for every TXT record at the apex.
4
Review the results
Read each record and its classified purpose (SPF/DKIM/DMARC/verification), plus the diagnostics and recommendations.
Related tools
4 tools
SPF Lookup
Check Sender Policy Framework (SPF) records for email authentication and mail server authorization
DMARC Lookup
Check DMARC policy records for email authentication, reporting, and policy enforcement
DKIM Lookup
Find DomainKeys Identified Mail (DKIM) records for email message signing and verification
MX Lookup
Find mail exchange (MX) records for email server configuration and priority
Frequently asked questions
5 Q&A
The most common uses are SPF (which senders are allowed), DKIM (email signing keys), DMARC policy, and verification tokens for services like Google Workspace and Microsoft 365.
Yes — a domain usually has several. However, it must have only one SPF record; multiple SPF records are invalid and break mail authentication.
DNS limits a single string to 255 characters, so long values (like DKIM keys) are published as several quoted strings that resolvers join back together.
DKIM records sit at
selector._domainkey.example.com and DMARC at _dmarc.example.com — subdomains, not the apex, so look them up there specifically.