Domain forwarding, or domain forwarding, is a service that directs visitors from one domain name to another web address. For example, typing old-example.it may redirect the visitor to example.it. Forwarding can be set up at the registrar, DNS provider, hosting service, or CDN and can use an HTTP redirect or browser-side forwarding techniques. These methods are not equivalent. A DNS record alone does not communicate a new URL to the browser; DNS translates names into network information, while redirects are applied by the server or a service that receives the HTTP request.
A permanent 301 redirect informs clients and search engines that the destination is stable, whereas a 302 indicates a temporary redirect. The choice should reflect the project’s intent and can affect caching, links, indexing, and browser behavior. Some forwarding services offer "masked" forwarding where the original address remains visible through a frame or intermediary page. This approach may cause issues with accessibility, sharing, analytics, security, and mobile display. In most cases, a transparent HTTP redirect to the actual destination is preferred.
Technical Configuration
Forwarding must cover all intended variations, such as with and without www, HTTP and HTTPS protocols, and any paths. A generic forward may only redirect the homepage and miss deeper pages; one that preserves the path retains the portion after the domain if the destination supports matching URLs. Avoid multiple redirects that chain through several steps before reaching the final page, as this increases latency and error risk. A loop, where two domains redirect to each other, makes the site unreachable. Testing both the status code and final URL across multiple browsers is essential.
The HTTPS certificate must also be available on the source domain. If a visitor accesses via https and the certificate is missing or expired, the browser will show a warning before the redirect can execute. A forwarding provider should support TLS for both names. DNS records must also point to the service performing the redirect; updating only the registrar without setting up the zone is insufficient. If email is hosted on the forwarded domain, preserve MX and authentication records: changing DNS for web access alone may disrupt mail if the zone is not correctly copied.
Uses and Limitations
Forwarding is useful for consolidating brand variants, recovering links to an old site, managing campaign domains, or directing a short name to a specific section. Before migration, inventory existing URLs, backlinks, and important pages. A blanket redirect of all pages to the homepage can confuse users and search engines; mapping old resources to relevant destinations is better. When changing structure, monitor 404 errors, redirect chains, and residual access to correct mappings. Domain registration and forwarding are separate services, so renewal of the domain name remains necessary.
Forwarding does not transfer ownership, hosting, or content, nor does it automatically protect a domain from theft or expiration. It does not replace SEO migration, canonical tags, or application rules when the destination page must handle different content. If the domain is used for email, web forwarding does not automatically forward emails. In summary, domain forwarding directs requests from one domain to another URL via redirects or intermediary services. Proper configuration preserves HTTPS, paths, mail, and expected behavior, avoiding masking or unnecessary chains.
← Full glossary