Websites and Tech

TXT Record

Also called Text record

A DNS entry holding plain text, used to prove you control the domain and to publish email authentication policy.

Quick facts: TXT Record

Category
Websites and Tech
Also called
Text record
Level
Intermediate
Affects
Domain verification, email authentication, inbox placement
Where to see it
Your DNS control panel, Google Search Console, SPF and DMARC lookup tools
In this article4
  1. How a TXT record works
  2. Why TXT records matter
  3. Common mistakes with TXT records
  4. Getting TXT records right

How a TXT record works

A TXT record stores a line of plain text in your DNS zone, readable by anyone who looks your domain up. It sends no traffic anywhere and changes nothing about how the site loads. Its whole value is that only somebody with control of the domain could have put the text there, which makes it both a proof of ownership and a place to publish policy that other systems will obey.

Two jobs dominate. The first is verification: Search Console, Meta Business Manager, Microsoft and most email platforms hand you a string to publish so they can confirm the domain is genuinely yours. The second is email authentication — SPF listing which servers may send on your behalf, DKIM publishing the key that signs your messages, and DMARC telling receivers what to do when a message fails those checks.

Why TXT records matter

Without verification you cannot claim your own property inside the tools that report on it, so nobody can see search performance, run ads against the domain or manage a business account properly. Without authentication, mail claiming to be from you is unproven, and receiving providers have grown steadily less tolerant of unproven mail. The symptom is campaigns and even quotes landing in spam for no reason anyone on your side can see.

These records also tend to be requested at the worst possible moment — the morning a campaign is due to launch, by somebody who has no access to DNS and no idea who does. Publishing verification and authentication early, while nothing is urgent, removes an entire category of launch-day delay.

Common mistakes with TXT records

Publishing a second SPF record is the classic. A domain may carry only one, so adding a separate record for a new email tool invalidates the pair of them, and mail that had been arriving cleanly starts failing checks everywhere. The correct move is always to merge the new sender into the record that already exists.

Next is deleting old verification strings during a tidy-up. They look like meaningless noise, and removing one silently un-verifies a Search Console property or a business account, taking someone’s access with it. Third is the host name: DKIM and DMARC belong on specific names within the zone, not on the bare domain, and a record pasted at the root is present, valid-looking and never consulted by anything.

Getting TXT records right

Keep a note against every record saying what it verifies and who asked for it, so the next person to tidy the zone is making an informed decision rather than a guess. When you add a sending tool, edit the existing SPF entry instead of creating another one. Start DMARC in a monitoring mode and actually read the reports before asking receivers to reject anything, or the first thing you block will be your own invoices.

Look the record up from outside your network after saving it, because control panels sometimes add quotation marks or split long values in ways that alter the string. If authentication is new to you, treat it as a small project of its own rather than a checkbox. The payoff is better email deliverability, and it is one of the few technical fixes whose effect on marketing shows up quickly.

Do and do not

Do

  • Label each record with what it verifies
  • Merge new senders into the existing SPF record
  • Start DMARC in monitoring mode and read reports

Do not

  • Publish a second SPF record for a new tool
  • Delete verification strings during a routine tidy-up
  • Paste DKIM or DMARC onto the bare domain

Questions people ask about this

How many TXT records can a domain have?

As many as you need, and most zones accumulate several over time for different platforms. The important exception is SPF: a domain may publish only one, and a second invalidates both. Everything else — verification strings from different services, DMARC policy, DKIM keys on their own host names — can sit alongside each other without conflict.

Is it safe to delete old TXT records?

Only when you know what each one does. Verification strings look like random text but often hold a platform property open, and removing one can un-verify an account and lock a colleague out. Before deleting, check which service issued it and whether that service is still in use, then remove it deliberately rather than as housekeeping.

Why is my domain still not verifying after I added the record?

Usually one of three things. The record was saved on the wrong host name, because the panel appended your domain to a value that already contained it. The old answer is still cached and the timer has not expired. Or the panel added quotation marks that changed the string. Look the record up from outside your own network to see what the world actually receives.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.