Domain forwarding sends a visitor from your domain to another web address. An ordinary redirect changes the browser's address bar to the destination. It does not copy the destination website into your hosting account or change where your email is delivered.
IN THIS ARTICLE
01 Prepare the destination
Open the destination URL directly and confirm it works over HTTPS. Decide whether you need to redirect the root domain, www, both, or another source offered by the screen. If a path is available, decide whether the rule covers a particular path or the whole site. Avoid creating a loop where the destination redirects back to the source.
02 Add the forwarder
- Open the domain in the client area and select Domain Forwarders. Some configurations also link to forwarding from DNS Manager.
- Read any DNS connection message. Required nameservers or forwarding records must point to the enabled forwarding service.
- Select Add Forwarder.
- Choose the source, redirect type and any supported path.
- Enter the complete Destination URL, including
https://. - Save the rule and wait for any deployment or certificate work shown by the service.
Should I use a permanent or temporary website redirect?
A 301 indicates a permanent move; a 302 is appropriate for a temporary destination. The screen may also offer 303, 307 or 308 for workflows with specific method-handling requirements. For an ordinary website move, follow your site's migration plan. Test temporary behaviour before making a permanent rule where possible, since browsers and other systems can cache permanent redirects.
03 Test all intended addresses
Try the root domain and www, over HTTP and HTTPS, and test an important path. HTTPS requires a working certificate on the source before a browser can receive the redirect. A correct destination certificate alone does not solve an HTTPS error at the source.
If the page asks you to use different nameservers, review the full DNS zone first. A nameserver change also affects mail and other subdomains. Do not replace delegation solely to fix a redirect without preserving those records.
04 Edit or remove
Use the existing row's Edit or Delete action. Confirm the effect before removing a live rule. If changes appear ignored, test with a fresh browser session and inspect the actual HTTP response alongside DNS. A cached redirect can continue to send that browser to an old destination even after the live rule changes.