June 7, 2026 · 12 min read

How to Check TXT Records for Your Domain

Learn how to easily check TXT records for any domain. Our guide covers online tools, command-line methods (dig & nslookup), and what TXT records are used for.

June 7, 2026 · 12 min read

DNS Domain Management Email Security

Are you trying to verify domain ownership, configure email authentication like SPF, DKIM, or DMARC, or perhaps set up a Google Site Verification? If so, you'll need to know how to check TXT records for your domain. TXT records are a fundamental part of your domain's DNS (Domain Name System) configuration, holding vital information that external services use to validate and interact with your domain.

This comprehensive guide will walk you through everything you need to know about checking TXT records. We'll cover the 'what' and 'why' of TXT records, then dive into practical methods, from user-friendly online checkers to powerful command-line tools like dig and nslookup. Whether you're a beginner or an experienced webmaster, this article will equip you with the knowledge to effectively check domain TXT records and understand the data they hold.

What Are TXT Records and Why Do You Need to Check Them?

DNS records are like an address book for the internet, translating human-readable domain names into IP addresses that computers understand. Among the various types of DNS records (like A, CNAME, MX), TXT records serve a unique purpose. They allow administrators to store arbitrary text strings in their DNS zone. While seemingly simple, these text strings are used for crucial verification and policy-setting functions.

Here are the most common reasons why you might need to check TXT records for a domain:

Email Authentication (SPF, DKIM, DMARC): This is arguably the most critical use case. Sender Policy Framework (SPF) records tell mail servers which mail servers are authorized to send email on behalf of your domain, helping to prevent spoofing. DomainKeys Identified Mail (DKIM) adds a digital signature to emails, allowing receivers to verify that the email hasn't been tampered with in transit and originated from the claimed domain. DMARC (Domain-based Message Authentication, Reporting & Conformance) builds on SPF and DKIM, providing a policy for how to handle emails that fail authentication and offering reporting capabilities.
Domain Verification: Many services, including Google Search Console, Google Workspace (formerly G Suite), Microsoft 365, and various other platforms, require you to prove ownership of your domain. This is often done by adding a specific TXT record provided by the service to your domain's DNS settings.
Site Verification: Similar to domain verification, services like Google Sites might ask you to add a TXT record to verify that you control the domain where your site is hosted.
Marketing and Analytics: Some marketing platforms or analytics tools might use TXT records for tracking or verification purposes.
Custom Policies and Information: Organizations can use TXT records to publish custom information or policies related to their domain that may be of interest to other systems or administrators.

Understanding how to check TXT records ensures that these critical configurations are in place and functioning correctly. If emails are landing in spam, or verification processes are failing, checking your TXT records is often the first step in troubleshooting.

How to Check TXT Records Online Using Free Tools

For many users, the quickest and easiest way to check TXT records is by using a free online DNS lookup tool. These tools query DNS servers on your behalf and present the information in a user-friendly format. You don't need to install any software or use the command line.

How it works:

Choose a Tool: Several reputable online DNS lookup tools are available. Some popular options include:
- What's My DNS? (whatsmydns.net)
- Google Admin Toolbox (toolbox.googleapps.com/apps/dig/)
- MXToolbox (mxtoolbox.com)
- DNSChecker.org
Enter Your Domain: In the tool's interface, you'll typically find a field to enter your domain name (e.g., example.com).
Select Record Type: There will be an option to select the type of DNS record you want to check. Choose 'TXT'.
Perform the Lookup: Click the 'Search' or 'Lookup' button.
Interpret the Results: The tool will display the TXT records associated with your domain. You'll see the record name (usually '@' for the root domain), the record type (TXT), and the actual text content of the record. Many tools also show results from various DNS servers worldwide, helping you see if the record has propagated globally.

Example with What's My DNS?:

Go to whatsmydns.net.
Select 'TXT' from the dropdown menu.
Enter your domain name (e.g., yourdomain.com).
Click 'Search'.

The results page will show a map and a list of locations, indicating where the TXT record was found. This is invaluable for confirming that your DNS changes have propagated across the internet.

Pros of Online Tools:

Ease of Use: No technical expertise required.
Speed: Get results almost instantly.
Accessibility: Available from any device with internet access.
Propagation Check: Many tools show results from multiple DNS servers globally.

