A TXT record is a type of Domain Name System (DNS) entry that stores text-based information associated with a domain. It's used to verify ownership, authenticate email senders, and configure services like spam protection and website verification.
TXT records are part of the DNS system, which translates human-readable domain names like example.com into IP addresses that computers use to communicate. Unlike A or MX records, which handle routing, TXT records carry arbitrary text data. They're not meant to direct traffic-they store instructions.
For example, Google uses a TXT record to verify domain ownership during setup for Google Workspace. When you add a specific string like v=spf1 include:_spf.google.com ~all to your domain's DNS, Google confirms your control over the domain. This is how TXT records enable trust in online systems.
DNS resolvers check TXT records when validating domain configurations. When a service like Gmail or Microsoft 365 needs to confirm whether an email came from a legitimate sender, it queries the domain's TXT records for SPF, DKIM, or DMARC policies.
Each TXT record contains a key-value pair format: a name (usually the domain or subdomain), a type (TXT), and a value (the actual text). The value can be a single string or multiple quoted strings. For example:
example.com. IN TXT "v=spf1 include:_spf.google.com ~all"
This line tells mail servers that only emails sent through Google's infrastructure are authorized for example.com. Any message from another source gets flagged as suspicious.
Multiple TXT records can exist for one domain. The DNS protocol allows this, but some systems may ignore extra records. Always test with tools like dnschecker.org to ensure visibility across networks.
TXT records serve several technical functions. The most common are for email authentication and domain verification.
| Use Case | Common Value Format | Example |
|---|---|---|
| Email Authentication (SPF) | v=spf1 include:_spf.provider.com ~all |
example.com. IN TXT "v=spf1 include:_spf.google.com ~all" |
| Domain Verification (Google, Bing) | google-site-verification=abc123xyz |
example.com. IN TXT "google-site-verification=KjLmNopQrStUvWxYzAbc123" |
| DMARC Policy | default=quarantine; dkim=pass; sp=reject |
_dmarc.example.com. IN TXT "v=DMARC1; p=reject; rua=mailto:[email protected]" |
| Sender Policy Structure (SPF) | v=spf1 ip4:192.0.2.0/24 -all |
example.com. IN TXT "v=spf1 ip4:192.0.2.0/24 -all" |
These values aren't random. They follow standardized syntax defined by RFC 1035 and later extensions. Misconfigurations often cause email delivery failures or security warnings.
One non-obvious fact: TXT records have a 255-character limit per string. If a value exceeds that, it must be split into multiple quoted strings. For example:
example.com. IN TXT "firstpart" "secondpart" "thirdpart"
Some DNS providers automatically merge these into a single logical value. Others require manual handling. Always check your DNS provider's documentation.
People often mistake TXT records for other DNS types. A common error is confusing TXT with CNAME or MX records. While CNAME maps a name to another name, and MX directs mail, TXT holds text data.
Another frequent mix-up: assuming TXT records affect website performance. They don't. They're read only during validation processes-like when sending an email or verifying a site with search engines. Changing a TXT record doesn't slow down your site or affect loading speed.
I once debugged an email deliverability issue where a client had accidentally placed an SPF policy inside a CNAME record. The mail server rejected messages because the SPF check failed. After moving the correct TXT record into place, delivery resumed within 15 minutes. This shows how critical proper placement is-even small errors break automation.
TXT records underpin digital trust. Without them, services couldn't verify domain authenticity. Phishing attacks rely on spoofed domains. TXT records help prevent that.
According to the Anti-Phishing Working Group (APWG), over 80% of phishing sites use domains that lack valid SPF or DMARC records. These missing TXT entries make it easier for attackers to impersonate brands.
Spam filters use TXT records to assess sender legitimacy. The Sender Policy Structure (SPF), defined in RFC 7208, relies on TXT records to list authorized IPs. If a message comes from an unauthorized IP, the receiving server can reject it based on the SPF policy.
When setting up email, always configure SPF, DKIM, and DMARC using TXT records. This layered approach reduces the risk of spoofing. For example, a complete setup includes:
v=spf1 include:_spf.google.com ~all (SPF)default=_domainkey.example.com (DKIM)v=DMARC1; p=reject; rua=mailto:[email protected] (DMARC)Each uses a TXT record. Missing any weakens your domain's defenses.
Always verify TXT records after adding them. Propagation takes time-up to 48 hours in rare cases-but usually completes within 15 minutes. Use command-line tools like dig or nslookup:
dig TXT example.com
Or use online tools like mxtoolbox.com to check live DNS resolution. These tools show real-time results across global servers.
If a TXT record isn't visible, check for typos, incorrect quoting, or TTL settings. Some providers cache records for longer than expected. Clearing the local DNS cache with ipconfig /flushdns (Windows) or sudo dscacheutil -flushcache (macOS) can help.
For advanced users, tools like dnswatch.info provide historical tracking of DNS changes. This helps detect unauthorized modifications.
A TXT record is a foundational element of secure domain management. It enables email authentication, verifies domain ownership, and supports anti-spam measures. Despite being simple in concept, its impact is profound.
Understanding what is a TXT record isn't just technical-it's essential for anyone managing a domain. securing a website, properly configured TXT records protect against fraud and improve deliverability.