Separate the domain from the hosting

Your domain is the name people use to reach your website. Hosting provides the server and application that respond to those visits. These services can be supplied by different companies. Buying new hosting does not mean you must buy the same domain again, and moving your website does not automatically transfer the domain registration.

Choose the existing-domain option

When you already own the name, choose use my existing domain at checkout. That should add no new registration charge. You may need to change the website DNS records or nameservers after the new hosting is ready. Keep access to the current registrar account and make sure recovery and renewal emails go to an address your business controls.

Know what an availability result means

A registrar checks whether a name can be registered. An unavailable result may mean the domain belongs to you or someone else, or that the registry restricts it. A failed check does not mean the name is available. If a provider cannot confirm the result, wait for a verified answer instead of treating an error as permission to purchase.

Treat transfer as a separate request

A domain transfer moves registration management between registrars. It differs from moving website files or pointing DNS to another server. Transfers may have eligibility rules, authorisation requirements and a separate price. Ask what the transfer includes and how renewals will be handled before paying. Do not select new registration when the task is an existing-domain transfer.

Check the order summary

The summary should make the intention clear: hosting with an existing domain, or hosting plus a new registration request. For a new name, review the registration term and price. An availability check is a point-in-time result. The name is yours only after the registrar completes registration; payment alone is not confirmation that registration succeeded.

Keep the records together

Store your registrar details, renewal date, DNS provider and hosting account in a business-controlled record. This helps a new developer or team member make changes without guessing. If a website move is planned, list email and third-party DNS dependencies as well. Contact WebFulHost before checkout if you are unsure which domain option matches your situation.

Ask WebFulHost about your website or browse the knowledge base.

Choose a safe DNS change window

Before changing nameservers, compare the current and destination DNS zones. Record the mail provider’s MX records and required authentication entries, plus verification records used by other business services. Confirm which records the hosting team will copy and who will validate email after the switch.

Check the website from a customer’s perspective

After DNS changes, test the main domain, the www version, HTTPS, an important landing page and a form submission. Different networks can see the change at different times. Record the actual result and investigate the exact failing address instead of purchasing the domain again.

For the next steps, browse the hosting knowledgebase and compare current plan resources and billing terms.