Cons of Online Tools:

Limited Control: You can't perform more advanced queries.
Reliance on Third-Party: You're dependent on the tool's availability and accuracy.

These online checkers are excellent for a quick glance and verifying that your TXT records are visible to the public internet. If you need more advanced diagnostics or are troubleshooting complex DNS issues, command-line tools might be more suitable.

Using Command-Line Tools to Check TXT Records

For users who are comfortable with the command line or need more granular control, tools like dig (Domain Information Groper) and nslookup (Name Server Lookup) are powerful options. These are typically available on Linux, macOS, and Windows (though nslookup is built-in, dig might require installation on Windows).

1. Using `dig` to Check TXT Records

The dig command is a flexible tool for querying DNS name servers. It provides detailed output, making it a favorite among system administrators.

Basic Syntax:

dig <domain_name> TXT

Example:

Let's say you want to check the TXT records for example.com:

dig example.com TXT

Interpreting dig Output:

The output can look intimidating at first, but focus on the ANSWER SECTION. You'll see something like this:

; <<>> DiG 9.16.1-Ubuntu <<>> example.com TXT
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12345
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;example.com.                    IN      TXT

;; ANSWER SECTION:
example.com.           300     IN      TXT     "v=spf1 include:_spf.google.com ~all"

;; Query time: 45 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Mon Nov 27 10:00:00 UTC 2023
;; MSG SIZE  rcvd: 100

In the ANSWER SECTION, example.com. 300 IN TXT "v=spf1 include:_spf.google.com ~all" indicates:

example.com.: The domain.
300: The Time To Live (TTL) in seconds.
IN: The class (Internet).
TXT: The record type.
"v=spf1 include:_spf.google.com ~all": The actual TXT record content. Notice that long TXT records are often broken into quoted strings, which dig displays correctly.

Checking a Specific Name Server with dig:

