Yes. A domain can have multiple TXT records, including different TXT values at the same hostname. An email policy and a website-verification token can be separate records. The important exception is the service’s own rules: do not publish competing SPF policies for the same hostname. Keep unrelated values separate, use the exact host and value requested, and check existing records before adding or replacing anything.
Before you begin
- Identify the service hosting your active nameservers before editing DNS.
- Copy the existing records and note each record’s purpose.
- Match both the requested hostname and the complete TXT value.
- Add independent verification values separately; do not combine unrelated tokens.
- Check for an existing SPF policy before changing email authorisation.
1. TXT is a record type, not one slot for the whole domain
Seeing an existing TXT row does not mean the domain has used up its only TXT setting. DNS supports sets of records with the same name and type but different data. Different services can therefore look for their own values at the same hostname. The receiving service still decides which text it recognises and what that text means.
Keep three pieces of information together: the hostname, the record type and the value. Two rows marked TXT may serve different purposes, while two records under different hostnames are separate settings even if their values look similar. Start with the provider’s current instructions rather than choosing a row just because its type matches.
2. A worked example: website verification alongside email
Imagine your email service already uses a TXT policy at the domain root. A separate website service now asks for a root TXT verification token. These are different instructions. Subject to their actual requirements, add the new verification value as another TXT record and leave the existing email policy intact. Do not paste the new token onto the end of the email policy.
The following list is hypothetical. The descriptions stand in for provider-supplied values; they are not text to copy into DNS. It shows how the same domain can hold several independent settings without turning them into one long record.
| Host | Purpose of the TXT value | How to treat it |
|---|---|---|
| @ (root) | Existing email SPF policy | Maintain one valid SPF policy for this hostname |
| @ (root) | Website service’s verification token | Keep as a separate value from the SPF policy |
| @ (root) | Another service’s verification token | Keep separate and record which service needs it |
| Provider-specified subdomain | A service-specific policy or token | Use the exact host requested, not automatically @ |
3. SPF has an important rule of its own
SPF is commonly published as TXT, but that does not mean every TXT value is an SPF policy. Its version marker is v=spf1. The SPF standard prohibits multiple records that would make the check select more than one SPF policy for the same name. An unrelated verification token is not a second SPF policy merely because it is also TXT.
If another email sender asks for SPF authorisation, inspect the current policy and arrange one valid policy covering the intended senders. Do not simply add another competing v=spf1 row. Combining senders also needs syntax and DNS-lookup-limit checks, so ask your email administrator or provider to validate the result if it is unclear.
4. Check the host and any CNAME before adding a row
In the NameUK DNS table, @ refers to the domain root. A provider may instead request a particular subdomain. Copy that host carefully and check how the form displays the full name. A token at the root does not answer a request for a different hostname, and adding the domain twice can put a record in the wrong place.
An ordinary CNAME alias cannot coexist with an ordinary TXT record at the same name. If the requested host already has a CNAME, do not delete a working alias to force the new instruction through. Ask the service for the appropriate verification method or clarify the intended hostname. This is a conflict at that exact name, not a ban on TXT records elsewhere in the domain.
5. Add the required value through the active DNS host
With NameUK managed nameservers, open the domain’s own dashboard page and its DNS records table. Keep a copy of the current records, choose Add record, select TXT and enter the host and value supplied by the service. Review the details before saving, then check the confirmed record. If the domain uses external nameservers, make the change at that active DNS host instead.
Keep independent verification tokens in separate records. A long TXT record can contain multiple character strings internally, but that is a different concept from publishing unrelated TXT values. Follow the form and service instructions for a long value rather than splitting a token into extra rows or inventing quotation marks. If it is rejected, resolve the format with support before changing existing records.
Sources: RFC 1035: TXT record format ↗
6. Check the result and keep useful records in place
Compare the saved host and complete value with the service’s instructions. Check that the public TXT answer includes the intended value, then use that service’s verification check. Cached DNS answers can delay what a checker sees, so a fresh dashboard row alone is not the whole result. Keep a note of the change time and allow the relevant caches to update.
Do not remove an existing token simply because another service has verified successfully. Record which service and account each value belongs to, and confirm its current retention requirements before removing it. If you changed an email policy, test the affected senders too. TXT verification does not create a mailbox, publish a website or automatically put pages in a search index.
7. Choose domain control as well as the registration price
Register .co.uk for £9.99 for one year, with annual renewal currently £9.99. Or choose a new three-year .co.uk registration for £25.99. Check the selected name and term before payment. Future renewal prices can change.
If you are buying a domain for a website and business email, you can plan those connections separately from registration. For buyers who want visible renewal pricing and a dashboard for managed DNS records, we recommend considering NameUK’s .co.uk registration. This is our own recommendation for those needs. Your chosen website and email providers still supply their own services and required DNS values.
Keep the annual renewal in your budget, and choose an initial term that fits your plans. A lower registration cost does not remove the need to maintain accurate records and secure account access. Start with an available name, confirm successful registration, then connect only the services you need.
This is NameUK’s own practical DNS guide. The worked record list is illustrative and contains no working verification token or ready-to-publish email policy. Our service recommendation is based on the stated needs, not an independent market ranking.
Further readingRFC 2181: DNS record sets and aliases ↗RFC 7208: SPF records and record selection ↗RFC 1035: TXT record format ↗Extension rules and provider processes can change. Check the current registrar instructions before a registration, transfer or renewal.
Low-cost registration. Affordable UK renewals.
Register .co.uk for £9.99 for one year, with annual renewal currently £9.99. Or choose a new three-year .co.uk registration for £25.99. Check the selected name and term before payment. Future renewal prices can change.