Domain Forwarding: How It Works and How to Set It Up

Domain forwarding is a DNS-level method that automatically sends visitors from one domain name to another, without requiring a web server or hosting on the forwarded domain. It is one of the most common ways to handle parked domains, post-rebrand traffic, and vanity URLs that need to point somewhere useful.

The concept is simple. The execution is where things break. Most domain registrars offer forwarding as a built-in feature, but the majority only forward HTTP traffic. When someone types https://yourdomain.com into a modern browser, the connection fails before the redirect ever fires. The browser demands a valid SSL certificate on the source domain, and if there is none, visitors see an error page instead of your destination site.

This article compares three ways to set up domain forwarding without hosting, explains why HTTPS forwarding breaks at most registrars, and covers the SEO implications of each approach. For a broader look at domain-level redirects and migration planning, see our domain redirects guide.

Key Takeaways

• Domain forwarding sends all traffic from one domain to another via DNS, with no hosting or server required on the source domain
• Most registrars forward only HTTP traffic. HTTPS requests fail because there is no valid SSL certificate on the source domain to complete the TLS handshake
• Three methods: registrar forwarding (free but limited), DNS-based forwarding service (HTTPS, analytics, path forwarding), and Cloudflare (free tier, limited rules)
• Always use a 301 redirect for permanent forwards. Some registrars default to 302, which prevents search engines from transferring link equity
• Registrar forwarding sends all paths to one destination. Path-preserving forwarding keeps the URL structure intact, which matters for SEO and user experience

What is domain forwarding?

Domain forwarding, also called web forwarding, URL forwarding, or domain name forwarding, is the process of redirecting all traffic from one domain to another. When someone types or clicks a forwarded domain, their browser is automatically sent to a different destination URL. The visitor does not need to know (or care) that the original domain exists.

