Check the public DNS TXT records of any domain using our free online TXT Record Lookup tool. Enter a domain name to view its published text records, including entries used for email authentication, domain ownership verification and other DNS-based services.
The tool displays TXT record values, their associated DNS names and reported time-to-live (TTL). It supports publicly resolvable domains, including .pk, .com.pk, .org.pk, .com and other domain extensions.
Use the TXT Record Lookup tool below to check your domain.
Enter a public domain or DNS hostname to see the TXT records returned by a public DNS resolver. A DNS TXT record stores text associated with a DNS name. Websites and email services use TXT records for domain ownership verification, SPF sender policies, DKIM public keys, and DMARC policies. The presence of text does not prove that a configuration is valid. Look up the main domain for many verification and SPF records. DMARC policies usually appear at Each result includes its DNS owner name, record text, and the time-to-live (TTL) reported by the resolver. A blank result is not necessarily a DNS failure. Recent DNS changes may take time to appear in different caches. Long TXT records may contain several quoted character strings that belong to one record.Check DNS TXT records
What does a TXT record show?
Which name should you check?
_dmarc.yourdomain.com. DKIM records are usually published under a service-specific selector such as selector._domainkey.yourdomain.com. Replace these examples with your actual DNS name.How should you read the results?
How to Check TXT Records for a Domain
Checking TXT records takes only a few steps.
- Enter your domain name. Type a domain such as
example.cominto the lookup field. Do not includehttps://,wwwunless it is part of the specific DNS hostname you need to query, or a website path. - Run the lookup. Click Look up TXT to request the publicly available DNS TXT records.
- Examine the results. Review the returned records, including their text values, hostnames and TTL information.
- Copy a record if needed. Use the Copy text button to copy a displayed TXT value for comparison with your DNS provider’s settings.
To check a specific subdomain or email authentication record, enter its complete DNS name rather than only the main domain.
Common Types of DNS TXT Records
TXT records are used for several different purposes. Understanding the record type helps you determine whether the information returned by a DNS lookup is relevant to your task.
| Purpose | Typical DNS Name | What to Look For |
|---|---|---|
| SPF | example.com | A value beginning with v=spf1 |
| DKIM | selector._domainkey.example.com | A DKIM public key, often containing v=DKIM1 and p= |
| DMARC | _dmarc.example.com | A policy beginning with v=DMARC1 |
| Domain verification | example.com or a provider-specified name | A verification token supplied by the service |
| Other verification or service settings | Provider-specified DNS hostname | Text matching the provider’s instructions |
These are examples of DNS name formats, not actual lookup results. Some services use custom subdomains or differently formatted values.
SPF TXT Records
Sender Policy Framework (SPF) allows a domain owner to publish rules identifying which mail servers are authorized to send email using that domain in the SPF-checked identity.
SPF policies are published as DNS TXT records and normally begin with v=spf1.
A TXT lookup can show whether an SPF record is visible at the name you queried. However, it does not evaluate every SPF mechanism, test the DNS lookup limits or guarantee that outgoing messages will pass SPF authentication.
DKIM TXT Records
DomainKeys Identified Mail (DKIM) uses cryptographic signatures to help receiving mail servers verify signed email messages.
A DKIM public key can be published at a DNS name such as:
selector._domainkey.example.com
The selector is provided by your email service or identified in the email’s DKIM signature. You must use the correct selector to locate the intended record.
This lookup displays the TXT record returned by DNS. It does not verify an email message’s DKIM signature or search automatically for every possible selector.
DMARC TXT Records
Domain-based Message Authentication, Reporting and Conformance (DMARC) provides domain owners with a way to publish email authentication policies and reporting preferences.
DMARC policies are normally queried using a hostname such as:
_dmarc.example.com
A DMARC record begins with v=DMARC1 and includes policy information, such as p=none, p=quarantine or p=reject.
The tool can display the published record, but it does not perform a complete DMARC validation or test how a receiving mail provider handles individual messages.
Domain Ownership Verification Records
Website platforms, search services and other providers may ask domain owners to add a specific DNS TXT record before activating a service or confirming domain ownership.
After adding the requested record through your DNS hosting provider, use this lookup to check whether the expected value is publicly visible.
Compare the complete returned value with the exact text supplied by the service. Finding the record in public DNS is useful evidence, but final verification still depends on the provider’s own system.
Understanding TXT Lookup Results
TXT Record Value
The record value contains the text published under the requested DNS name.
A domain can have several TXT records serving different purposes. Each should be reviewed separately.
Long records may appear as multiple quoted text segments. These segments can belong to one DNS TXT record rather than representing several independent records. The lookup displays the resolver’s presentation format without automatically interpreting the record’s application-specific meaning.
TTL (Time to Live)
TTL represents the caching lifetime reported by the DNS resolver, expressed in seconds.
For example, a TTL of 300 seconds corresponds to five minutes. This does not mean every DNS resolver worldwide will update within exactly five minutes.
The displayed TTL is a resolver-reported value, not a countdown showing when a DNS change will become visible everywhere.
No TXT Records Found
If the lookup returns no TXT records, the queried DNS name may exist without any TXT records, or the requested record may be published under a different hostname.
For example, a DMARC policy may be available under _dmarc.example.com even when your lookup of example.com does not display that policy.
DNS Name Not Found (NXDOMAIN)
An NXDOMAIN response means the queried DNS name was not found by the resolver.
Check the domain spelling and any subdomain labels. This response is different from finding an existing DNS name that has no TXT records.
DNS Lookup Error
A timeout, resolver failure or other DNS error does not establish that the domain lacks TXT records.
If an error appears, repeat the lookup later or compare the result using your DNS provider’s management interface.
Why Is My TXT Record Not Showing?
If you recently added or modified a DNS TXT record, several issues may explain why the expected value is missing.
Incorrect DNS hostname: Verify that you entered the precise hostname required by your service. SPF, DKIM and DMARC records may use different names.
Wrong DNS hosting provider: Confirm that the record was created in the authoritative DNS zone currently serving your domain. Editing a DNS panel that is no longer authoritative will not publish the intended change.
Caching delay: Previously cached DNS responses may remain visible until their caching periods expire. Check again later and compare the results with the authoritative DNS provider.
Incorrect record value: Make sure the TXT value matches the instructions from the service requesting it. Missing characters, accidental spaces or incorrectly entered segments may prevent a service from accepting the record.
Different resolver results: Public DNS resolvers may temporarily return different answers because of caching or DNS configuration changes.
For domains registered in Pakistan, including .pk and .com.pk, the same DNS troubleshooting principles apply.
How This TXT Record Lookup Works
NetTools Pakistan uses a server-side DNS lookup to request public TXT records through Google Public DNS over HTTPS.
When you submit a hostname, the website sends the request to its WordPress server. That server requests the DNS TXT records from Google’s public resolver and returns the results for display.
The tool may temporarily cache results to reduce repeated requests. It also applies lookup limits to help control excessive automated requests.
Important limitations:
- Results show the selected public resolver’s view rather than every DNS server on the internet.
- The tool does not modify your DNS records or access your domain registrar account.
- It does not certify SPF, DKIM, DMARC or domain ownership configuration.
- A lookup may fail because of DNS errors, network problems or request limits.
- The tool displays up to 50 TXT records from a single response.
The entered DNS hostname is sent to Google Public DNS through this website’s server. Normal website, server and DNS resolver logging practices may apply.
Check Your DNS Configuration
A TXT record lookup is a useful first step when verifying a domain, troubleshooting an email authentication setup or checking whether a recently published DNS value is visible.
If the expected record appears, compare its complete value with your provider’s requirements. If it does not appear, check the hostname, authoritative DNS settings and any applicable caching delay before making further changes.
NetTools Pakistan provides this independent DNS lookup service for informational and troubleshooting purposes. It is not affiliated with Google Public DNS, domain registrars or email service providers.
Technical References
- RFC 1035 – Domain Names: Implementation and Specification
- RFC 7208 – Sender Policy Framework
- RFC 6376 – DKIM Signatures
- RFC 9989 – DMARC
- Google Public DNS – DNS-over-HTTPS JSON API