Free TXT Record Lookup

What Are TXT Records?

TXT (Text) records are a versatile type of DNS record that allow domain administrators to store arbitrary text data in their DNS configuration. Unlike A records (which point to IP addresses) or MX records (which route email), TXT records carry human- and machine-readable text that serves a wide range of purposes.

Originally designed for general-purpose notes, TXT records have become the backbone of email authentication and domain verification on the modern internet. Nearly every domain on the web has at least one TXT record, and most have several -- for SPF, DMARC, and service verification.

Common TXT Record Types

SPF (Sender Policy Framework)

SPF records start with v=spf1 and define which mail servers are authorized to send email on behalf of your domain. When a receiving server gets an email claiming to be from your domain, it checks your SPF record to verify the sending server is on the approved list. This is a critical defense against email spoofing. Use our SPF Record Checker for a detailed SPF analysis.

DKIM (DomainKeys Identified Mail)

DKIM records are published as TXT records at specific subdomains (e.g., selector._domainkey.example.com). They contain public keys used to verify the cryptographic signatures attached to outgoing emails. This ensures that email content has not been altered in transit and confirms the sender's identity.

DMARC (Domain-based Message Authentication)

DMARC records are published at _dmarc.example.com and tie together SPF and DKIM. They instruct receiving mail servers on what to do when an email fails authentication -- whether to allow it, quarantine it, or reject it outright. DMARC also enables reporting so domain owners can monitor authentication failures. Check your DMARC setup with our DMARC Record Checker.

Verification Records

Many services -- including Google, Microsoft, Facebook, Atlassian, Adobe, and others -- require you to add a unique TXT record to prove you own a domain. These records typically follow a pattern like google-site-verification=abc123. Once verified, you gain access to the service's domain-specific features such as Google Search Console, Microsoft 365 admin, or Meta Business tools.

TXT Records for Domain Verification

Domain verification via TXT records is the most widely accepted method for proving domain ownership across the internet. The process is straightforward: a service generates a unique token, you add it as a TXT record in your DNS, and the service queries your DNS to confirm the record exists. Because only a domain's administrator can modify its DNS records, the presence of the token proves ownership.

Many SaaS platforms use this same pattern to verify that customers control the domains they want to connect. Other platforms use routing-based verification (for example, checking required CNAME or A records) depending on their architecture.

TXT Records and Custom Domains

For SaaS platforms that support custom domains, TXT record verification can be part of the domain onboarding workflow. Depending on implementation, platforms may verify domain control via TXT tokens or by validating required routing records before activating SSL and traffic.

SaaSKevin verifies custom domains by checking that required routing records (CNAME for subdomains, A/AAAA for apex domains) resolve to expected targets. Once routing checks pass, SSL provisioning and traffic routing proceed automatically.

Combined with CNAME records for traffic routing and automatic SSL certificate management, this creates a secure and trustworthy custom domain experience for your users. You can inspect the full DNS configuration for any domain with our DNS Lookup Tool.