Website Hosting and Domain Ownership Questions for Contractors

Separate the domain, hosting, website and email

A domain name is the address used to reach a website; it is distinct from the hosting service and the files or platform that create the site. Email may be connected to the domain but managed by another provider. A single invoice or vendor relationship can hide these separate parts, so list them individually.

ICANN’s registrant guidance explains the registrant’s role and the difference between registering a domain and having a website. Ask the provider to name the registrar, registrant of record, hosting company, website platform and email provider. Do not assume one login controls all of them.

Confirm who is listed as the registrant

The business should verify the registrant information through its registrar account or confirmation records. If a founder’s personal information or a former vendor is listed, understand the transfer and update process before a dispute or renewal problem occurs. Changes to registration details can have consequences, so follow the registrar’s current instructions.

Avoid collecting the domain password in an email or spreadsheet shared broadly. Use the registrar’s proper role-based access or transfer process, keep recovery options controlled by the authorized owner, and remove access when a vendor’s role ends. Use multifactor authentication where available.

Write down renewal and recovery responsibilities

Record the expiration date, renewal setting, billing owner and email address that receives notices. ICANN tells registrants to keep contact details current and renew through the registrar before expiration to maintain services. Assign a backup who can see renewal notices if the primary owner is unavailable.

Document how to recover the registrar account without placing passwords in a public project or marketing folder. Keep payment information within the registrar’s secure account. If billing responsibility changes, confirm that the new payer receives invoices and can resolve a failed renewal promptly.

Ask what hosting and maintenance actually include

Clarify who performs backups, software or platform updates, security response, form monitoring and restoration. Ask how often backups happen, how long they are retained and whether the business can retrieve its content and images. A phrase like ‘hosting included’ may not answer whether custom development or unlimited redesign is part of the service.

For Parallax’s Foundation offer, the managed website and hosting are part of the $299 monthly service within the agreed template scope. Domain, communication, phone, email, AI and third-party usage charges may be separate according to the agreement. Confirm the specific account and fees before work begins.

Review access before changing providers

Before ending a vendor relationship, inventory domain, DNS, host, content, forms, analytics, tag manager, CRM, email and image access. Identify which assets are owned by the contractor, what is licensed and what can be exported. A clear transition checklist avoids a last-minute scramble when a phone number, site form or tracking code is unavailable.

Do not make a DNS change until the new site and email routing are ready. Incorrect records can interrupt the website or business email. If a provider is changing hosting without changing URLs, follow a controlled move and test page availability, HTTPS, forms and analytics after cutover.

Put ownership and service boundaries in writing

A simple vendor agreement or onboarding record should say who owns the domain, who pays the registrar, which party controls hosting and what happens to content and access when service ends. Include a contact for emergencies, a notice process for renewal and a practical export or transition path.

Ask whether the provider can transfer the domain or deliver a site backup, what fees or limitations apply, and how long handoff takes. Keep the answer specific to the technology being used. Do not rely on an informal promise that ‘everything can be moved’ without confirming what the system actually allows.

Use this quick ownership review

• The correct business or approved owner is named as domain registrant.
• At least one authorized business owner can access the registrar and recovery method.
• Renewal date, billing contact and backup contact are recorded.
• Hosting, website platform, email and domain are listed separately.
• The provider explains backups, export, restoration and exit steps.
• Analytics, CRM, forms and media accounts have clear business access.
• Vendor permissions are limited to the work required and reviewed at offboarding.

A practical asset register

Keep a small asset register with service name, account owner, billing contact, recovery method location, renewal date, provider support path and the team member responsible for review. Do not put passwords or recovery codes in the document. The register should tell an authorized owner where the secure account is and what happens if the account owner leaves.

Include the registrar, DNS host, web host, email service, site builder, CRM, analytics property, tag manager, phone provider and any paid image or font license. Mark whether the business or a vendor pays for each item. This helps the owner spot dependencies before a redesign or contract change creates pressure to transfer access quickly.

Questions to ask before signing a managed website agreement

• Who is the domain registrant and who pays the renewal?
• Which site content and design assets can the business export?
• What does routine maintenance include, and what is separately scoped?
• How are backups stored and how would restoration be requested?
• What happens to the site and CRM access if service ends?
• Which metered communication, AI, domain or third-party fees can occur?
• How do we grant and later remove vendor access safely?