You've added a TXT record to your domain's DNS settings, clicked Verify, and received an error saying the record couldn't be found. You check your DNS dashboard, and the record is right there. So why isn't it working?
A TXT record not showing up usually means one of three things: the record was added to the wrong DNS location, the hostname or verification value is incorrect, or the DNS resolver is still returning cached information.
The good news is that you don't have to keep changing settings and hoping something works. By checking the TXT record directly, you can identify whether the problem is with your DNS configuration or the service trying to verify your domain.
This guide explains how to find a missing TXT record, troubleshoot DNS verification errors, and confirm that your domain is ready for verification.
Why Is My TXT Record Not Showing Up?
A DNS TXT record may not appear in a lookup even when it seems correctly configured in your domain management dashboard.
The most common reasons include:
- Incorrect DNS host: The record was created under www instead of the root domain, or vice versa.
- Wrong DNS provider: The record was added to a dashboard that doesn't manage your domain's active nameservers.
- DNS caching: A resolver is temporarily returning an older result or a cached response indicating the record doesn't exist.
- Incorrect record value: The verification token contains a typo, missing character, or unintended formatting.
- Unsaved DNS changes: The record was entered but wasn't successfully published.
- Subdomain mismatch: The verification service expects the TXT record at a different hostname.
- DNS resolution errors: Problems such as incorrect DNSSEC configuration prevent the record from being retrieved.
Before modifying anything, check whether your record is publicly visible. This helps separate a missing DNS record from a verification failure.
How to Check If Your DNS TXT Record Exists
The quickest way to troubleshoot a missing TXT record is to perform a DNS lookup.
A lookup shows which TXT records are publicly returned for a particular domain or hostname. You can compare those results with the record you entered in your DNS dashboard.
Method 1: Check Your TXT Record Using Smooli AI
You can use the Smooli AI DNS Checker to inspect your domain's publicly available DNS records without installing command-line software.
Follow these steps:
- Open the Smooli AI DNS Checker.
- Enter the domain you want to check, such as
example.com. - Run the DNS lookup and inspect the TXT record results.
- Look for the verification value provided by Google Search Console, your email provider, or another service.
- Compare the publicly returned TXT value against the expected value.
For example, Google Search Console may ask you to create a record similar to:
| Field | Example |
|---|---|
| Type | TXT |
| Name / Host | @ |
| Value | google-site-verification=abc123example |
| TTL | Auto |
If the lookup returns the expected TXT value, your record is publicly visible through the DNS resolver used for the lookup.
If it doesn't appear, investigate the DNS settings before retrying verification.
Important: A successful DNS lookup does not automatically mean Google or another service has completed verification. It confirms that the queried DNS server can retrieve the record.
Method 2: Check TXT Records Using Command Prompt or Terminal
You can also inspect TXT records using nslookup or dig.
On Windows, open Command Prompt and run:
nslookup -type=TXT example.comReplace example.com with your domain.
To query Google's public DNS resolver specifically, run:
nslookup -type=TXT example.com 8.8.8.8On macOS or Linux, open Terminal and use:
dig example.com TXT +shortFor a lookup through Cloudflare's public DNS resolver:
dig @1.1.1.1 example.com TXT +shortIf your TXT record exists, the response may include a value such as:
"google-site-verification=abc123example"Remember that a domain can have several TXT records. You might see SPF information, verification tokens, and other text values returned together.
If you don't see the expected record, continue with the fixes below.
9 Ways to Fix a TXT Record That Is Not Showing Up
1. Confirm That the TXT Record Was Created Correctly
Start with the simplest possibility: the record might not have been saved correctly.
Open your DNS management dashboard and locate the record you recently added.
Check that:
- The record type is TXT, not A, CNAME, or another type.
- The host/name field is correct.
- The value field contains the complete verification token.
- The DNS provider shows the record as saved or active.
Some DNS providers require an additional confirmation before publishing changes.
If you don't see the TXT record in your dashboard, add it again using the instructions from the verification service.
Avoid creating multiple identical verification records unnecessarily. First confirm whether the original record was saved.
2. Correct the TXT Record Host or Name
An incorrect hostname is one of the most common reasons for DNS verification failure.
For example, suppose you're verifying ownership of:
example.com
The verification service may require the TXT record at the root domain. In many DNS control panels, the root domain is represented by @ or an empty Name field.
If you accidentally enter www, the TXT record will instead be created at:
www.example.com
The two hostnames are different DNS names.
| Intended location | Common DNS Name entry |
|---|---|
| example.com | @ or blank |
| www.example.com | WWW |
| verify.example.com | verify |
| acme-challenge.example.com | acme-challenge |
The exact entry depends on your DNS provider. Some DNS dashboards expect a short hostname such as verify, while others accept the complete hostname verify.example.com.
Entering the full domain into a panel that automatically appends your domain could accidentally create:
verify.example.com.example.comHow to fix it: Check the full hostname displayed in your DNS dashboard and compare it with the location required by the verification service.
3. Make Sure You're Editing the Active DNS Provider
You might have purchased your domain from one company, hosted your website with another, and delegated your DNS to a third provider.
For example, you could purchase a domain through Namecheap, host the website with Hostinger, and use Cloudflare for DNS management.
In that situation, adding a TXT record to the registrar's default DNS dashboard won't necessarily publish it if Cloudflare is managing the active DNS zone.
To identify your domain's nameservers, run:
dig example.com NS +shortYou can also inspect NS records using the Smooli AI DNS Checker.
Compare the results with the nameservers configured at your domain registrar.
How to fix it: Add the TXT record to the authoritative DNS provider currently responsible for the domain.
For more complex configurations, including separately delegated subdomains, check the authoritative nameservers for the specific hostname you're verifying.
4. Check the TXT Record Value for Errors
Even a small difference between the expected verification token and the published TXT record can cause verification to fail.
For example, Google Search Console might give you:
google-site-verification=abc123exampleIf your DNS value is entered as:
google-site-verification=abc123It won't match.
Common mistakes include missing characters, additional spaces, copying an outdated token, or pasting the wrong information into the Name field instead of the Value field.
Some DNS providers automatically handle the quotation marks used to represent TXT strings. You normally don't need to add extra quotation marks unless your provider specifically requires them.
How to fix it: Copy the verification value directly from the service and compare it with the exact value returned in a public DNS lookup.
Don't manually shorten or modify the token.
5. Check DNS Caching and Propagation
If your TXT record is correct but public DNS lookups return an old or empty result, DNS caching might be responsible.
Recursive DNS resolvers temporarily store DNS responses to reduce repeated queries.
For example, a resolver may have checked your hostname before you created the TXT record and cached a response indicating that the record wasn't present.
This behavior is called negative DNS caching.
Even after the record is published on your authoritative nameserver, that resolver may continue returning the cached negative response until its cache entry expires.
To investigate, compare responses from different DNS resolvers:
dig @8.8.8.8 example.com TXT +short
dig @1.1.1.1 example.com TXT +shortIf one returns the new record and another doesn't, caching may explain the difference.
You can also use Smooli's DNS Propagation Checker to examine DNS resolution across locations and available resolvers.
How to fix it: If the correct record is already available from the authoritative DNS servers, allow cached responses to expire before retrying verification.
Lowering the TTL on a newly added TXT record does not immediately clear negative responses that resolvers already cached.
For a detailed explanation of DNS caching, TTL, and update behavior, see our guide on what DNS propagation is and how DNS changes work.
6. Verify the Correct Domain or Subdomain
DNS verification can fail when you're checking the wrong hostname.
For example, these are separate DNS lookup targets:
example.comwww.example.comshop.example.com_acme-challenge.example.com
The TXT record must be published at the exact DNS name required by the service.
This is especially important when configuring email authentication or validating an SSL certificate
A DKIM record might be stored at:
selector1._domainkey.example.comAn ACME DNS-01 certificate challenge might require:
_acme-challenge.example.comLooking up TXT records for example.com alone won't necessarily show records stored at those names.
How to fix it: Copy the hostname from the service's DNS configuration instructions and perform a TXT lookup for that exact hostname.
7. Check for DNSSEC or DNS Resolution Errors
Sometimes a TXT record isn't returned because DNS resolution is failing, rather than because the record is missing.
For example, an incorrectly configured DNSSEC setup can cause validating resolvers to reject DNS responses.
This may happen after changing DNS providers without updating the relevant DNSSEC delegation settings.
A lookup could return:
SERVFAILThis response indicates that the resolver couldn't complete the DNS query. It does not, by itself, prove that the TXT record is missing.
DNSSEC problems are one possible cause, but server errors and other DNS configuration issues can also produce SERVFAIL.
How to fix it: Check whether your domain's DNSSEC settings match the current authoritative DNS provider. If you recently migrated nameservers, verify the DS records configured through your registrar.
Don't disable DNSSEC blindly. Correct the configuration or work with your DNS provider if DNSSEC validation is failing.
8. Inspect Existing TXT Records and Possible Conflicts
Many websites already have TXT records for email security, search engine verification, and third-party services.
Having more than one TXT record at the same hostname is generally valid.
For example, a root domain can have both:
v=spf1 include:_spf.example.net ~alland
google-site-verification=abc123exampleThese records can coexist because they serve different purposes.
However, problems can occur if you accidentally overwrite a record, combine unrelated verification values, or add a TXT record at a hostname that already uses a conflicting CNAME configuration.
SPF records need special attention: multiple separate SPF policies beginning with v=spf1 at the same hostname can cause SPF validation errors.
How to fix it: Review existing records before editing them. Add independent verification tokens as separate TXT records where your provider supports this, and follow the specific service's instructions for records such as SPF and DKIM.
Avoid deleting existing records unless you understand what they're used for.
9. Retry Verification After Confirming Public DNS Visibility
If the correct TXT record is publicly visible but the verification service still rejects it, the issue may be on the verification side.
The service might still be using an older cached response, the verification job may not have completed, or the token being checked may no longer match the one associated with your current verification request.
Before retrying, confirm that:
- The correct record is publicly visible.
- The TXT value matches the current token.
- The full hostname matches the verification instructions.
- You're verifying the intended domain or account.
- Your DNS lookups aren't returning resolution errors.
Once these checks pass, retry verification through the service.
If verification continues to fail, consult the service's documentation or support team with your lookup results.
TXT Record Exists, but DNS Verification Still Fails?
A visible TXT record and successful domain verification are not the same thing.
A DNS lookup checks whether a resolver can retrieve the TXT record. A verification service checks whether the expected record exists at the required hostname and contains the correct value.
Use this table to identify the next step:
| What you find | What it means | What to do |
|---|---|---|
| Record is missing from the DNS dashboard | It may not have been saved | Create or save the record |
| Record exists in dashboard but not authoritative DNS | It isn't being served correctly | Check provider, hostname, and publication |
| Record appears on some resolvers but not others | Cached responses may differ | Wait for cache expiry |
| Record appears everywhere but contains a different token | The service can't match the value | Correct the verification token |
| TXT lookup returns SERVFAIL | DNS resolution is failing | Investigate DNSSEC and nameserver errors |
| Correct record is publicly visible but verification fails | The service hasn't accepted it | Recheck the account/property and retry |
For a deeper technical check, query an authoritative nameserver directly.
First find your domain's authoritative nameservers, then run a query such as:
dig @ns1.example-dns.net example.com TXT +shortReplace ns1.example-dns.net with an actual authoritative nameserver for your domain.
If the authoritative server returns the correct TXT record but public recursive resolvers don't, caching or DNS resolution along the lookup path becomes a more likely explanation.
If the authoritative server doesn't return the record, revisit the DNS configuration rather than simply waiting.
How to Fix Google Search Console TXT Record Verification Failed
Google Search Console is a common example of DNS TXT verification.
When you add a Domain property, Google asks you to prove that you control the domain, typically by adding a DNS record.
If Search Console reports that your verification TXT record wasn't found, follow these steps.
Step 1: Copy the verification token from Google Search Console
Open Google Search Console, select or add your Domain property, and locate the DNS verification instructions.
Google will provide a unique TXT value similar to:
google-site-verification=abc123exampleCopy the complete value.
Step 2: Add the record to the correct DNS zone
Open the DNS provider responsible for your domain.
For a typical root-domain verification, enter:
| Setting | Value |
|---|---|
| Record type | TXT |
| Host/Name | @ (or blank, as required) |
| Value | Your exact Google verification token |
| TTL | Provider default or Auto |
Save the changes.
If your DNS provider uses different field names, follow its instructions for adding a root-domain TXT record.
Step 3: Confirm that Google can retrieve the record
Use the Smooli DNS Checker to inspect your domain's TXT records.
You can also use Google's Admin Toolbox Dig to check what is publicly returned.
Look for the full google-site-verification= value.
If the value doesn't appear, revisit the troubleshooting steps above.
Step 4: Return to Search Console and click Verify
Once the correct TXT value is publicly visible, return to Google Search Console and retry verification.
According to Google's official verification documentation, manually added DNS records can sometimes take up to two or three days to become available to Google's verification process.
If verification doesn't succeed immediately, avoid repeatedly deleting and recreating a correctly published TXT record. Instead, check that the token matches and retry after an appropriate interval.
Step 5: Keep the verification record after success
When verification succeeds, leave the TXT record in place.
Google may periodically check that the verification token still exists. Removing it could eventually cause your verified ownership status to expire.
How Long Does a New TXT Record Take to Show Up?
A TXT record may become publicly visible within minutes after the authoritative DNS provider publishes it, but some changes can take longer to appear through recursive resolvers.
The delay depends on several factors, including the DNS provider, cached responses, TTL values, and any recent nameserver changes.
For example, if a resolver already cached a previous TXT value with a TTL of 3,600 seconds, it may continue serving that value for up to an hour from the time it was cached.
Newly created records can also be affected by negative caching if the hostname was queried before the record existed.
This is why waiting is useful only after confirming that the record is correctly published.
If the record is missing from your authoritative DNS servers, additional waiting alone will not fix an incorrect configuration.
Learn more about these differences in our DNS propagation guide.
How to Verify Your TXT Record Using Smooli AI
Once you've corrected your DNS configuration, make one final check before returning to the verification service.
With the Smooli AI DNS Checker, you can inspect public DNS information for your domain and check whether your TXT value is returned.
Start by entering the exact domain or hostname associated with the record. Review the TXT lookup results and compare them with the expected verification value.
For example, if Google expects:
google-site-verification=abc123exampleThen that full token should be present in the TXT response for the required hostname.
If the correct value is visible, you have confirmed that the queried DNS resolver can retrieve your record.
If the record is still missing, use an authoritative DNS query to determine whether the issue lies in DNS publication or caching.
This gives you a more reliable troubleshooting process than making repeated DNS changes without checking the results.
Frequently Asked Questions
Why is my TXT record not showing up after 24 hours?
If your TXT record is still missing after 24 hours, confirm that you're editing the active DNS provider and using the correct hostname. Check the authoritative DNS servers directly. If the record isn't present there, the issue is more likely a configuration or publication problem than ordinary caching.
How do I know if my TXT record has propagated?
Look up your TXT record using different public DNS resolvers or a DNS propagation checker that supports TXT lookups. If they return the expected value, the record is publicly accessible through those resolvers. An authoritative DNS query can confirm whether your DNS provider is serving the correct record.
Can I have multiple TXT records for one domain?
Yes. Multiple TXT records can exist at the same hostname, such as separate Google verification and email-related records. However, certain protocols have their own rules. For example, publishing multiple SPF policies for one hostname can cause email authentication errors.
Why does Google Search Console say my TXT record was not found?
Google may not find the record if it's stored at the wrong DNS hostname, the active DNS provider isn't serving it, or the record hasn't become visible through the DNS infrastructure used for verification. Check the current token, query the correct hostname, and retry once the record is publicly available.
Can I use a TXT record for subdomain verification?
Yes, if the verification service supports it. The TXT record must be published at the hostname specified by that service. For example, a service verifying shop.example.com may require a TXT record at that subdomain rather than at example.com.
Does lowering the TTL fix a missing TXT record?
Not necessarily. Lowering TTL can help with future caching behavior, but it doesn't correct an incorrect hostname, missing DNS record, or wrong DNS provider. It also won't immediately remove negative DNS responses that have already been cached.
Does a missing TXT record affect my website?
A missing TXT record doesn't automatically prevent your website from loading, since website routing usually relies on other DNS record types. However, it can prevent domain ownership verification, email authentication, or other services from working correctly, depending on the record's purpose.
Final Thoughts
When a TXT record isn't showing up, the best solution isn't always to wait for DNS propagation.
Start by checking whether the record exists publicly. If it's missing, verify the hostname, active DNS provider, and record value. If it appears on authoritative DNS servers but not public resolvers, investigate caching. And if the correct record is publicly visible but verification still fails, review the verification service's requirements.
Most TXT record verification problems become easier to diagnose once you know exactly where the lookup is failing.
Before attempting verification again, use the Smooli AI DNS Checker to inspect your domain's DNS records and confirm that the expected TXT value can be retrieved.






.png&w=3840&q=75)