Many independent websites are held together by accounts opened months or years apart. The domain sits with one registrar, DNS somewhere else, deployment on Vercel and email inside another provider. This arrangement feels simple until a renewal fails or the person who set it up is unavailable.
A website ownership record gives the operator one place to understand the chain without storing passwords in an unsafe document. The same distinction becomes decisive in an acquisition: receiving a repository does not mean receiving control.
Record the domain separately from DNS
Write down the registrar, registrant contact, recovery method, renewal date and payment owner. Then record the active nameservers and DNS provider separately. These may be the same company, but they perform different jobs.
Add the website, email, verification and application records that matter. You need enough detail to recognise an unexpected change. There is little value in copying the entire zone file into another document.
Connect hosting to source control
Identify the repository and branch that produce the live site. Record the Vercel or hosting project, its owners and the account paying for it. Confirm that more than one trusted recovery path exists.
If the site can only be deployed from one person's laptop, it is not operationally ready.
Include the services people forget
Analytics, Search Console, email sending, form delivery, affiliate accounts, monitoring and image storage can all matter to the business. Record the account owner and purpose of each service. The operating value becomes clearer when real search data arrives, as in the field note on 3,250 impressions and four clicks.
Do not include API keys or passwords. A useful ownership record points to the secure vault or provider process used to access them.
Review it when something changes
Update the record after a domain transfer, hosting migration, staff change or new publishing integration. Add a short quarterly review for renewals, inactive users and recovery details.
I now create this record while setting up a site, because reconstructing it during an outage is miserable. It also means another person can understand the website without inheriting a trail of unexplained personal accounts. Build the record in the Website Ownership Mapper. For a sale rather than routine operations, use the more demanding SaaS Transfer Control Register.