Key takeaways:
- Web forwarding and secure web forwarding both direct visitors to another URL, but the first connection is handled differently.
- HTTPS can help prevent browser warnings or connection problems when visitors reach your domain through a secure connection.
- A simple setup can work with web forwarding, while secure web forwarding fits traffic that reaches your domain through HTTPS.
When you type a domain into a browser, you expect to get where you’re going without thinking about what happens in between. That’s usually the experience a redirect gives you. But when you’re setting up web forwarding, there’s another choice to consider. Secure web forwarding handles the first connection differently, which can change how browsers respond and how reliable the forwarding feels. The difference also affects setup, so it’s worth knowing what you’re getting before you choose one.
What is the difference between web forwarding and secure web forwarding?
The two options may lead visitors to the same place, but the connection starts differently.
With regular web forwarding, that connection may begin over HTTP. Secure web forwarding uses HTTPS instead, so the visitor gets a secure connection before the redirect takes them to the destination URL. The browser still has to connect to the original domain before the redirect can do its job.
Need to forward a domain?
We can help you set up domain forwarding and send visitors to the URL you choose.
What is web forwarding?
Web forwarding, also called domain forwarding, sends visitors who enter one domain to a different URL. The original domain doesn’t need its own website. Instead, its traffic can point to the destination URL where you want visitors to land.
The forwarding is handled through your domain’s settings, using a redirect that sends the visitor to the destination. If you want a closer look at how domain forwarding works, see our domain forwarding guide.
What is secure web forwarding?
When someone visits a domain with secure web forwarding, their browser connects to that domain using HTTPS before the redirect sends them elsewhere. The destination stays the same, but the connection to the source domain is handled securely from the start.
HTTPS needs a valid SSL certificate to establish that secure connection. The visitor may only spend a moment at the source domain, but that first connection still needs to work properly before the redirect can happen.
Need an SSL certificate for your domain?
We offer SSL certificates that enable HTTPS and help protect connections between your domain and its visitors.
Web forwarding vs. secure web forwarding: Key differences
You might not notice anything different when a redirect works as expected. You enter a domain, and you end up where you need to go. The part worth looking at is what happens before you get there. Here’s where the differences come in:
Security and SSL
The visitor doesn’t jump straight from the source domain to the destination. The browser has to connect to the source first, and that connection needs to work before the redirect can take place. When visitors arrive through HTTPS, the source domain needs to support that connection. Secure web forwarding gives the first connection the HTTPS setup it needs, including a valid SSL certificate.
Browser compatibility
The browser also has its own expectations for that first connection. HTTPS is now the norm, and some domains are on the HSTS preload list, which tells browsers to use HTTPS when connecting to them. If the forwarding service can’t handle that secure connection, the browser may stop the visit with an SSL/TLS error instead of following the redirect.
That can leave visitors stuck before they reach the destination and may cost you traffic in the process.
Performance and speed
Once the browser makes that first connection, the forwarding setup can affect how quickly the visitor gets to the destination. An extra redirect or fallback gives the browser another step to process and another point where the connection could fail. A well-configured forwarding setup keeps the path to the destination as direct as possible.
Cost and setup
There’s also the practical side of setting up forwarding. What you get, how you configure it, and whether secure forwarding is included can vary from one provider to another. Namecheap, for example, offers free domain forwarding, while GoDaddy offers forwarding with and without masking.
But before you set anything up, check what your provider supports and whether you need to change any DNS settings. If you manage several domains, you’ll also want to consider how the forwarding will fit into your overall domain setup.
When to use web forwarding and when to use secure web forwarding
Sometimes a basic redirect is all you need. Other times, HTTPS traffic changes what you need from the forwarding setup. Here’s where each option fits:
When to use web forwarding
Web forwarding makes sense when you have a simple domain-to-destination URL setup and your provider handles the connection reliably. For example, you might point a subdomain to another website or send traffic from one domain to another. Before choosing this option, check how your provider handles secure browser requests.
When to use secure web forwarding
Go with secure web forwarding when visitors use HTTPS to reach your domain. This can be useful when you forward an old domain to a new domain, protect brand-related domains, or manage domains connected to eCommerce. It keeps the initial connection secure while the redirect takes visitors to where they need to go.
Pros and cons of web forwarding and secure web forwarding
If you’re deciding between the two, it helps to look at what you gain and what you’ll need to manage. Web forwarding requires less setup, while secure web forwarding is designed for visitors who reach your domain through HTTPS.
Web forwarding pros and cons
Pros
- Simple setup: Basic forwarding can be an easier option when you only need a domain to point to another URL.
- Straightforward configuration: Your provider may offer the redirect as part of its domain management tools.
Cons
- Browser issues: Modern browsers may flag non-HTTPS traffic or block an unencrypted redirect.
- Limited fit: A basic setup may not work well when visitors expect a secure connection.
Secure web forwarding pros and cons
Pros
- Works with secure traffic: The initial connection uses HTTPS, which fits the way modern browsers handle websites.
- More reliable visitor experience: A secure web forwarding setup can help avoid connection problems when people reach your domain through HTTPS.
Cons
- More to manage: The source domain needs a valid SSL certificate and a provider that supports secure forwarding.
- Provider differences: Setup, management, and cost vary, so check what’s included before you create the configuration.
How to choose between web forwarding and secure web forwarding?
The way visitors reach your domain can help you choose between the two. When HTTPS is part of that traffic, make sure your provider supports a secure connection before the redirect sends visitors on their way.
Then check the practical details. Does your registrar offer secure web forwarding? Is there a difference in cost or configuration? Does the option you’re considering fit the way you plan to use the domain?
Once you’ve made your choice, test the finished setup. Visit the source URL with both HTTP and HTTPS and check that the redirect works as expected. A few minutes of testing can catch connection problems before they affect your traffic.
The simplest check is also the most practical: try the domain yourself. As Michael Chattan, Senior Director of Domain Operations, puts it, “Verification is done by using your new service!”
Frequently asked questions
Web forwarding gives a domain a different place to send its visitors. When someone enters the domain or URL, the forwarding setup takes them to the destination URL instead.
Yes. You can redirect an old URL to a new destination URL when you move a website or change domains. If you forward an old domain to a new domain, test the redirect to make sure visitors reach the right place.
Enter the source URL in your browser and check that it takes you to the right website. Try the redirect from a private browser window too. If your setup has a button to save or apply changes, click it first and test again.
Yes. HTTPS matters because browsers expect a secure connection. With secure web forwarding, the source domain uses HTTPS before the visitor is redirected. Standard forwarding over HTTP may trigger a browser warning or connection error.
An HTTP-to-HTTPS redirect can fail when the source domain cannot handle a secure connection. Visitors may see a connection error instead of reaching the destination URL. Check that your provider supports HTTPS for web forwarding.
Domain forwarding only negatively impacts a website’s rankings if it’s done incorrectly. One common issue is masking, which keeps the original URL visible and can create SEO problems. Use the right forwarding setup for your situation and avoid masking when SEO matters.
Choose the right forwarding option for your website
Once you’ve settled on the forwarding method, don’t skip the last step: test it. Open the domain with HTTP and HTTPS, follow the redirect, and make sure you land where you expect. A quick check now is better than discovering a forwarding problem after visitors run into it.
Have a domain in mind? Search below to see what’s available.
Find the perfect domain
Ready to register a domain name? Check domain availability and get started with Network Solutions today.
