TXT Record Lookup

Use the TXT Record Lookup tool to check TXT records for any domain. TXT records are widely used for email authentication, domain verification, security policies, and third-party service setup. If you want to check SPF, DKIM, DMARC, Google verification, Microsoft verification, or other DNS text values, this tool helps you review the published TXT records online.

TXT records are especially important for email deliverability. Incorrect or missing SPF, DKIM, and DMARC records can cause emails to land in spam, fail authentication, or be rejected by major email providers. With IPMYP, you can enter a domain or TXT-related hostname and quickly see the TXT values returned by DNS.

If you need to confirm which IP address your current connection is using during DNS or email troubleshooting, you can identify your current public IP before reviewing domain records.

What Is a TXT Record?

A TXT record is a DNS record that stores text-based information for a domain or subdomain. Although it can hold general text, TXT records are most commonly used for email authentication, domain ownership verification, and security-related configuration.

Unlike A records or MX records, TXT records do not directly point a domain to a server. Instead, they publish readable policy or verification data that other systems can check.

Common uses of TXT records include:

• SPF: Defines which servers are allowed to send email for a domain.
• DKIM: Publishes a public key used to verify email signatures.
• DMARC: Defines how receivers should handle emails that fail SPF or DKIM checks.
• Domain verification: Proves ownership for services such as Google, Microsoft, analytics tools, SaaS platforms, CDN providers, and security services.
• Security policies: Publishes configuration values used by external systems.

Why TXT Records Matter for Email Security

TXT records are a core part of modern email security. They help receiving mail servers decide whether a message claiming to come from your domain is legitimate.

Without correct TXT-based email records, attackers may be able to spoof your domain more easily, and real emails from your business may be more likely to land in spam or fail authentication.

The most important email-related TXT records are SPF, DKIM, and DMARC.

SPF Record

SPF, short for Sender Policy Framework, tells receiving mail servers which IP addresses or services are allowed to send email for your domain.

An SPF record usually starts with:

v=spf1

For example:

v=spf1 include:_spf.example.com ~all

If SPF is missing or incorrectly configured, receiving mail servers may treat your messages as suspicious, especially when emails are sent from third-party platforms such as business email providers, marketing tools, CRM systems, or transactional email services.

DKIM Record

DKIM, short for DomainKeys Identified Mail, uses cryptographic signatures to help prove that an email was authorized by the domain and was not modified in transit.

DKIM records are usually published as TXT records under selector-based hostnames such as:

selector._domainkey.example.com

A DKIM TXT record usually starts with:

v=DKIM1

To check a DKIM record, you usually need to enter the exact DKIM selector hostname provided by your email service.

DMARC Record

DMARC, short for Domain-based Message Authentication, Reporting and Conformance, tells receiving mail servers what to do when an email fails SPF or DKIM checks.

DMARC records are published as TXT records under:

_dmarc.example.com

A DMARC record usually starts with:

v=DMARC1

DMARC can be configured to monitor, quarantine, or reject suspicious email. It also helps domain owners receive reports about email authentication results.

How to Use the TXT Record Lookup Tool

Using the IPMYP TXT Record Lookup tool is simple and does not require command-line tools or direct access to a DNS panel.

1. Enter a domain name, such as example.com.
2. For DKIM or DMARC, enter the exact TXT hostname when needed, such as selector._domainkey.example.com or _dmarc.example.com.
3. Run the TXT record check.
4. IPMYP sends a DNS query for TXT records on the hostname you entered.
5. Review the result, including TXT values, record type, host, and TTL when available.

For a broader DNS review that includes A, AAAA, MX, NS, CNAME, SOA, WHOIS, SSL, Ping, and other diagnostics, use the main DNS lookup tool and online network tools hub.

What Information Does a TXT Record Report Show?

After running the check, the TXT record report may show several useful DNS details.

• Host: The domain or subdomain being checked.
• Type: The DNS record type, which should be TXT.
• TXT Value: The full text value published in DNS.
• TTL: The Time To Live value that tells DNS resolvers how long they may cache the record.

If a domain has multiple TXT records, the tool may show all of them. This is normal because a domain may use TXT records for SPF, domain verification, analytics verification, security tools, SaaS platforms, and other services at the same time.

TXT Records and Email Deliverability

TXT records can strongly affect email deliverability. Mailbox providers often check SPF, DKIM, and DMARC when deciding whether to accept an email, reject it, or place it in the spam folder.

To improve domain email trust, you should check that:

• Your SPF record includes all services that send email for your domain.
• You do not publish multiple conflicting SPF records on the same hostname.
• Your DKIM record exists at the correct selector hostname.
• Your DMARC record exists at _dmarc.yourdomain.com.
• Your MX records point to the correct receiving mail servers.

TXT records should be reviewed together with MX Record Lookup when troubleshooting business email, inbound mail delivery, spam placement, or domain authentication problems.

How to Check an SPF Record

To check SPF, enter your root domain, such as example.com, and look for a TXT value that starts with v=spf1.

A valid SPF record may include IP addresses, include mechanisms, and rules that define which services are allowed to send email for the domain.

Common SPF issues include:

