What is secure web forwarding? How it works and when to use it

Key takeaways:

• Secure web forwarding sends visitors from one domain or URL to another while keeping the forwarding connection on HTTPS.
• Without HTTPS support, visitors may hit a browser warning before they ever reach the site you’re sending them to.
• You can use it when an old domain needs a new home, a campaign needs a short URL, or an alternate domain needs to point to your main site.

Have you ever typed an old website address only to land on a completely different site? The business may have changed its domain, or you may be using a second domain to point people to your main website.

Domain forwarding is useful in situations like these, but there’s another detail to consider when people access the forwarding address through HTTPS. The domain still needs to handle that secure connection before visitors can be sent to the site you want them to see. This can come up when you’re changing domains, managing several web addresses, or creating a short URL for a campaign.

What is secure web forwarding?

Secure web forwarding automatically sends visitors from one domain or URL to another while supporting an encrypted HTTPS connection on the forwarding domain.

You may also see domain forwarding, URL forwarding, or domain redirect used to describe this process. Someone enters one address, and the forwarding service sends them to a different destination URL.

The forwarding domain needs to support HTTPS before the redirect can happen. The browser first checks that it can establish a secure connection with the domain. That requires HTTPS support and a valid SSL certificate.

If the forwarding domain doesn’t support HTTPS, the browser may show a security warning or error instead of sending the visitor to the destination.

There’s one important distinction, though. Secure web forwarding only protects the connection to the forwarding domain. It doesn’t secure the destination website. The destination still needs its own HTTPS protection.

How secure web forwarding works

When someone visits a forwarded domain, the process looks like this:

1. The visitor enters or clicks the original URL.
2. The browser requests the HTTPS version of the forwarding domain.
3. The browser establishes a secure connection with the forwarding domain.
4. The forwarding service sends back a URL redirect.
5. The browser follows the redirect and requests the destination URL.

DNS records and DNS settings can affect how the forwarding domain is configured. Once the forwarding is working, the service handles the redirect.

Who needs secure web forwarding?

The reason you’re forwarding a domain can vary. You might be running a business, managing a website, or working on a marketing campaign. Here are a few situations where it can make sense:

Small business owners and site owners

Maybe you changed your business name or moved your website to a new domain. People may still be using the old address, especially if they have it bookmarked or saw it on an older piece of marketing.

You can forward that domain to your main site instead of leaving visitors wondering where it went. Anyone who types the old address can still find your business.

Web developers and system administrators

If you’re moving a website to a new domain, you’ll probably have to deal with forwarding at some point. Changes to the URL structure or DNS settings can bring it up, too.

Before you make the switch, check the DNS records, HTTPS support, and redirect settings. Conflicting DNS records can get in the way, so it’s worth testing the old URL and its HTTPS version before you consider the move finished.

There’s no need to make the setup more complicated than it is. You just want to know that the forwarding domain connects properly and sends visitors where they’re supposed to go.

Digital marketers and brand managers

A long landing-page URL isn’t exactly easy to remember, especially when you’re putting it on a poster or asking someone to type it into their browser. A short domain gives you a cleaner address to share.

You can forward that domain to your campaign page and change the destination later if you need to. The same approach can work when you’re going through a rebrand or managing several domains for the same campaign.

Why does secure web forwarding matter?

When you forward a domain, you want visitors to get where they’re going without running into a security warning along the way. HTTPS support on the forwarding domain helps keep that first connection secure. You’ll see why this is useful when:

It helps prevent security warnings and broken journeys

Most people don’t know or care what’s happening with a redirect behind the scenes. They click a link because they expect a page to open.

A browser warning changes that experience. Someone looking for your business may see the warning and leave, even when the destination site is perfectly fine. The same thing can happen with an old link that no longer leads anywhere useful.

It supports safer site migrations and sensitive customer journeys

When you move a website to a new domain, forwarding helps direct visitors from the old domain to the new site. It sends visitors to the new destination instead of leaving them at an outdated URL.

This becomes especially useful when the destination URL leads to a checkout or another page where customers expect a secure HTTPS site.

It helps protect traffic from alternate and secondary domains

Businesses often have multiple domains pointing to the same primary site. You might own an alternate extension, a previous brand domain, or a common variation of your original domain.

You can forward multiple domains to the primary site so visitors who use those addresses can still find you. The same applies to domains you’ve acquired to protect your brand. This can help you capture traffic that might otherwise be lost when someone uses an old or alternate domain.

If you’re also buying domains to protect your brand, it’s worth knowing how cybersquatting can put those domains at risk. Read What is cybersquatting?

When should you use secure web forwarding?

Secure web forwarding is useful when an HTTPS-enabled domain needs to send visitors somewhere else. Here are some common situations where you might use it:

When migrating or rebranding a website

A domain change doesn’t mean you have to leave the old address behind. You can send visitors from the old domain to the new site, so people who still use the original domain can find you.

If the old address is being replaced for good, a 301 redirect usually makes sense. Once it’s set up, check both the HTTP and HTTPS versions of the old domain. The redirect may work on one and fail on the other, so it’s worth testing both before you call the switch done.

When redirecting a campaign or promotional domain to a landing page

A short campaign domain can give people a simple web address to remember and type into their browser. You can use URL forwarding to send that address to the destination URL for your campaign.

For example, a promotional domain could take visitors to a seasonal offer on your website. It could also point to a destination site outside your main website. Either way, the domain you’re forwarding still needs HTTPS support. The redirect only sends the website traffic to the place you choose.

When pointing a domain to social links or profiles

You can also use a custom web address to send people to a social profile, Linktree page, Etsy shop, or another external page. The domain gives people one simple address to remember, while URL forwarding sends them to the destination URL you choose.

But remember, the secure connection only applies to the forwarding part. It doesn’t guarantee anything about the security of the destination site.

Ways to get secure web forwarding

Your domain provider may already offer secure forwarding. If it doesn’t, you may need to set it up yourself.

Before you get started, check whether HTTPS is supported. Standard domain forwarding doesn’t always include it. If not, you have a couple of other options:

Method #1: Use secure forwarding from your domain provider

Once you get to the forwarding settings, you’ll choose the domain and enter the destination URL. Your provider will give you the settings available for that domain, and it may also handle the SSL certificate for you.

If you have several domains, check whether you can forward them all and whether the service gives you the redirect type you need.

Method #2: Configure secure forwarding through a hosting or server environment

If you have access to your hosting or server settings, you can handle the HTTPS connection and redirect there. This gives you more control over how the forwarding works and where visitors end up. You can also adjust the URL structure or redirect rules to fit your setup.

You’ll need to handle the SSL certificate and server settings yourself. If you’re already comfortable with your hosting or server, this extra control may work well for you.

Method #3: Use a third-party secure redirect service

A third-party service can be useful when your domain provider doesn’t offer secure forwarding. Some services are built specifically for redirects and can handle HTTPS without requiring you to set up a web server.

You may also get features that aren’t available with basic domain forwarding, such as forwarding multiple domains or keeping the URL path intact. For example, olddomain.com/products could go to newdomain.com/products instead of sending every visitor to the homepage.

Frequently asked questions

Forward your domains with confidence

You don’t always need to give up a domain just because you’re no longer using it for a website. It can still send people to your current site or give you a memorable address for a campaign.

Just don’t forget about the connection along the way. Secure web forwarding supports HTTPS on the forwarding domain, so check that before you put the address out there. It’s also worth checking the redirect and destination URL while you’re at it.

If you’re looking for another domain name, we can help you register and manage it, along with free tools and apps for your online presence.