Buy Domain Name UK

Buying a domain?Agree who controls it.

A designer can arrange the purchase without becoming the person who should control the registration. Agree the records, access and renewal responsibilities before anyone checks out.

Build my buying agreement

One purchase, several responsibilities

A designer orders a domain for a small business.

The business needs the appropriate registrant record, an accessible registration email and a clear renewal arrangement.

The designer may manage DNS without being the only person able to recover the account.

Illustrative arrangement, not advice about a particular contract or proof of domain availability.

The payer and registrant may differ

Who pays the invoice is only one question. Check which person or organisation will be recorded as the registrant, who has account access and who can deal with renewals. Ask the registrar how it supports your chosen arrangement instead of sharing a password by default.

Agree the purchase, not just the price

Use these checks when a colleague, developer or agency is buying on your behalf. They also help a buyer who will manage everything directly.

Name the intended registrant

Confirm the appropriate person or organisation with the buyer and registrar. A contact person, billing contact and registrant can serve different roles. Do not assume a designer's account name or the invoice automatically establishes the intended registration record.

For .uk registrations, Nominet's terms require correct contact information. If you are unsure which identity should be used, resolve it before the order rather than selecting a convenient placeholder.

Keep a usable recovery route

Agree an email address that the intended controller can access. Relying only on an address at the newly purchased domain can make recovery harder if its email service fails. Ask about delegated access or separate permissions where the registrar offers them.

Use a unique password and available account protections. Do not put passwords, recovery codes or payment information into a shared planning document.

Separate registration from DNS work

The person maintaining website or mail records does not necessarily need to control every registration or billing function. Ask the provider which permissions are available and document who may approve a nameserver change.

If DNS is already in use, record website, mail and verification records before moving it. A nameserver change can affect more than the website.

Put renewals in somebody's diary

Specify who receives reminders, maintains payment details and authorises the renewal. If an agency pays first and invoices later, agree what happens when the relationship ends or an invoice is disputed.

Record the registration period and exact domain ending. Ask for renewal terms separately from the introductory registration price and any management fee.

Leave room for a handover

Agree how the intended controller will obtain the domain record, account access, DNS settings and renewal information if a supplier changes. The actual registrar or registrant-change procedure depends on the provider and ending.

Keep an order confirmation and a responsibility note that both parties can find. A checklist records what you agreed; it cannot verify the registry record or settle a contractual dispute.

Build a domain purchase responsibility list

Choose the nearest arrangement. The output gives the buyer and helper specific points to agree; it does not access an account or check a registration.

Choose an answer to each question. Not sure is a useful answer.

What this list does

This planner records responsibilities and questions. It does not check domain availability, legal rights, registrar permissions or the actual registrant record. No order or account change is made.

No accounts, analytics, storage or submissions. Your answers stay in this page until you clear or reload it. Download a copy to keep it.

Clear up the common assumptions

A convenient purchasing arrangement should still leave an understandable record of who does what.

Does paying the invoice make me the registrant?

Do not rely on the payment alone. Check the identity submitted to the registrar and the resulting registration record. Resolve differences through the registrar's procedure.

Can the designer still look after the website?

Often there are ways to manage website or DNS tasks separately from registration and billing, but permissions differ by provider. Ask which supported access arrangement fits your relationship.

Does this list verify that I control the domain?

No. It helps you state responsibilities before purchase. Check actual account access and registration details with the registrar; use suitable advice for any contractual or rights dispute.

Agree it while everyone is available

A short responsibility note before the order is easier to use than assumptions after a supplier or staff member leaves. Keep the exact domain, intended registrant, accessible email and renewal contact together.

Build my buying agreement

Sources and scope

Guide checked 2 November 2026. Official documentation supports the distinctions above; use the terms and instructions for your actual provider. No provider ranking, live price or search-inclusion promise.

This planner records responsibilities and questions. It does not check domain availability, legal rights, registrar permissions or the actual registrant record. No order or account change is made. External links have their own privacy terms.