TXT Record Lookup
Check TXT records for SPF, DKIM, DMARC, and domain verification from multiple locations.
About DNS Lookup
Complete DNS lookup tool that queries A, AAAA, MX, TXT, NS, CNAME, and other DNS record types from multiple global DNS servers.
Key Features
Multiple record types (A, AAAA, MX, TXT, NS, CNAME, SOA, CAA)
Multi-region DNS resolution
Propagation checking
TTL information
Reverse DNS lookup
TXT records serve as the Swiss Army knife of DNS, storing text-based data used for domain verification, email authentication, and security policies. They're essential for proving domain ownership to services like Google and Microsoft, and for email security protocols like SPF, DKIM, and DMARC.
Our multi-region TXT lookup tool helps you verify that your verification codes, SPF records, and other TXT configurations are properly propagated worldwide. This is crucial when setting up new services that require domain verification, configuring email authentication to prevent spoofing, or troubleshooting deliverability issues.
For complete email deliverability, combine TXT checks with MX record verification to ensure mail routing is correct, and reverse DNS lookup to verify your mail server's PTR record matches your sending domain.
**Methodology:** TXT record queries from 6 regions showing all text records including SPF, DKIM selectors, and DMARC policies.
Common DNS Errors & How to Fix Them
4 relevant issuesThe domain name does not exist in DNS. This means no DNS records of any type were found for this domain.
1) Verify spelling: dig example.com ANY. 2) Check registration: whois example.com (look for "Status: active"). 3) Verify NS at registrar matches your DNS provider. 4) If recently registered, wait 24-48 hours and test with: dig @8.8.8.8 example.com
The domain exists but has no records of the requested type. For example, querying MX records for a domain that only has A records.
1) Confirm record type exists: dig example.com MX +short. 2) Check all records: dig example.com ANY. 3) Query authoritative NS: dig @ns1.yourprovider.com example.com MX. 4) For MX, verify mail is configured in your DNS panel. For AAAA, IPv6 may not be configured (this is often intentional).
The DNS server did not respond within the expected time. This can indicate network issues, overloaded nameservers, or firewall blocking.
1) Test NS connectivity: dig @ns1.example.com example.com +time=10. 2) Check if NS responds: nslookup example.com ns1.yourprovider.com. 3) Verify UDP port 53: nc -vzu ns1.example.com 53. 4) Test from different resolver: dig @1.1.1.1 example.com. If public resolvers work, your NS may be overloaded or blocking.
Different DNS resolvers are returning different values for the same query. This typically occurs during DNS propagation after a recent change.
1) Compare resolvers: dig @8.8.8.8 example.com vs dig @1.1.1.1 example.com vs dig @9.9.9.9 example.com. 2) Check TTL: dig example.com +ttlunits (lower = faster propagation). 3) Check authoritative: dig @ns1.yourprovider.com example.com (should show new value). 4) Wait for old TTL to expire, or pre-lower TTL before changes.
Frequently Asked Questions
4 relevant questionsTXT records store text data in DNS and are used for domain verification (Google, Microsoft, SSL certificates), email authentication (SPF, DKIM, DMARC), and security policies. When you add a Google Search Console verification or configure SPF for email, you're adding TXT records. They're also used for DKIM signatures, DMARC policies, and various third-party service verifications.
SPF (Sender Policy Framework) is a TXT record that specifies which mail servers are authorized to send email on behalf of your domain. It helps prevent email spoofing and improves deliverability. An SPF record looks like "v=spf1 include:_spf.google.com ~all". Without SPF, your emails are more likely to be marked as spam, and attackers can more easily spoof your domain in phishing attacks.
DMARC (Domain-based Message Authentication, Reporting & Conformance) is a TXT record that tells receiving mail servers what to do when SPF or DKIM checks fail. It builds on SPF and DKIM to provide a complete email authentication policy. DMARC can instruct servers to reject, quarantine, or allow suspicious emails, and sends you reports about authentication failures—helping you identify and stop email spoofing attempts.
DNS propagation is the time it takes for DNS changes to spread across all DNS servers worldwide. When you update a DNS record, the change must propagate from your authoritative nameserver to DNS resolvers globally. Propagation typically takes 1-24 hours, though it can take up to 48 hours in rare cases. The actual time depends on the TTL (Time To Live) value of your records—lower TTLs mean faster propagation but more DNS queries to your servers.
Related Tools
View All Tools →Related Tools
Global Infrastructure Verification
Verify SSL certificates, DNS records, and connectivity from 6+ regions worldwide. Get automated monitoring, expiry alerts, and full API access.