TXT Record Checker - Free DNS TXT Record Lookup
Instantly look up and analyse all TXT DNS records for any domain - including SPF, DMARC, DKIM, Google and Microsoft verification records. Free, real-time, no signup required.
Filter by type
Fetching TXT records...
Supports Google · Cloudflare · OpenDNS resolvers · real-time results · no signup required
How to Use the TXT Record Checker
1
Enter a domain name (e.g.
example.com) in the input field - the tool strips https:// automatically2
Select a DNS resolver - Google, Cloudflare, or OpenDNS - to query records from different sources
3
Click Check Records or press Enter to retrieve all TXT records for the domain instantly
4
Use the filter pills - All, SPF, DMARC, DKIM, Other - to isolate specific record types, then copy any record with the Copy button
Understanding Your TXT Record Lookup Results
SPF / DMARC / DKIM status chips
🟢
Found - the record is published and detected in DNS
🔴
Not Found - the record is missing; this is a common cause of emails landing in spam
Record type tags
SPF
Specifies which servers are allowed to send email for your domain.
DMARC
Sets the policy for what happens when an email fails authentication.
DKIM
A digital signature that proves your emails haven't been tampered with.
Google Verification
Proves domain ownership to Google Workspace or Search Console.
Microsoft Verification
Proves domain ownership to Microsoft 365 or Azure AD.
TXT
Any other TXT record - tokens for SaaS tools or custom strings.
TTL (e.g. 3600s)
How long DNS resolvers cache the record. Lower = changes spread faster. Higher = changes take longer to apply globally.
What Is a DNS TXT Record?
A DNS TXT (text) record is a type of DNS record that stores arbitrary text data associated with a domain. Originally designed for human-readable notes, TXT records are now widely used for machine-readable verification and authentication purposes - most importantly for email security.
Unlike A or MX records, which route traffic and email, TXT records don't affect how DNS resolves your domain. Instead, they act as a public notice board: mail servers, security tools, and third-party services read them to verify identity, authorise actions, or enforce policies.
What TXT Records Are Used For
Email authentication
SPF, DKIM, and DMARC all use TXT records to publish policies that receiving mail servers check before delivering email.
Domain verification
Google, Microsoft, and other services ask you to add a TXT record to prove you own a domain before granting access.
Security policies
BIMI, MTA-STS, and TLS-RPT records are published as TXT records to communicate security configurations.
Third-party integrations
Many SaaS tools use TXT records to verify domain ownership before enabling custom sending domains or SSO.
Frequently Asked Questions
A TXT record lookup queries the DNS for all TXT-type records published under a domain name. It returns the raw record values along with TTL data. This tool performs the lookup in real time using your choice of DNS resolver - Google, Cloudflare, or OpenDNS - and automatically classifies each record as SPF, DMARC, DKIM, or a verification record.
Yes - a domain can have as many TXT records as needed. In practice, most domains have several: one SPF record, one DMARC record, one or more DKIM records (one per selector/sending service), plus domain verification records for Google, Microsoft, or other platforms. Note that a domain should only ever have one SPF record - multiple SPF records cause SPF to fail.
It means the record is not published in DNS for this domain. Missing SPF means receiving servers can't verify your authorised senders - increasing spam likelihood. Missing DKIM means emails aren't signed, reducing trust. Missing DMARC means you have no policy controlling what happens when SPF or DKIM fails, and you're not receiving any abuse reports. All three should be present for good deliverability.
DNS record types serve different purposes: A records map a domain to an IP address, MX records define mail servers, CNAME records create aliases, and NS records define nameservers. TXT records store free-form text and are used for verification and policy publishing - they don't affect how your domain resolves or routes traffic, but they're read by mail servers and third-party services.
TXT record changes propagate based on the TTL (Time to Live) value of the record. A TTL of 3600 means resolvers cache the record for up to 1 hour before fetching a fresh copy. Changes typically take between a few minutes and 48 hours to propagate globally, depending on the TTL and downstream resolver cache times. During migrations, temporarily lowering your TTL to 300 seconds speeds up propagation.
If SPF is missing from results, the most common causes are: the record hasn't been added yet, it was added to the wrong subdomain (should be on the root domain
@), DNS changes haven't propagated yet (wait up to 48 hours), or the record has a syntax error that prevents it being recognised. Try switching to a different DNS resolver in the dropdown - Google and Cloudflare sometimes reflect changes at different speeds.
