{"id":34,"date":"2026-10-22T07:04:56","date_gmt":"2026-10-22T07:04:56","guid":{"rendered":"https:\/\/michaelracle.com.ng\/blog\/?p=34"},"modified":"2026-10-22T07:04:59","modified_gmt":"2026-10-22T07:04:59","slug":"own-domain-hosting-website","status":"publish","type":"post","link":"https:\/\/michaelracle.com.ng\/blog\/2026\/10\/22\/own-domain-hosting-website\/","title":{"rendered":"Who should own my domain, hosting and website accounts?"},"content":{"rendered":"<p class=\"oracle-photo-credit\">Photo: Mateusz Dach \/ Pexels. Illustrative photograph. <a href=\"https:\/\/www.pexels.com\/photo\/computer-set-up-on-a-workspace-450035\/\">Photo source<\/a> \u00b7 <a href=\"https:\/\/www.pexels.com\/license\/\">Pexels licence<\/a><\/p>\n<p>Your business should retain clear ownership and recovery access for the accounts on which its website depends. A developer can manage technical work without becoming the only person who can renew the domain or recover the hosting account. Arrange this before the build starts.<\/p>\n<h2>List the accounts that matter<\/h2>\n<p>Include the domain registrar, hosting, business email, content management system, payment provider and any important third-party service. Record the account owner, recovery method, renewal date and person responsible for payment. Store this information securely rather than in a public project document.<\/p>\n<p>Use business-controlled contact details where practical. Shared passwords create avoidable confusion. Where a service supports separate roles, give collaborators their own access and only the permissions required for the agreed work.<\/p>\n<h2>Agree what handover includes<\/h2>\n<p>Ask for the finished content, agreed source code or export, documentation and a description of recurring charges. Confirm whether any theme, plugin or software licence is transferable. Ownership and licensing are separate questions, so the proposal should address both.<\/p>\n<p>Imagine a site built years ago under a former contractor&#x27;s email address. The homepage may still work, but renewal or recovery becomes difficult when that person is unavailable. Keeping the business in control of the account avoids that dependency.<\/p>\n<h2>Keep recovery practical<\/h2>\n<p>Enable strong authentication where available and retain recovery codes in a secure place. Remove access that is no longer needed after a project or support arrangement ends. Test that an authorised business owner can reach the relevant dashboard without depending on one person&#x27;s device.<\/p>\n<p>My <a href=\"\/solutions\/website-design\">project process<\/a> includes discussing handover responsibilities. Explore <a href=\"\/portfolio\/\">my portfolio<\/a> and <a href=\"\/solutions\/contact\">send your current setup<\/a>, without passwords or recovery codes. Read <a href=\"https:\/\/michaelracle.com.ng\/blog\/2026\/10\/22\/website-running-costs\/\">What ongoing costs should I budget for after launching a website?<\/a> for renewal planning and <a href=\"https:\/\/michaelracle.com.ng\/blog\/2026\/10\/22\/website-backup-restore-test\/\">How do I know whether my website backup actually works?<\/a> for recovery testing.<\/p>\n<p>An attractive website is still a business asset that needs ownership, maintenance and a way back in when something goes wrong. Make those arrangements part of the project scope.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Your business should retain clear ownership and recovery access for the accounts on which its website depends. A developer can manage technical work without becoming the only person who can renew the domain or recover the hosting account. Arrange this before the build starts.<\/p>\n","protected":false},"author":1,"featured_media":19,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-34","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-getting-a-website"],"_links":{"self":[{"href":"https:\/\/michaelracle.com.ng\/blog\/wp-json\/wp\/v2\/posts\/34","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/michaelracle.com.ng\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/michaelracle.com.ng\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/michaelracle.com.ng\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/michaelracle.com.ng\/blog\/wp-json\/wp\/v2\/comments?post=34"}],"version-history":[{"count":2,"href":"https:\/\/michaelracle.com.ng\/blog\/wp-json\/wp\/v2\/posts\/34\/revisions"}],"predecessor-version":[{"id":134,"href":"https:\/\/michaelracle.com.ng\/blog\/wp-json\/wp\/v2\/posts\/34\/revisions\/134"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/michaelracle.com.ng\/blog\/wp-json\/wp\/v2\/media\/19"}],"wp:attachment":[{"href":"https:\/\/michaelracle.com.ng\/blog\/wp-json\/wp\/v2\/media?parent=34"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/michaelracle.com.ng\/blog\/wp-json\/wp\/v2\/categories?post=34"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/michaelracle.com.ng\/blog\/wp-json\/wp\/v2\/tags?post=34"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}