Define the destination URL
Choose a stable HTTPS destination. Decide whether source paths should be retained or everything should land on the homepage. A permanent redirect may suit a lasting move. The source also needs HTTPS so direct secure visits can redirect without a certificate error.
Avoid loops and unnecessary hops
Check that the destination does not redirect back, creating a loop. Keep the route short and test the apex, www and an actual path. Website redirects do not move email: MX and mailboxes remain separate.
Your practical checklist
- Choose one HTTPS destination.
- Decide how paths behave.
- Test loops and extra hops.
- Review email separately.
A useful question
Is CNAME enough for forwarding?
No. CNAME is a DNS alias. A web service must perform the actual redirect.
Ready to check your name? Start with the exact domain, then compare alternatives. Find a domain →
Sources & further reading
Original guide by chname.ch editorial. Archive dates organise this library; this guide was created and reviewed on . Provider and registry instructions take precedence when requirements change.