Skip to content

What is a TXT record?

By Ash, Founder, HosteazePublished 3 min read

A TXT (text) record is a DNS entry that stores a line of text against your domain. Other services read it to check facts about you, most often to prove you own the domain or to publish email security settings such as SPF, DKIM and DMARC. You can have many TXT records on one domain.

Handwritten paper notes pinned to a cork board, like the many short text notes a domain keeps in its TXT records.
Credit: tom69green via Pixabay

Most DNS records tell computers where to go. A TXT record is different: it's a sticky note on your domain. It doesn't send visitors or email anywhere. It just holds a line of text that another service can look up to check something about you.

The original DNS standard, RFC 1035, left the meaning open: "the semantics of the text depends on the domain where it is found." That vagueness turned out to be useful. Today TXT records carry domain verification codes and most of the email security settings that decide whether your messages are trusted.

What are TXT records used for?

UseWhat the record starts withWho reads it
Proving you own a domainA code such as google-site-verification=The service you're signing up to, e.g. Google Workspace or Search Console
Listing who can send your emailv=spf1Receiving mail servers checking SPF
Publishing your email signing keyv=DKIM1Receiving servers checking DKIM
Telling receivers what to do with fakesv=DMARC1Receiving servers applying your DMARC policy
Showing your logo in inboxesv=BIMI1Gmail, Apple Mail, Yahoo and others that support BIMI

Busy domains collect a lot of these. When we looked up bbc.co.uk in October 2026, it had more than a dozen TXT records, mostly verification codes for different software suppliers.

What does a TXT record look like?

Every record has a host (the name), a type, a TTL and a value. A verification record usually sits on the bare domain:

yourbusiness.co.uk.   3600   TXT   "google-site-verification=abcdef123_456wx789yz"

Some records sit on a special name instead. DMARC always lives at _dmarc.yourbusiness.co.uk, and DKIM keys live at names like google._domainkey.yourbusiness.co.uk. Putting a record on the wrong host is the most common reason a check fails.

Each piece of text inside a TXT record can be at most 255 characters. Long values, such as 2048-bit DKIM keys, are split into several quoted strings in the same record, and receivers join them back together. Most DNS panels do the splitting for you.

How do I add a TXT record?

To check it's live, look it up with a free DNS tool such as Google Admin Toolbox Dig. If it isn't showing yet, how long DNS propagation takes explains the wait.

What mistakes should I avoid?

The big one is creating a second SPF record. RFC 7208 says a domain must not have multiple SPF records, and two records starting v=spf1 make SPF fail for every email you send. Add the new sender to your existing record instead.

The other classic is pasting the value with the domain name tacked on, or adding a TXT record when the service asked for a CNAME. Copy exactly what you're given, into exactly the field it names. For the full email setup in the right order, see how to set up SPF, DKIM and DMARC.

Frequently asked questions

Can a domain have more than one TXT record?

Yes. Most business domains have several, one for each service that needs to check something. The exception is SPF, where you must have only one record starting v=spf1, so extra senders are added to that single record.

Do TXT records affect my website or email delivery?

They don't change where your website or email goes. That's the job of A, CNAME and MX records. But the SPF, DKIM and DMARC TXT records strongly affect whether your emails reach the inbox or the spam folder.

Can I delete an old verification TXT record?

It depends on the service, so check its help pages first. Google Workspace says its record can be removed once your domain is verified, but Google Search Console keeps checking for its token and will drop your access if it disappears.

Sources

  1. RFC 1035, Domain Names, Implementation and Specification (section 3.3.14, TXT)
  2. RFC 7208, Sender Policy Framework (sections 3.2 and 3.3)
  3. Google Workspace, Verify your domain with a TXT record
  4. Google Search Console, Verify your site ownership
A brass padlock with two keys beside it on a white backgroundTutorialHow to set up DMARC for Microsoft 365Add an SPF record with include:spf.protection.outlook.com, then create the two DKIM CNAME records Microsoft gives you and switch on DKIM signing in the Defender portal. Once both pass, add a TXT record at _dmarc with v=DMARC1; p=none; rua=mailto: and a reporting address, and tighten the policy later.Email and domains · 15 October 2026An old iron key in a rustic wooden door lockTutorialHow to set up DMARC for Google WorkspaceFirst make sure SPF includes _spf.google.com and DKIM is switched on in the Google Admin console. Wait 48 hours, then add a TXT record at _dmarc on your domain with the value v=DMARC1; p=none; rua=mailto: followed by a reporting address. Read the reports for a few weeks before moving to quarantine.Email and domains · 15 October 2026A tall stack of envelopes and letters seen side on, the scale bulk senders work atQuestionGoogle, Yahoo and Outlook bulk sender rules, explainedGmail, Yahoo and Outlook.com require anyone sending around 5,000 or more emails a day to them to pass SPF, DKIM and DMARC, offer one-click unsubscribe and keep spam complaints below 0.3%. Every sender, whatever the volume, needs at least SPF or DKIM, valid reverse DNS and a low spam rate.Email and domains · 15 October 2026Red octagonal stop sign against a blue sky, like a mail server refusing a messageQuestionWhat does a 550 email bounce error mean?A 550 error means the receiving mail server permanently refused your email, so it won't try again. The extra code after it gives the reason. 5.1.1 means the address doesn't exist, 5.7.1 means it was blocked as spam or by a policy, and 5.7.26 means your domain's SPF or DKIM authentication failed.Email and domains · 14 October 2026Two stacked cardboard boxes, ready for a move, like your email moving to a new providerTutorialHow to change MX records without losing emailLog in to wherever your domain's DNS is managed, delete the old MX records, and add the new ones your email provider gives you with the exact priority numbers. Lower the TTL a day before if you can. New email reaches the new provider within minutes to hours, so keep the old mailboxes open for a few days.Email and domains · 14 October 2026

Want email on your own domain?

Hosteaze hosting plans let you set up mailboxes on your own domain. See what each plan includes.

See hosting plans