Sometimes, you want to query a specific DNS server (e.g., your authoritative name server or Google's public DNS). You can specify the server IP address:

dig @8.8.8.8 example.com TXT

This command queries Google's DNS server (8.8.8.8) for the TXT records of example.com.

2. Using `nslookup` to Check TXT Records

nslookup is another command-line utility for querying the DNS. It's widely available, especially on Windows systems.

Basic Usage:

nslookup can be used in two modes: interactive and non-interactive.

Non-Interactive Mode:

nslookup -type=TXT <domain_name>

Example:

nslookup -type=TXT example.com

Interpreting nslookup Output:

The output will look something like this:

Server:         192.168.1.1
Address:        192.168.1.1#53

Non-authoritative answer:
Name:	example.com
Address: "v=spf1 include:_spf.google.com ~all"

Here, the Address line shows the TXT record content. Unlike dig, nslookup might not always show the quotes around the TXT record string in its output, but the content is what matters.

Interactive Mode:

Type nslookup and press Enter to enter interactive mode. Then, you can set the record type and query the domain:

> set type=TXT
> example.com

Checking a Specific Name Server with nslookup:

Similar to dig, you can specify a server:

nslookup -type=TXT example.com 8.8.8.8

Pros of Command-Line Tools:

Power & Flexibility: Offer advanced query options and detailed output.
Automation: Can be scripted for regular checks.
Troubleshooting: Essential for diagnosing DNS issues.
Direct Access: Directly query specific DNS servers.

Cons of Command-Line Tools:

Steeper Learning Curve: Requires some familiarity with the command line.
Installation (sometimes): dig might need to be installed on Windows.
Less Visual: Output is text-based, not graphical.

Whether you choose online tools or command-line utilities depends on your technical comfort level and the specific task at hand. Both methods effectively allow you to check TXT records for any domain.

Common TXT Record Values Explained

When you check TXT records, you'll encounter various strings. Understanding what these mean is crucial. The most common ones relate to email authentication:

SPF (Sender Policy Framework):
- Purpose: Prevents email spoofing by specifying which mail servers are authorized to send emails on behalf of your domain.
- Format: Starts with v=spf1. Examples include:
  - v=spf1 include:_spf.google.com ~all (Allows emails from Google Workspace, soft fails others)
  - v=spf1 a mx ip4:192.168.1.1 -all (Allows emails from A/MX records and a specific IP, hard fails others)
- Key terms: include, a, mx, ip4, ~all (softfail), -all (hardfail).
DKIM (DomainKeys Identified Mail):
- Purpose: Provides a digital signature to emails, allowing recipients to verify that the email was authorized by the owner of that domain and hasn't been altered.
- Format: Typically involves a selector (e.g., google._domainkey) and a public key.
- Example: A TXT record for DKIM might look like google._domainkey.example.com TXT "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMII...AQAB"". You usually check the TXT record for a specific selector (e.g., google._domainkey).
DMARC (Domain-based Message Authentication, Reporting & Conformance):
- Purpose: Instructs receiving mail servers on how to handle emails that fail SPF or DKIM checks and provides reporting back to the domain owner.
- Format: Starts with v=DMARC1. Example:
  - v=DMARC1; p=quarantine; rua=mailto:[email protected]; (Quarantine emails failing checks, send aggregate reports to the specified email address).
- Key terms: p= (policy: none, quarantine, reject), rua= (aggregate reporting), ruf= (forensic reporting).
Google Site Verification:
- Purpose: To verify that you own the domain you're using with Google services like Google Search Console.
- Format: A specific string provided by Google, often starting with google-site-verification=. Example:
  - google-site-verification=aBcDeFgHiJkLmNoPqRsTuVwXyZ1234567890

When you check TXT records, compare the output against the requirements from the service you are configuring. Even a small typo can prevent the record from working correctly.

Troubleshooting Common TXT Record Issues

Even with the right tools, issues can arise when configuring or checking TXT records. Here are some common problems and how to address them:

Propagation Delays: DNS changes don't happen instantly across the entire internet. It can take anywhere from a few minutes to 48 hours for changes to propagate fully. If you just made a change and can't see it, wait a bit and check again using an online tool that shows results from various locations.
Typos and Incorrect Formatting: TXT records are text strings. A single misplaced character, incorrect capitalization (though TXT values are case-sensitive, the process of checking and setting them usually handles it), or missing quote can render the record invalid. Double-check the exact string provided by the service.
Incorrect Hostname/Name Field: For the root domain (e.g., example.com), the hostname is often left blank or entered as '@'. For subdomains (like google._domainkey.example.com for DKIM), the full subdomain name is required. Ensure you're using the correct hostname for the TXT record.
Multiple SPF Records: You can only have one SPF record per domain. If you have multiple TXT records starting with v=spf1, email servers will treat your SPF configuration as invalid. Consolidate them into a single record.
Missing Record: The record simply might not have been added to your DNS settings yet. Verify with your domain registrar or DNS hosting provider.
Conflicting Records: While less common for TXT, ensure you don't have conflicting or overlapping DNS configurations that might interfere.

If you're still struggling, consult the documentation of the service requiring the TXT record or reach out to your DNS provider's support.

Frequently Asked Questions (FAQ)

Q: How long does it take for TXT records to update?

A: DNS propagation can take anywhere from a few minutes to 48 hours, though typically it's much faster (within a few hours). The TTL (Time To Live) setting on your DNS record influences how long caches store old information.

Q: Can I check TXT records for any domain?

A: Yes, as long as the domain's DNS records are publicly accessible, you can use online tools or command-line utilities to check its TXT records.

Q: What is the difference between checking TXT records and other DNS records?

A: The process is similar, but you specifically select 'TXT' as the record type. Each record type (A, CNAME, MX, TXT) stores different kinds of information for different purposes.

Q: My email is going to spam. How can checking TXT records help?

A: Poorly configured or missing SPF, DKIM, and DMARC TXT records are common reasons for emails landing in spam. Checking these records helps you identify and fix authentication issues.

Conclusion

Mastering how to check TXT records is an essential skill for anyone managing a domain, especially for email deliverability and service verification. Whether you opt for the simplicity of online DNS lookup tools or the power of command-line utilities like dig and nslookup, the ability to accurately retrieve and interpret TXT record data is invaluable.

By understanding the purpose of these records – particularly for crucial email authentication protocols like SPF, DKIM, and DMARC – you can proactively troubleshoot issues and ensure your domain is properly configured for optimal performance and security. Regularly checking your TXT records is a small step that can prevent significant headaches down the line. Keep this guide handy, and you'll be able to confidently manage your domain's DNS settings.