Quick answer
How do I verify domain ownership with a TXT record?
To verify domain ownership with a TXT record on a Shroudname domain, copy the token the service gives you, open the DNS tab, click Add record, choose TXT, enter @ as the name, paste the token as the value, click Add and then Save changes. Back at the service, click Verify; Google allows up to 2 or 3 days.
In brief
- What it proves: that whoever asks controls the domain's DNS, which only the holder can change.
- Where: a TXT record, usually on @, sometimes on a sub-name such as _atproto or _acme-challenge.
- Several at once: a domain can hold many TXT records on @; only SPF must be unique.
- Paste as given: no quotes, no extra spaces; long values are split for you.
- Keep it: Google says removing the record can cost the verification.
What are the steps, with Google Search Console as the example?
Five steps. Other services follow the same pattern; only the token and sometimes the name change.
Get the token
In Google Search Console, add a property of type Domain and choose TXT. Copy the value, which starts with google-site-verification=.
Open the DNS tab
In My domains, click Manage on the domain, then DNS. The domain must use Shroudname's nameservers for the record to be served.
Click Add record and choose TXT
In Name, type @ for the domain itself. In Text, paste the token as given, without quotes. Click Add.
Click Save changes
The new row shows New until saved; DNS records saved confirms it. Check it with dig TXT example.com from a terminal.
Click Verify at the service
Return to Search Console and verify. If it fails, wait and retry; Google notes a manual record can take up to two or three days to be seen.
Which services verify a domain by TXT, and where?
Most services put the token on @; a few use a dedicated sub-name so the token does not mix with other records.
| Service | Name | Value starts with |
|---|---|---|
| Google Search Console (Domain property) | @ | google-site-verification= |
| Proton Mail custom domain | @ | protonmail-verification= |
| Bluesky handle on your domain | _atproto | did= |
| Let's Encrypt DNS-01 challenge | _acme-challenge | A token set by the ACME client |
| SPF (not a verification, but a TXT) | @ | v=spf1 |
Why does a TXT record prove ownership?
Only someone who can edit the domain's zone can publish a chosen string in it, and the zone can only be changed through the registrar account or the DNS provider the holder picked. RFC 1035 defines TXT as free text attached to a name; services use it to ask for a random token and then look it up.
On a Shroudname domain, that control sits behind the account number, a password and two-factor codes if set. Anyone who can add a TXT record can also verify the domain with Google or point it elsewhere, which is why securing the account matters as much as the record.
The same mechanism serves mail providers: the verification row of the Proton Mail template is one, as shown in how to set up a private email on your own domain. Once you know how to verify domain ownership with a TXT record, every such request reads the same.
Why does verification fail, and how do you fix it?
Four causes cover nearly every failure: the record is on the wrong name, the value was changed in copying, the zone is not served, or the service checked too early.
- Wrong name: @ means the domain itself; typing the full domain in Name creates example.com.example.com.
- Changed value: quotes added, a space at the end, or a token cut in half. Paste again from the service.
- Zone not served: if the DNS tab says This domain uses other nameservers, add the record at that provider instead.
- Too early: wait, check with dig TXT example.com, then click Verify again.
A host that also needs the site to point somewhere should read how to point a domain to a server IP; both records live in the same table.
What is the best practice for TXT verification records in 2026?
Keep each token as long as the service uses it, note what each one is for, and remove tokens of services you have left. A zone full of unexplained TXT records makes it hard to tell which ones still matter. The DNS tab filters by type with the TXT button, which lists them all at once.
A related record limits who may issue certificates for the domain; it is covered in how to add a CAA record to a domain. The overall flow of an account, a domain and its DNS is on how it works.
According to Shroudname's survey of 12 November 2026, GoDaddy renews a .com at $22.99 against $12.49/year at Shroudname, where DNS hosting and its TXT records are free. Once you know how to verify domain ownership with a TXT record, each new service takes one more row in the table.
Frequently asked questions
Can I have several TXT records on the same domain?
Yes. A domain can hold many TXT records on @ side by side; only the SPF record must be unique.
Should I put quotes around the value?
No. Paste the value as given, without quotes; the DNS editor handles quoting and splits long values automatically.
How long does TXT verification take?
The record is usually visible within minutes of Save changes on a new name. Google notes it can take up to two or three days in some cases.
Can I delete the TXT record after verifying?
Google advises against it: the service may check again later and remove the verification if the record is gone.
Does a TXT record reveal anything about me?
Only the token and the service it belongs to. TXT records are public, so avoid putting personal data in them.
Verdict
- Token, TXT on @, Save changes, Verify: the whole check takes a minute in the DNS tab.
- Paste as given and leave it in place: most failures come from a changed value, and many services re-check later.
Sources (3)
- Verify your site ownership — Google Search Console Help (read 2026-11-16)
- RFC 1035: Domain Names, Implementation and Specification (TXT RDATA) — IETF (read 2026-11-16)
- RFC 8555: Automatic Certificate Management Environment (ACME), DNS challenge — IETF (read 2026-11-16)
Add your TXT record
Free DNS hosting with TXT, A, MX, CAA and more, edited from the DNS tab.