Under the hood, domain forwarding is a standard HTTP redirect. The browser sends a request to the forwarded domain. The DNS points that domain to a server (either the registrar's forwarding server or a dedicated forwarding service). That server responds with an HTTP 301 or 302 status code and a Location header pointing to the destination. The browser follows the redirect and loads the destination page.

Three common scenarios where domain forwarding makes sense:

• Brand protection. You own acmeco.net, acmeco.org, and acmeco.co. All three forward to acmeco.com so that traffic reaches your primary site regardless of which extension someone types. This is standard practice for companies managing multiple TLD variants.
• Post-rebrand traffic. After a company rename or domain change, the old domain still receives traffic from bookmarks, printed materials, and cached search results. Forwarding the old domain to the new one preserves that traffic. For the full migration process, see our domain migration SEO checklist.
• Campaign and vanity URLs. Short, memorable domains (like promo.yourbrand.com or a dedicated .io domain) can forward to specific landing pages. This is common in print advertising, podcast sponsorships, and event marketing where a clean URL matters.

Domain forwarding vs URL redirects

Domain forwarding and URL redirects are technically the same mechanism (an HTTP 301 or 302 response), but they operate at different levels. Our complete guide to URL redirects covers the full spectrum of redirect types and use cases.

Domain forwarding applies to an entire domain. You set it up once, and every request to that domain gets redirected. It is typically configured at the DNS level or through your registrar's control panel. You do not need a web server, a CMS, or an .htaccess file.

A URL redirect applies to a specific URL or path. You might redirect /old-page to /new-page within the same domain, or redirect a single URL to a different site. URL redirects are usually set up on the server (Nginx, Apache, IIS), in a CMS plugin, or through a redirect management tool.

The terminology can be confusing because registrars use "forwarding" while technical documentation uses "redirect." They describe the same HTTP behavior. The difference is scope: domain forwarding is broad (entire domain), URL redirects are granular (per path or page). For a step-by-step walkthrough of individual URL redirects, see how to set up a domain redirect. For the technical differences between DNS-level and server-side approaches, see DNS-level vs server-side redirects.

Two related concepts worth distinguishing. Email forwarding is separate from domain forwarding: it routes email from one address to another and requires its own configuration (MX records, not A records). redirect.pizza offers email forwarding as a separate feature. Wildcard forwarding applies to all subdomains of a domain (*.example.com) at once, which is useful for catching traffic to any subdomain. That requires a wildcard redirect setup, not a standard domain forward.

Why most domain forwarding breaks on HTTPS

This is the part that most forwarding guides skip entirely.

When a visitor types https://yourdomain.com, the browser initiates a TLS handshake before sending any HTTP request. During that handshake, the browser asks the server for an SSL certificate that matches the domain. If no valid certificate exists for the source domain, the browser blocks the connection and shows a security warning. The HTTP redirect that your registrar configured never executes, because the TLS layer rejected the connection before HTTP was even involved.

Most registrar forwarding services do not provision an SSL certificate for the forwarded domain. They handle the HTTP redirect, but HTTPS traffic hits a dead end. Some registrars are explicit about this. Hover's documentation states that their forwarding redirects to the HTTP version and will not function for HTTPS. Others, like GoDaddy, have recently started adding HTTPS support to their forwarding, but this is the exception rather than the rule.

This matters more than it used to. Chrome now defaults to HTTPS when you type a bare domain into the address bar, and other major browsers are moving in the same direction. If your forwarding only works over HTTP, a growing share of your traffic never reaches the destination.

Michel Bardelmeijer, Tech Lead at redirect.pizza:

Every browser defaults to HTTPS now. If your forwarding setup cannot serve a valid certificate on the source domain, your redirect is invisible to a growing share of your traffic. That is not an edge case anymore, it is the default behavior.

The fix is to use a forwarding method that provisions an SSL certificate on the source domain before any traffic arrives. DNS-based forwarding services do this automatically, typically using Let's Encrypt certificates that renew on their own.

Three ways to forward a domain without hosting

You do not need a web server, a hosting plan, or a CMS to forward a domain. There are three methods, each with different trade-offs.

Option 1: Registrar forwarding

Most domain registrars include a forwarding feature in their control panel. You log in, find the DNS or forwarding settings for your domain, enter a destination URL, and save. Setup takes about two minutes.

What you get:

• Free with your domain registration
• Simple setup, no technical knowledge required
• Works for basic domain-to-domain forwarding

What you do not get:

• HTTPS support at most registrars. Hover and many others only forward HTTP traffic. GoDaddy has added HTTPS forwarding recently, but check your specific registrar's documentation.
• Path forwarding. If someone visits yourdomain.com/pricing, registrar forwarding typically sends them to destination.com (the root), not destination.com/pricing. All paths collapse to the homepage.
• Analytics. No insight into how much traffic the forwarded domain still receives.
• 301/302 choice. Some registrars default to 302 (temporary) redirects. Hover uses 302 by default. That means search engines will not transfer link equity to the destination.

If you are forwarding a single parked domain that receives minimal traffic and HTTPS is not a concern, registrar forwarding works fine. For anything beyond that, the limitations add up.

redirect.pizza has setup guides for forwarding with HTTPS support at specific registrars: GoDaddy, Namecheap, Hover, Network Solutions, Cloudflare, Route 53, Azure DNS, and DigitalOcean.

Option 2: DNS-based forwarding service

A DNS-based forwarding service sits between your domain's DNS and the destination. You point your domain's A/AAAA records, CNAME, or nameservers to the service, and it handles the redirect on its own infrastructure.

The key advantage: the service provisions an SSL certificate for your source domain automatically, usually through Let's Encrypt. That means HTTPS forwarding works out of the box. No manual certificate management, no certificate expiration surprises.

What a DNS-based forwarding service typically includes:

• Automatic HTTPS with SSL certificate provisioning and renewal
• Path forwarding (preserves URL structure during the redirect)
• Query parameter forwarding (so yourdomain.com/page?ref=campaign forwards to destination.com/page?ref=campaign, keeping your tracking parameters intact)
• Analytics on forwarded traffic
• Bulk management for multiple domains (CSV import, API)
• Choice between 301 and 302 per domain

redirect.pizza is a DNS-based forwarding service. The free tier covers 5 domains and 250,000 requests per month. Setup involves changing your domain's DNS records and takes about five minutes, including DNS propagation time. For a detailed walkthrough of the DNS configuration, see DNS management.

For teams managing dozens or hundreds of domains (brand protection portfolios, post-acquisition consolidation), bulk import via CSV or API makes this manageable. Manually configuring forwarding at each individual registrar does not scale past a handful of domains.

Option 3: Cloudflare

Cloudflare can handle domain forwarding through its Redirect Rules and Bulk Redirects features. You add your domain to Cloudflare (free plan works), point your nameservers to Cloudflare, and create a redirect rule.

Redirect Rules (which replaced the now-deprecated Page Rules in 2024) let you define URL-matching patterns and forward to a destination. The free plan includes 10 single redirect rules. For larger setups, Bulk Redirects support redirect lists with thousands of entries, though the configuration is more involved.

Advantages: HTTPS works (Cloudflare provisions certificates through its proxy), and the free tier is genuinely free. Disadvantages: you must move your nameservers to Cloudflare, redirect rule syntax is more complex than a simple "from/to" form, and there is no built-in per-redirect analytics.

Comparison

Domain forwarding and SEO

Domain forwarding is an HTTP redirect, and search engines treat it accordingly. The redirect type you choose determines whether SEO value transfers to the destination.

301 (permanent) forwarding tells search engines that the source domain has moved permanently. Google transfers most of the original link equity to the destination URL. Over time, the source domain drops out of the index and the destination inherits its ranking signals. This is what you want for any permanent domain change.

302 (temporary) forwarding tells search engines the move is temporary. The source domain stays in the index. Link equity does not transfer. Use this only for genuinely temporary situations, like redirecting to a maintenance page. The problem: some registrars default to 302 without making it obvious. If your registrar is forwarding with a 302 and you intended a permanent move, your destination is not getting the SEO benefit.

Forwarding with masking (iframe) is a separate option offered by some registrars, including GoDaddy. It loads the destination site inside an iframe while keeping the source domain in the browser's address bar. This is harmful: search engines cannot crawl iframe content properly, the source domain accumulates no ranking value, and modern browsers may flag it as deceptive. Our link masking guide covers why this technique is outdated and what to use instead.

Path forwarding vs homepage forwarding also has SEO implications. If your old domain had indexed pages at /about, /pricing, and /blog, and your forwarding sends all of those to the destination's homepage, search engines lose the per-page relevance signals. Path-preserving forwarding (where old.com/pricing goes to new.com/pricing) maintains the 1:1 mapping and gives each destination page the ranking benefit from its corresponding source page. For the complete checklist on preserving SEO during a domain transition, see our domain migration SEO checklist.

Common mistakes when forwarding a domain

1. HTTP-only forwarding. The browser sends an HTTPS request, there is no certificate on the source domain, and the visitor sees a security warning instead of the redirect. This is the most common failure mode and the one most registrar how-to guides do not mention. The fix: use a forwarding method that provisions SSL certificates automatically.

2. Defaulting to 302 instead of 301. If your registrar uses 302 redirects by default (Hover does this), search engines keep the old domain in their index and do not transfer link equity. Check your redirect type with a tool like curl or a browser's developer tools. If it shows 302 and you intended a permanent move, switch to 301.

3. Using forwarding with masking. GoDaddy still offers this as a checkbox option. It loads your destination inside an iframe while showing the source domain in the address bar. Search engines treat the source domain as thin content. Analytics break. Mobile rendering breaks. Do not use this.

4. Sending all paths to the homepage. If your old domain had traffic to specific pages and your forwarding collapses everything to the destination's root URL, those visitors land on a page that does not match what they expected. Search engines lose the per-page signals. If your forwarding method does not support path preservation, at minimum set up individual redirects for your highest-traffic pages.

5. Not waiting for DNS propagation. After setting up forwarding, DNS changes can take up to 48 hours to propagate globally (though most resolve within a few hours). Test with whatsmydns.net to confirm your changes are live before assuming something is broken.

Frequently Asked Questions

Related Guides

• Domain Redirects Guide: How to Redirect Your Domain
• How to Set Up a Domain Redirect in 3 Minutes
• DNS-Level vs Server-Side Redirects: When to Use Each
• The Complete Guide to URL Redirects

Set up domain forwarding in minutes

redirect.pizza handles domain forwarding at the DNS level with automatic HTTPS, path forwarding, and analytics. No hosting required. The free plan covers 5 domains and 250,000 requests per month. Get started for free.