Topic · DNS & Infrastructure
DNS TXT verification
DNS TXT verification is an ownership or configuration check using a token placed in a domain’s DNS TXT record.
How it works
A third-party service queries a specified owner name and compares the answer with its issued verification value.
What can go wrong
Publishing tokens at the wrong name or leaving stale privileged tokens can delay setup or increase takeover risk.
What to check or do
Verify the exact required hostname, wait for DNS caches and remove old verification artifacts when permitted.
How to investigate DNS TXT verification
- Signal to investigate
- A platform reports ownership verification failure after a token is pasted into a TXT record.
- Evidence to collect
- Query the exact owner name and full TXT value; check quoting, whitespace, multiple segments and which domain the platform verifies.
- Common wrong conclusion
- Putting the right token at the root zone does not satisfy a service asking for a subdomain-specific owner name.
How to interpret the evidence
DNS dashboards display owner names differently, sometimes appending the zone automatically. A copied full FQDN can accidentally create a doubled suffix.
What to change and how to verify it
Use the exact provider instructions, verify the public authoritative result, and remove obsolete tokens after their owner-specific lifecycle ends.
Put this into practice
Run a focused check, then explore protection if your domain needs it.