TXT Lookup - SPF, DKIM & Domain Verification Records

A TXT lookup queries DNS TXT records containing SPF policies, DKIM keys, domain verification tokens, and other text-based data. Use robtex.com to inspect email authentication records and troubleshoot deliverability.

What TXT Records Contain

TXT records store arbitrary text data in DNS. Common uses:

SPF (Sender Policy Framework) - Lists authorized mail sending IPs. Receiving servers check SPF to detect spoofing.

DKIM (DomainKeys Identified Mail) - Public keys for verifying email signatures. Stored as selector._domainkey.example.com.

DMARC - Policy telling receivers how to handle SPF/DKIM failures. Stored at _dmarc.example.com.

Domain verification - Tokens proving domain ownership for Google, Microsoft, and other services.

Custom data - Any text the domain owner chooses to publish.

CAA records - Certificate Authority Authorization policies specifying which CAs can issue certificates.

Email Authentication Debugging

Email deliverability depends on proper authentication records. When messages land in spam or get rejected, TXT lookup reveals configuration issues:

SPF problems - Missing authorized IPs, too many DNS lookups (10 maximum), syntax errors.

DKIM issues - Missing or malformed public keys, selector mismatches between signing and DNS.

DMARC failures - Overly strict policies before SPF/DKIM are fully deployed, missing aggregate report addresses.

Querying TXT Records

Enter any domain to retrieve its TXT records. For DKIM keys, query the selector subdomain (e.g., google._domainkey.example.com).

Results show all TXT records at that name. Domains commonly have multiple TXT records - SPF, DKIM, and verification tokens coexist at different names within the zone.

TXT records have size limits. Long records may be split into multiple strings that resolvers concatenate. Lookup shows the complete assembled value.

→ Look up TXT records on robtex.com

FAQ

Why do I have multiple TXT records?
Different purposes require different records. SPF goes on the bare domain, DKIM on selector subdomains, verification tokens wherever the service specifies.
What does "v=spf1" mean?
It identifies an SPF record. Everything after declares authorized senders: "include:" for other domains, "ip4:" for specific IPs, "-all" to reject unauthorized sources.
How do I find my DKIM selector?
Check your email provider's documentation or examine the DKIM-Signature header in emails you've sent. The "s=" field contains the selector.
Can TXT records break email?
Malformed SPF or strict DMARC policies can cause delivery failures. Test changes in monitoring mode before enforcing.
What about BIMI records?
Brand Indicators for Message Identification (BIMI) are TXT records at _bimi.domain.com containing your brand logo URL. Requires DMARC enforcement to work.