• No SPF record published.
• Multiple SPF records on the same hostname.
• Missing email service provider include values.
• Old providers still included after migration.
• Overly complex SPF records that may create lookup or maintenance problems.

How to Check a DKIM Record

DKIM records are usually not published directly on the root domain. They are normally published under a selector hostname provided by your email service.

For example:

google._domainkey.example.com
selector1._domainkey.example.com
default._domainkey.example.com

To check DKIM, you need to know the selector name. Enter the full selector hostname in the TXT lookup tool and look for a value that starts with v=DKIM1.

If no DKIM record is found, confirm the selector name in your email provider dashboard and check whether the DNS record was added to the correct DNS zone.

How to Check a DMARC Record

DMARC records are published at the _dmarc subdomain. To check DMARC for example.com, enter:

_dmarc.example.com

A DMARC record usually begins with v=DMARC1 and may include a policy such as p=none, p=quarantine, or p=reject.

If you are just starting with DMARC, many domains begin with a monitoring policy and then move to stricter enforcement after reviewing reports and fixing authentication issues.

Domain Verification TXT Records

TXT records are also widely used to prove domain ownership. Many services ask you to add a specific TXT value before they activate your domain, verify your account, or enable a custom domain connection.

You may see TXT records used for:

• Google site or Workspace verification.
• Microsoft 365 domain verification.
• Cloud platforms and CDN providers.
• Email marketing and transactional email platforms.
• Analytics and tracking services.
• Security and monitoring tools.

When verifying a domain, copy the TXT value exactly as provided by the service. Extra spaces, missing characters, wrong hostnames, or adding the record to the wrong DNS provider can cause verification to fail.

Why TXT Records May Not Appear Immediately

TXT record changes may take time to become visible because of DNS caching and TTL values. Some DNS resolvers may update quickly, while others may keep older results for longer.

If you recently added or changed a TXT record and it does not appear yet, check the following:

• The record was added to the active DNS provider.
• The hostname is correct.
• The TXT value was copied exactly.
• The TTL period has had enough time to expire.
• The domain is using the name servers where you added the record.

Common TXT Record Problems

TXT records are simple in concept, but small mistakes can break email authentication or service verification.

• Adding TXT records to the wrong DNS provider.
• Publishing more than one SPF record on the same hostname.
• Using the wrong DKIM selector.
• Adding DMARC to the root domain instead of _dmarc.
• Copying verification values with missing characters.
• Leaving old email provider records after migration.
• Using an SPF record that does not include all sending services.
• Forgetting to update TXT records after changing email providers.

Common Use Cases for TXT Record Lookup

• Email authentication: Check SPF, DKIM, and DMARC records for a domain.
• Spam troubleshooting: Review email DNS records when messages are landing in spam.
• Domain verification: Confirm whether Google, Microsoft, SaaS, CDN, or analytics verification records are live.
• Email migration: Verify TXT records after moving to a new mail provider.
• DNS audits: Review all TXT values published on important domains and subdomains.
• Security checks: Identify outdated, missing, or conflicting TXT-based policies.

Best Practices for Managing TXT Records

• Keep only one SPF record per hostname and include all authorized sending services in that single record.
• Use the exact DKIM selector and TXT value provided by your email service.
• Publish DMARC at _dmarc.yourdomain.com, not directly on the root domain.
• Remove outdated verification records when services are no longer used.
• Review TXT records after changing email providers, DNS providers, or hosting platforms.
• Document which TXT records belong to which service.
• Check MX records together with SPF, DKIM, and DMARC when diagnosing email delivery problems.

Frequently Asked Questions

What does a TXT Record Lookup do?

A TXT Record Lookup checks the DNS TXT records published for a domain or subdomain and shows the text values returned by DNS.

What is a TXT record used for?

A TXT record is used to publish text-based DNS information. Common uses include SPF, DKIM, DMARC, domain verification, service validation, and security policies.

How do I check my SPF record?

Enter your domain and look for a TXT record that starts with v=spf1. This record defines which servers and services are allowed to send email for your domain.

How do I check my DKIM record?

Enter the full DKIM selector hostname, such as selector._domainkey.example.com, and look for a TXT record that starts with v=DKIM1.

How do I check my DMARC record?

Enter _dmarc.example.com and look for a TXT record that starts with v=DMARC1. This record defines your domain’s DMARC policy.

Can a domain have multiple TXT records?

Yes. A domain can have multiple TXT records for different purposes. However, a hostname should normally have only one SPF record that includes all authorized sending services.

Why are my emails going to spam?

Email spam placement can be affected by missing or incorrect SPF, DKIM, and DMARC records, poor sender reputation, content quality, blacklist issues, and mail server configuration. TXT records are an important part of the diagnosis.

Why is my TXT record not showing?

The record may be added to the wrong DNS provider, the hostname may be incorrect, the TXT value may be copied incorrectly, or DNS cache may not have expired yet.

Check TXT Records Online With IPMYP

IPMYP’s TXT Record Lookup tool gives you a fast way to check SPF, DKIM, DMARC, verification records, and other DNS text values for any domain or subdomain. Enter a hostname above, run the check, and review the TXT records to understand how your domain is configured for email security, service verification, and DNS-based policies.