Free TXT Record Lookup & Checker

Your IP:
Check the DNS record Propagation in Multi-Region Check Multi-Region
Domain Type Primary NS Responsible Person Serial Refresh Retry Expire Minimum TTL
Name Server IP Address TTL
Domain Type TTL Record Value
Trace Result
Domain Type Record Status
Domain Type Record Status

Check live TXT DNS records, TTL values, and trace the full root-to-authoritative resolution path.

TXT (Text) Records Overview

What is a TXT record?

A TXT record is used to store arbitrary text data for a domain, often for email verification purposes like SPF, DKIM, and DMARC.

Why do you need a TXT record?

TXT records provide flexibility in managing domain-related text data and policies, enhancing security and domain management.

TXT record structure

A TXT record includes the domain name, TTL, record type (TXT), and text data. Example: example.com. 3600 IN TXT "v=spf1 include:_spf.example.com ~all"

How to create a TXT record?

Add a TXT record with the host (often @, or a service-specific label such as _dmarc or a google._domainkey selector) and paste the exact value the service provides, quotes included. A host can hold many TXT records, so adding one won't overwrite existing verification strings.

FAQs

Yes, a domain can have multiple TXT records for different purposes.

The maximum length of a TXT record is 255 characters per string, but multiple strings can be used together.

You can use online DNS lookup tools or command-line tools like dig or nslookup to verify your TXT record.

TXT records are commonly used for domain ownership verification and to publish email-authentication policies such as SPF, DKIM, and DMARC.

A domain can have many TXT records. Each individual string is limited to 255 characters, but a record can chain multiple strings and resolvers return them all.

TXT Record Troubleshooting & Common Fixes

Domain verification fails for Google Search Console, Microsoft 365, or Facebook

When services ask you to paste a verification token like google-site-verification=... or MS=ms12345678, the verification tool frequently reports that no matching TXT record was found.

How to fix: The most common cause is the host field. If the verification instructions say to place it on the root domain, enter @ (or leave it blank). If you typed your full domain name yourdomain.com into a panel that automatically appends your origin, you may have accidentally published the record at yourdomain.com.yourdomain.com. Run our TXT lookup to see exactly where your strings are published.

2048-bit DKIM key or long TXT record rejected (“String exceeds 255 characters”)

According to original DNS protocol specifications (RFC 1035), a single character-string within a TXT record cannot exceed 255 bytes. Modern 2048-bit RSA public keys used for DKIM are typically around 400 to 500 characters long.

How to fix: DNS supports chaining multiple strings within a single TXT record. If your DNS host throws a character limit error, split the long key into two quoted strings separated by a space: ("v=DKIM1; k=rsa; p=MIIBIj..." "...AQAB"). Resolvers automatically stitch the strings together seamlessly upon receipt.

Double quotation marks breaking string formatting

Some DNS control panels (such as Cloudflare or AWS Route 53) automatically add enclosing quotes around TXT values. If you manually enter quotation marks in the input box, the record is saved with literal duplicate quotes: ""v=spf1..."", breaking parser syntax.

How to fix: Check the returned raw value in our TXT lookup tool. If you see doubled quotes at the beginning and end, edit the record in your DNS manager and paste the content without surrounding quotation marks.

DNS Info extension for Chrome is now available

Install