Prepare before changing DNS
Know who owns the domain, where its DNS is managed and which service hosts business email. Record the existing website records before changing them. Build and review the new website privately while the existing site remains available.
Do not share registrar passwords, transfer codes or private registrant information in public docs, screenshots or ordinary support messages. Use the secure account and domain controls.
Connect an existing domain
- Open the intended website’s Domains area.
- Choose the existing-domain flow and enter the exact domain.
- Complete the displayed TXT ownership verification.
- Review and approve the certificate request when prompted.
- Add the exact validation and website-routing records shown for that domain.
- Prepare the release for the verified address and review the final configuration.
- Approve publication and verify the public HTTPS result.
Ownership verification alone does not move the website or change email. Certificate validation and website routing are separate steps. Do not invent DNS targets from a sample article; copy the values shown for your own project.
Protect email and unrelated records
Do not delete MX, SPF, DKIM, DMARC or other unrelated records during a website cutover. Follow the exact approved record changes. Avoid changing nameservers unless the reviewed plan specifically requires it and you understand the consequences for all domain services.
Apex/root-domain routing can differ from a www subdomain. Use the displayed ALIAS, ANAME or CNAME instructions appropriate to the domain and DNS provider. Do not create an apex CNAME simply because www uses one.
Register a new domain
Where registration is available, use the live availability and price lookup, review the registration and renewal quotes, supply the required registrant details securely, and approve the exact purchase. Payment alone does not reserve the domain. Wait for the registrar outcome and follow any verification instructions.
The current implemented registration flow supports standard .com, .net and .org outcomes when available. Premium or unsupported domains may be unavailable. The public starting price is not a universal quote for every domain or renewal.
Renewals and transfers
Review the renewal method, annual price cap and expiry of any saved authorization. A provider price above the approved cap or a payment requiring authentication can require another decision. A hosting cancellation does not itself cancel domain ownership or define its renewal outcome.
For a transfer, the owner must use the supported domain controls and observe registrar restrictions. Unlocking or revealing an authorization code is not a completed transfer; the receiving registrar must finish the process. Keep the code private.
Change the domain on a live site carefully
Check connected forms and proof experiences as well as the website. Connections may be bound to the old origin and require approval for the new one. Review matching www behavior and any additional alias limits in your actual plan. Do not assume every desired hostname is ready merely because it was entered.
Verify the outcome
Open the exact public HTTPS address, check the expected content, test relevant redirects and confirm the certificate is valid. DNS propagation and certificate issuance can take time. If an operation is pending or unknown, retain its reference and let support reconcile the provider result rather than repeatedly paying or changing records.