What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Redirecting a domain sends visitors from one web address to another, whether you are moving to a new brand, consolidating duplicate domains, pointing a parked domain to your main site, or forwarding an old URL after a website migration. A well-configured redirect helps users land in the right place and preserves search visibility, bookmarks, and referral traffic as much as possible.
Domain redirects can be handled in several ways, including registrar forwarding, DNS provider tools, hosting control panels, web server rules, or application-level settings. The right method depends on how much control you need, whether the redirect applies to an entire domain or specific paths, and whether it should be permanent, temporary, or masked.
As an Amazon Associate I earn from qualifying purchases.
Before changing settings, it is useful to understand the differences between common redirect types, confirm where your domain is managed, and plan how you will test the result. A clear setup process can prevent redirect loops, HTTPS errors, broken paths, and delays caused by caching or DNS propagation.
What Domain Redirects Are and When to Use Them
A domain redirect sends visitors from one address to another automatically. When someone enters oldexample.com, clicks an outdated link, or requests a specific URL, the redirect tells the browser or search engine to load a different destination, such as newexample.com or example.com/new-page. This can happen at the registrar, DNS provider, hosting control panel, web server, CDN, or application level, depending on how the domain and website are managed.
Redirects are commonly used when a business changes its domain name, consolidates mulle domains, moves from HTTP to HTTPS, or wants several variations of a domain to point to one primary site. For example, a company might redirect example.net and example.org to example.com, or redirect www.example.com to example.com to keep a single canonical version of the site. They are also useful after a site restructure, where older URLs need to lead visitors to updated pages instead of producing 404 errors.
Domain redirects can apply to the entire domain or to individual paths. A full-domain redirect might send every request for oldbrand.com to newbrand.com. A path-level redirect might send oldbrand.com/pricing to newbrand.com/plans. Preserving paths and query strings can be valuable during migrations because users and search engines reach the closest matching content rather than landing on a generic homepage.
Common situations for using a domain redirect
- Rebranding: moving from an old company or product domain to a new one.
- Domain consolidation: sending alternate extensions, misspellings, or regional domains to a main domain.
- Canonical domain selection: choosing either the www or non-www version as the preferred address.
- HTTPS migration: forwarding all HTTP traffic to the secure HTTPS version.
- Campaign forwarding: pointing a short or memorable domain to a landing page.
- Content migration: mapping retired URLs to replacement pages after a redesign or CMS change.
Redirects also help maintain user trust and search visibility. Without them, visitors may see browser errors, parked domain pages, or missing-page messages. Search engines may treat the old and new addresses as separate locations, which can split ranking signals and make indexing less predictable. A properly planned redirect keeps navigation smooth and helps transfer signals from the old URL to the new destination, especially when the change is permanent and the redirect type is selected correctly.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →They are not always the best tool, though. If you only need a domain to resolve to the same website infrastructure, DNS records such as A, AAAA, or CNAME records may be involved, but DNS alone does not create an HTTP redirect with a visible URL change in the browser. If you need the browser address bar to change from one URL to another, you need an actual redirect service or server-side rule. Understanding that distinction makes it easier to choose the right setup method in the sections that follow.
Choosing Between 301, 302, and Masked Redirects
Before setting up a domain redirect, choose the redirect type that matches the purpose of the move. The three common choices are 301 redirects, 302 redirects, and masked redirects. They may look similar to visitors because each can send someone from one address to another, but browsers, search engines, analytics tools, and hosting platforms treat them differently.
301 redirects: permanent moves
A 301 redirect tells browsers and search engines that the original URL has permanently moved to a new destination. Use it when you have changed your primary domain, consolidated mulle domains into one site, moved from an old brand to a new brand, or want example.net to always forward to example.com. It is also the usual choice when redirecting from HTTP to HTTPS or from the non-www version of a domain to the www version, or the other way around.
For search visibility, a 301 redirect is usually the safest long-term option because it signals that ranking signals and indexing should transfer to the new URL over time. It also helps avoid duplicate versions of the same website being accessible from several domains. Once a 301 is cached by browsers and search engines, it can take time to reverse, so use it only when the destination is intended to remain in place.
302 redirects: temporary forwarding
A 302 redirect indicates that the move is temporary and that the original URL may be used again. Choose this when you are running a short campaign, testing a landing page, sending traffic to a maintenance page, or temporarily forwarding a domain during a site migration. For example, you might send promo.example.com to a seasonal page for a few weeks, then point it elsewhere later.
Because a 302 does not communicate a permanent move, search engines typically keep the original URL as the main address in their index. That behavior is useful for short-term changes but can be undesirable if the redirect remains in place for months. If a temporary redirect becomes permanent, change it to a 301 so browsers and search engines receive a clear signal.
Masked redirects: keeping the original domain in the address bar
A masked redirect, sometimes called URL masking or frame forwarding, loads the target website while keeping the original domain visible in the browser address bar. For instance, a visitor may type example.org and still see example.org while content from another-site.com appears on the page. This is usually done through a registrar or forwarding service rather than a standard web server redirect.
Rank #2
Masked redirects can create issues with mobile display, SSL certificates, cookies, login forms, analytics tracking, accessibility, and search indexing. Many modern sites also block being displayed inside frames for security. Use masking only for simple, low-risk cases, such as a temporary placeholder or a very basic external page. For a professional website, a standard 301 or 302 redirect is usually cleaner and more reliable.
| Redirect type | Best use | Search engine signal |
|---|---|---|
| 301 | Permanent domain or URL change | Transfer indexing signals to the new URL |
| 302 | Temporary forwarding, tests, campaigns, maintenance | Keep the original URL as the primary address |
| Masked | Simple forwarding while showing the original domain | Often unreliable for indexing and tracking |
As a practical rule, use 301 for permanent moves, 302 for temporary changes, and avoid masked redirects unless you have a narrow use case and understand the limitations. This choice should be made before changing registrar forwarding, DNS-related services, hosting panel settings, or server configuration, because the redirect type affects how the move is cached, indexed, and measured.
Redirecting a Domain Through Your Registrar or DNS Provider
Many registrars and DNS providers include a simple forwarding feature that sends visitors from one domain to another URL without requiring a hosting account. This is commonly used when you own example.net and want it to send visitors to https://example.com, or when a parked domain should point to a product page, landing page, or primary website. The exact labels vary by provider, but the feature is usually called Domain Forwarding, URL Forwarding, Web Forwarding, or Redirect.
To set it up, sign in to your registrar or DNS provider, open the domain’s management page, and look for forwarding or redirect settings. Enter the destination URL exactly as it should load, including https:// and any path, such as https://www.example.com/sale. If the provider offers a redirect type, choose 301 for a permanent move or 302 for a temporary one. Save the change, then allow time for the provider to publish the setting. Some forwarding changes work within minutes, while others can take longer depending on the provider’s infrastructure and cached DNS records.
Domain forwarding is not the same as a standard DNS record. DNS records such as A, AAAA, and CNAME point a hostname to an IP address or another hostname; they do not, by themselves, redirect a browser to a different URL. A redirect requires an HTTP response from a web service. When you use registrar forwarding, the registrar typically points your domain to its own forwarding servers, which then return the redirect response to visitors.
Recommended Free Tools
Typical setup steps
- Open the domain settings at your registrar or DNS provider.
- Find the forwarding, redirect, or URL forwarding section.
- Choose the source host, such as the root domain example.com or a subdomain like www.example.com.
- Enter the full destination URL, including protocol and path.
- Select 301 or 302 if the option is available.
- Decide whether to forward only the root domain, only www, or both.
- Save the change and test from a browser and command-line HTTP checker.
Pay close attention to the root domain and the www version because they are separate hostnames. Forwarding example.com does not always forward www.example.com unless your provider automatically includes it. If needed, create forwarding rules for both versions, or use a DNS record for www that points to the provider’s forwarding service. For subdomains such as go.example.com or shop.example.com, create a separate forwarding entry for each hostname you want to redirect.
Some providers offer masked forwarding, where the browser continues showing the original domain while displaying the destination site in a frame. This is usually a poor choice for modern websites because it can interfere with mobile layouts, analytics, SSL certificates, login flows, and search indexing. A standard 301 or 302 redirect is usually cleaner and more reliable because the browser lands on the real destination URL.
If the redirect does not work, check for conflicting DNS records, especially old A or CNAME records on the same hostname. Confirm that the domain uses the nameservers where you made the change; editing DNS at one provider has no effect if the domain is delegated to another. Also verify HTTPS behavior. Some registrar forwarding services handle HTTP redirects but fail on https://example.com unless SSL forwarding is included. In that case, use a hosting control panel, CDN, or web server configuration that can serve a valid TLS certificate and return the redirect securely.
Setting Up Redirects in Hosting Control Panels
Hosting control panels are often the fastest place to create a domain redirect when the domain is already attached to a hosting account. Unlike registrar forwarding, a hosting-panel redirect is handled by the web hosting environment, so the domain usually needs to point to the host’s nameservers or server IP address first. This method is common when you manage websites through cPanel, Plesk, DirectAdmin, hPanel, or a managed WordPress hosting dashboard.
In cPanel, open Domains or Redirects, then choose the redirect type, usually Permanent 301 or Temporary 302. Select the source domain from the dropdown, enter the destination URL, and decide whether the redirect should apply to the bare domain, the www version, or all matching paths. For example, redirecting example.net to https://example.com can often preserve page paths, sending example.net/about to example.com/about. After saving, cPanel typically writes the rule into the site’s .htaccess file.
In Plesk, redirects are usually configured from Websites & Domains. You can add a domain, choose a hosting type such as Forwarding, and enter the target address. Plesk commonly offers standard forwarding and frame forwarding; standard forwarding is preferred for most SEO and usability cases because visitors see the final destination URL in the browser. In DirectAdmin or similar panels, look for menu items such as Site Redirection, Domain Pointers, Aliases, or Forwarders, depending on how the host labels the feature.
Most hosting panels follow a similar setup flow:
- Confirm the domain is connected to the hosting account. Check that its DNS points to the hosting provider through nameservers, an A record, or another supported setup.
- Open the redirect or domain forwarding tool. This may be under domains, websites, aliases, or site tools.
- Select the source domain and path. Redirect the entire domain, a subdomain, or a specific folder such as /old-section.
- Enter the full destination URL. Include the protocol, such as https://, and use the correct hostname and path.
- Choose the redirect status. Use 301 for permanent moves and 302 for short-term campaigns, testing, or temporary maintenance.
- Save and test in a private browser window. Cached redirects can make a browser show an old result even after the rule has changed.
Control-panel redirects can conflict with existing site rules, especially on WordPress, Joomla, Laravel, or custom applications that already manage routing. If the redirect does not work, inspect the site’s .htaccess file, Nginx configuration provided by the host, or application-level redirect plugins. Also check for redirect chains, such as http to https, then non-www to www, then old domain to new domain. A clean setup should send visitors to the final URL in as few hops as possible.
SSL certificates are another common issue. If visitors enter https://old-domain.com, the old domain still needs a valid certificate before the browser can safely receive the redirect. Many hosting panels let you issue a free certificate for the source domain before enabling the redirect. Once the rule is active, verify both http and https, with and without www, and test a few deeper URLs to confirm that paths are handled as intended.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteConfiguring Redirects on Apache, Nginx, or Application Servers
Server-level redirects are useful when you control the hosting environment and need precise behavior beyond what a registrar, DNS provider, or control panel offers. They are commonly used to force HTTPS, redirect www to non-www or the reverse, move an old domain to a new domain, preserve paths and query strings, or redirect only selected pages. These redirects happen after DNS has resolved the domain to your server, so the domain must still point to the correct hosting account or server IP.
On Apache, redirects are often configured in the site’s virtual host file or in an .htaccess file if overrides are enabled. A simple domain-wide 301 redirect can be handled with Redirect or RewriteRule. For example, redirecting every request from an old domain to the same path on a new domain is usually done with rewrite rules that match the host name and append the requested URI. After changing Apache configuration files, reload or restart Apache so the change takes effect; for .htaccess, changes usually apply immediately.
- Use virtual host configuration when you have server access and want faster, centralized rules.
- Use
.htaccesson shared hosting when you do not control the main Apache configuration. - Use 301 redirects for permanent migrations and canonical domain redirects.
- Use 302 or 307 redirects for temporary routing, campaign pages, or short-term maintenance.
On Nginx, redirects are configured in server blocks, usually with a dedicated block for the source domain. A common pattern is to listen for the old host name and return a redirect to the new host, preserving the original request path. Nginx does not use .htaccess, so all redirect rules must be placed in the active site configuration and then tested before reload. Run a configuration test, such as nginx -t, before applying changes to avoid taking the site offline due to a syntax error.
Application servers can also issue redirects from within the app itself. This is common in Node.js, Express, Django, Rails, Laravel, Spring, and similar frameworks. Application-level redirects are helpful when the destination depends on business rules, user status, locale, product IDs, or database lookups. For simple whole-domain redirects, however, the web server or reverse proxy is usually better because it responds earlier and avoids unnecessary application processing.
Practical setup checks
- Confirm the old domain resolves to the server where the redirect rule is configured.
- Install or issue TLS certificates for both the source and destination domains if HTTPS requests must redirect cleanly.
- Preserve paths when moving a full site, such as
/aboutbecominghttps://new.example.com/about. - Avoid redirect chains, such as HTTP to HTTPS, then non-www to www, then old domain to new domain.
- Check that query strings are retained when needed for tracking, search, or application behavior.
After saving the configuration, test with a browser and with command-line header checks to confirm the status code and Location header. Test variations including HTTP, HTTPS, www, non-www, trailing slashes, deep URLs, and URLs with query strings. If the redirect fails, the most common causes are DNS pointing elsewhere, missing virtual host matches, cached browser redirects, CDN rules overriding the server, absent SSL certificates, or conflicting rules in the application and web server.
Testing, Troubleshooting, and Maintaining Redirects
After you configure a domain redirect, test it from several angles before considering the job finished. Open the old domain in a private browser window, try both http:// and https://, and check common variants such as example.com and www.example.com. If the redirect targets a specific path, test deep URLs as well, such as old-domain.com/pricing or old-domain.com/blog/article, to confirm whether they land on the matching new page or the intended homepage.
Use command-line and online tools to inspect the response chain. A browser may hide intermediate hops, but tools such as curl, redirect checkers, and SEO crawlers show each status code and destination. A clean permanent redirect often looks like one 301 response from the old URL to the final new URL. Mulle hops, such as HTTP to HTTPS, non-www to www, and then old domain to new domain, can still work, but they add latency and make troubleshooting harder. Where possible, configure the first request to point directly to the final destination.
Common issues to check
- DNS has not propagated: Registrar, DNS, and hosting changes may take minutes or hours to appear globally, depending on TTL values and resolver caching.
- Wrong redirect type: Use 301 for permanent moves and 302 or 307 for temporary changes. Avoid masked redirects when search indexing, analytics accuracy, or user trust matters.
- HTTPS certificate errors: If visitors use HTTPS on the old domain, that old domain still needs a valid TLS certificate before the browser can receive the redirect safely.
- Redirect loops: Conflicting registrar, hosting, CDN, or server rules can send requests back and forth between URLs.
- Missing path forwarding: Some simple forwarding tools send every request to the new homepage instead of preserving paths and query strings.
- Cached browser results: Browsers aggressively cache 301 redirects, so test in private mode or with a different device if changes do not appear.
If a redirect fails, isolate each layer. First confirm the domain resolves to the expected provider with a DNS lookup. Then check whether the request reaches the registrar forwarding service, hosting account, CDN, or origin server. Disable duplicate rules temporarily if more than one system is attempting to redirect the same hostname. For web server rules, review pattern matching carefully: a missing slash, overly broad wildcard, or incorrect capture group can redirect valid URLs to broken locations.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsMaintenance is just as as initial setup. Keep the old domain registered for as long as users, backlinks, email signatures, ads, or printed materials may still reference it. Renew TLS certificates for redirected HTTPS hostnames and monitor redirects after DNS migrations, hosting changes, CDN updates, or CMS plugin changes. Periodically crawl the old domain and review analytics or server logs for 404 errors, unexpected destinations, long redirect chains, and traffic to legacy paths that may deserve page-specific redirects.
Finally, document the redirect source, destination, status code, and where the rule is configured. This prevents future teams from unknowingly adding conflicting forwarding at another layer. A short redirect inventory is especially useful when managing mulle domains, brand changes, campaign URLs, or international sites with several hostnames pointing to different sections of the same web property.
Frequently Asked Questions
Can I redirect a domain using only DNS records?
DNS cannot create an HTTP redirect by itself because it only points a domain to an IP address or hostname. To redirect visitors from one URL to another, you need a registrar forwarding feature, hosting control panel redirect, web server rule, or application-level redirect. Some DNS providers offer “URL forwarding,” but that is a separate web forwarding service, not standard DNS.
Should I use a 301 or 302 redirect when moving a domain permanently?
Use a 301 redirect when the move is permanent, such as changing from an old domain to a new domain. Search engines usually transfer ranking signals more reliably with a 301, and browsers may cache it aggressively. Use a 302 only for temporary changes, testing, campaigns, or short-term maintenance pages.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →How do I redirect both the root domain and www version?
You need to configure redirects for both hostnames, such as example.com and www.example.com. This often means adding both versions in your registrar forwarding settings, hosting panel, or web server configuration. Also make sure both hostnames have valid DNS records and SSL certificates if visitors may access them over HTTPS.
Why does my redirect work with http but fail with https?
HTTPS redirects require the original domain to have a valid SSL/TLS certificate before the browser can receive the redirect response. If the certificate is missing, expired, or does not cover the domain, visitors may see a security warning instead of being redirected. Add or renew the certificate for the redirecting domain, including the www version if needed.
How can I check whether my domain redirect is set up correctly?
Test the root domain, www version, HTTP, HTTPS, and a few subpages to confirm they all land on the intended destination. Use browser developer tools, curl, or an online redirect checker to inspect the status code and redirect chain. A clean setup usually returns one redirect hop with the correct 301 or 302 status code.
Bottom Line
Redirecting a domain is usually straightforward once you choose the right method: registrar forwarding for simple redirects, hosting control panels for site-level changes, or web server rules when you need more control. Use a 301 redirect for permanent moves and a 302 or 307 when the change is temporary.
Free tools Windows power users keep installed
One-click scans. No signup required.
After setup, test the redirect in mulle browsers, confirm the final URL and HTTPS behavior, and allow time for DNS or cache updates if needed. If it does not work as expected, check nameservers, DNS records, SSL coverage, redirect loops, and any conflicting rules before making further changes.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
