Your business should normally control its domain registration, primary hosting or website platform account, recovery routes and access to agreed source files. Give your website partner appropriately scoped access rather than making them the only route to renewal, recovery or migration. This website ownership checklist turns that recommendation into decisions you can record before approving a proposal.
1. Separate account control from legal ownership
The registrar manages your domain registration. DNS, the domain name system, directs visitors and email towards the right services. Hosting stores and runs the website; a hosted platform bundles this with website tools. These services may share a provider, but they remain separate responsibilities. A working website login does not prove control of any of them.
Account control is an operational safeguard, not proof that you legally own commissioned code or design. Intellectual-property rights depend on the agreement and applicable law. Record four things separately: who controls accounts, what rights the business receives, who pays recurring charges and what can move elsewhere. Resolve unclear assignment or licensing terms before signing, with legal advice where needed.
2. Record each account and the evidence of control
Copy these linked tables into your procurement document. Replace role suggestions with named people and actual dates. Keep account addresses and identifiers in the register, but store passwords and recovery codes separately. Use one row per service, including separate rows for email, backups and paid extensions where relevant.
| Service / account ID | Business custodian | Partner permissions | Payer | Renewal date | Recovery route |
|---|---|---|---|---|---|
| Domain / [ID] | [Director] | Domain configuration only | [Business] | [Date] | Business contact and registrar recovery |
| DNS / [ID] | [Operations lead] | Required record changes | [Business or included] | [Date or not applicable] | Business user and secure recovery codes |
| Hosting or platform / [ID] | [Operations lead] | Deployment and maintenance | [Business or reseller] | [Date] | Business owner login and provider support |
| Source repository / [ID] | [Director] | Development access | [Business or included] | [Date or not applicable] | Business organisation owner and recovery |
| Billing / [profile ID] | [Finance manager] | Invoice access if needed | [Named payer] | [Linked service dates] | Business finance contact |
| Recovery vault / [ID] | [Director plus deputy] | No routine access | [Business] | [Date] | Documented independent emergency route |
| Service | Agreed deliverables | Proof of business control |
|---|---|---|
| Domain | Registration details, expiry date, transfer procedure | Check registrant details where applicable; open renewal and transfer settings |
| DNS | Current record inventory | View records and manage delegated access |
| Hosting or platform | Subscription details, backups, export procedure | Open owner settings and retrieve agreed exports |
| Source repository | Agreed code, history, assets and deployment notes | Retrieve files and manage repository membership |
| Billing | Invoices, payment method responsibility, failure escalation | Business receives notices and can update billing |
| Recovery vault | Recovery procedure and custodian list | Authorised business deputy can retrieve recovery material |
Do not accept an “administrator” label as proof of ultimate control. Cloudflare, for example, distinguishes Administrator, Super Administrator and Billing roles. Its Administrator role cannot manage members or the billing profile; Super Administrators have broader powers. [1] Ask a business representative to demonstrate the required actions, and avoid granting unnecessary top-level permissions to the partner.

3. Assign every renewal and payment failure
Name both the payer and the accountable business custodian. They may be different people: finance pays while operations checks that renewal succeeded. Record the renewal date, notice recipients, failed-payment escalation and backup payment procedure. Automatic renewal reduces administration, but it does not remove responsibility for expired cards, missed invoices or changed contact details.
Direct business billing usually makes critical subscriptions easier to control. Agency-resold hosting can still be sensible when it includes useful support. Before choosing it, record storage, backups, support, renewal notices, export access and migration assistance. Identify subscriptions that require replacement after termination and how replacement costs will be established. Paying an agency invoice alone does not establish account control.
4. Keep recovery independent of the partner
Use individual logins and multi-factor authentication, which adds a second check beyond a password. Give the partner only the permissions needed for its work. Name a business deputy so holidays, departures or illness do not create a single point of failure. Where a provider lacks delegated access, agree a supported arrangement rather than routinely sharing passwords.
Keep business-user recovery material in a business-controlled secure vault. Establish an emergency route that does not rely solely on email behind the affected domain or hosting. Cloudflare provides single-use backup codes; generating replacements invalidates previous codes. [2] Check the selected provider’s process and ensure the business deputy knows where current material is stored, without exposing it in the procurement register.
5. Specify source files, data and continuing licences
Replace “you own everything” with a deliverables schedule. It should distinguish the files you receive from the rights you receive, and identify anything that remains with the agency or provider. Add this schedule to your proposal alongside the requirements in Write a website project brief that makes estimates useful.
- Bespoke work: editable source, custom designs, agreed repository history and the rights granted or assigned.
- Business assets: supplied copy, photographs, product data and editable originals created for the project.
- Open-source components: names, versions and applicable licences; these are not exclusive business property.
- Commercial assets: themes, plugins, fonts and stock media, including licence holder, permitted use and replacement requirements.
- Reusable agency tools: exclusions, continuing usage rights, dependencies and available alternatives.
- Hosted services: exportable data, unavailable source code and subscriptions needed to continue operating.
Request dependency versions, configuration notes and build or deployment instructions. Transfer live credentials through a separate secure process, not inside the source package. For WordPress, a typical full restoration needs both files and the database; downloading the website directory alone misses the database. [3] WordPress itself uses GPLv2 or later, so account control does not make every component exclusively yours. [4]

6. Agree an exit route, not just an ownership promise
Changing an account owner, transferring a domain and moving a website to another platform are different jobs. Specify which exit the agreement supports. Shopify’s duplication guidance, for example, describes exports and theme downloads but also limits: visitor traffic data and saved custom reports do not transfer, while apps and settings need additional work. [5] Platform control does not guarantee complete portability.
Cloudflare’s Registrar account-transfer guidance says both accounts must confirm the move. Registration contact details move unchanged, but other configuration does not. [6] This is a provider-specific example, not a universal registrar rule. Require a separate continuity plan for DNS, email and hosting rather than assuming that moving the domain moves the whole website.
7. Test whether another partner could take over
Put these acceptance checks in the proposal before appointment, then perform them at the agreed milestone. An authorised replacement partner can help with technical checks. Use a separate test environment where appropriate, and agree how personal data will be protected. The goal is demonstrable control, not an unnecessary live-site migration.
- Open owner, member-management and billing settings using business-controlled access.
- Confirm the business receives renewal notices and can use the documented recovery route.
- Retrieve the agreed source, files, assets and data without depending solely on the outgoing partner.
- Restore or redeploy in a separate test environment where applicable; otherwise verify the supported export and takeover route.
- Demonstrate that partner access can be replaced or removed while business access remains intact.
Should the agency register our domain?
It can assist, but the business should normally control the registrar account and recovery details. Check the registrant information where applicable. If registration sits inside an agency account, require a documented transfer route and clear renewal responsibility before proceeding.
Does paying for development mean we own the source code?
Do not assume so. Your agreement and applicable law determine the rights you receive. Specify bespoke deliverables, exclusions, usage rights and any assignment conditions. Commercial licences and hosted services need separate treatment.
Is agency-managed hosting always a lock-in risk?
No. It can simplify support, but you need clear service terms, accessible exports and a workable exit. Understand which account stays with the agency, what can move and which subscriptions you must replace.
Before approving the proposal, complete both responsibility tables, name a business deputy and attach the deliverables and exit terms. Ask the partner to resolve every unclear row. For ongoing procedures after launch, use Keep control of the website after launch. That turns these procurement decisions into a practical support and handover routine.
Sources & further reading
Use the original guidance when checking details or planning implementation.
This research-assisted guide uses the primary sources linked above. Examples are illustrative unless explicitly identified otherwise. Check original documentation when implementing changes.



