Domain Forwarding and Redirects: Setup Guide (2025)

Quick Answer

Table of Contents

Understanding Domain Forwarding

Domain forwarding redirects visitors from one domain to another automatically.

What Is Domain Forwarding?

Definition: Domain forwarding (also called domain redirection) is the process of automatically sending visitors who type one domain name to a different domain or URL.

Common scenarios:

Example 1: Alternative domain to main site

User types: yourbusiness.net
Browser redirects to: yourbusiness.com
User sees: yourbusiness.com in address bar

Example 2: Old domain to new brand

User types: oldcompanyname.com
Browser redirects to: newcompanyname.com
User sees: newcompanyname.com in address bar

Example 3: Marketing campaign

User types: specialoffer.com
Browser redirects to: yourbusiness.com/special-offer
User sees: yourbusiness.com/special-offer

How Forwarding Works

Basic process:

1. User enters domain in browser (e.g., domain-a.com)
2. DNS resolution occurs (browser finds server)
3. Server receives request
4. Redirect instruction sent to browser
5. Browser requests new URL (e.g., domain-b.com)
6. Final page loads

Two main approaches:

HTTP redirect (URL forwarding):

• Server sends redirect instruction to browser
• Browser makes new request to destination
• Address bar shows final destination

DNS pointing (DNS forwarding):

• Multiple domains point to same server IP
• Server decides what content to show
• Address bar may show original or destination

Types of Domain Forwarding

Permanent redirect (301):

• Indicates domain permanently moved
• Transfers SEO value to new domain
• Search engines update their index
• Use for: Rebranding, domain consolidation

Temporary redirect (302):

• Indicates temporary redirection
• Doesn't transfer SEO value
• Search engines keep original in index
• Use for: Maintenance, A/B testing, campaigns

Meta refresh:

• HTML-based redirect
• Slower than server redirects
• Not recommended for SEO
• Use for: Limited server access only

JavaScript redirect:

• Client-side redirect via JavaScript
• Search engines may not follow
• Poor for SEO
• Use for: Special use cases only

URL Forwarding vs DNS Forwarding

Understanding the difference helps you choose the right method.

URL Forwarding (HTTP Redirect)

How it works:

1. User visits forwarded domain
2. Server sends HTTP redirect response (301 or 302)
3. Browser automatically requests new URL
4. Final page loads

Technical details:

GET / HTTP/1.1
Host: olddomain.com

HTTP/1.1 301 Moved Permanently
Location: https://newdomain.com

Characteristics:

Advantages: ✓ Simple to set up via registrar ✓ Works without hosting ✓ Preserves SEO (with 301) ✓ Can forward to any URL ✓ Can include path forwarding

Disadvantages: ✗ Requires registrar forwarding service ✗ Limited customization ✗ May not work for email ✗ Extra redirect adds minimal delay

Best for:

• Redirecting unused domains to main site
• Consolidating multiple domains
• Rebranding scenarios
• Marketing campaign domains

DNS Forwarding (A Record Pointing)

How it works:

1. Multiple domains have A records pointing to same IP
2. User visits any domain
3. DNS resolves to same server
4. Server decides what to display based on requested domain

Technical details:

domain-a.com    A    93.184.216.34
domain-b.com    A    93.184.216.34

Server configuration determines response:

• Show same content for both domains
• Redirect one domain to another
• Show different content based on domain

Characteristics:

Advantages: ✓ Faster (no redirect) ✓ More control over behavior ✓ Can show same content under multiple domains ✓ Works well for hosting scenarios

Disadvantages: ✗ Requires web hosting ✗ More complex setup ✗ Doesn't transfer SEO by default ✗ May cause duplicate content issues

Best for:

• Multiple domains serving same website
• Hosting environment with multiple domains
• Advanced redirect scenarios
• When you control the server

Comparison Table

Which Should You Use?

Use URL forwarding when:

• Redirecting unused domains to main website
• You don't have hosting for the forwarded domain
• Simple redirect is sufficient
• You want registrar to handle it
• Rebranding or domain consolidation

Use DNS forwarding when:

• You have hosting/server control
• Need advanced redirect logic
• Want same content under multiple domains
• Building complex multi-domain site
• Need full control over behavior

Recommendation for most users: URL forwarding via registrar is simpler and sufficient for most needs.

301 vs 302 Redirects

Choosing the right redirect type affects SEO and user experience.

301 Redirect (Permanent)

What it means: "This page has permanently moved to a new location."

HTTP response:

HTTP/1.1 301 Moved Permanently
Location: https://newdomain.com

SEO impact:

• Transfers 90-99% of link equity to new URL
• Search engines update their index
• Old URL eventually replaced by new URL in results
• Consolidates ranking signals

Browser behavior:

• Browser may cache redirect
• Future visits go directly to new URL
• Users see new URL in address bar

When to use:

Permanent domain changes:

oldbrand.com → newbrand.com (rebranding)

Domain consolidation:

yourbusiness.net → yourbusiness.com
yourbusiness.org → yourbusiness.com

Alternative TLD forwarding:

yourbusiness.io → yourbusiness.com

WWW to non-WWW (or vice versa):

www.example.com → example.com

Protocol change:

http://example.com → https://example.com

Important: Only use 301 when redirect is truly permanent—reversing later can confuse search engines.

302 Redirect (Temporary)

What it means: "This page is temporarily at a different location."

HTTP response:

HTTP/1.1 302 Found
Location: https://temporarylocation.com

SEO impact:

• Does NOT transfer link equity
• Search engines keep original URL in index
• Original URL retains rankings
• New URL doesn't get SEO benefit

Browser behavior:

• Browser doesn't cache redirect
• Always checks original URL first
• Users see new URL after redirect

When to use:

Temporary campaigns:

campaign.com → mainsite.com/promo (during campaign only)

A/B testing:

example.com → version-a.example.com (temporary test)
example.com → version-b.example.com (alternate test)

Maintenance:

example.com → maintenance.example.com (during repairs)

Seasonal content:

holiday.example.com → example.com/holiday (seasonal)

Geographic testing:

example.com → us.example.com (for US visitors, temporary)

Important: Use 302 when you plan to change the redirect back or the redirect serves temporary purpose.

Other Redirect Types

303 See Other:

• After form submission
• Prevents duplicate form submissions
• Rarely used for domain forwarding

307 Temporary Redirect:

• Modern alternative to 302
• Guarantees method preservation (POST stays POST)
• Better for REST APIs
• Can be used instead of 302

308 Permanent Redirect:

• Modern alternative to 301
• Guarantees method preservation
• Less browser support than 301
• Use 301 for broader compatibility

Meta refresh:

<meta http-equiv="refresh" content="0;url=https://newdomain.com">

• HTML-based redirect
• Delays possible (content="5" = 5 second delay)
• Not ideal for SEO
• Use only if server redirects unavailable

JavaScript redirect:

window.location.href = "https://newdomain.com";

• Client-side redirect
• Search engines may not follow
• Can be blocked by users
• Avoid for domain forwarding

Redirect Type Decision Tree

Is the redirect permanent?
├─ Yes → Use 301 redirect
│   Examples: Rebranding, domain consolidation, www canonicalization
│
└─ No → Use 302 redirect
    Examples: Campaigns, A/B testing, maintenance pages

When to Use Domain Forwarding

Common scenarios where domain forwarding is the right solution.

Domain Consolidation

Scenario: You own multiple domain variations and want all to point to your primary domain.

Example:

Primary: yourbusiness.com
Forward to primary:
  - yourbusiness.net (301)
  - yourbusiness.org (301)
  - yourbusiness.co (301)
  - your-business.com (301)
  - theyourbusiness.com (301)

Benefits:

• Consolidates SEO value to one domain
• Prevents visitor confusion
• Protects brand from typosquatting
• Ensures all domains reach main site

Setup: 301 redirect from all alternate domains to primary

Rebranding

Scenario: Company changed name; old domain should redirect to new brand.

Example:

Old: acmecorp.com
New: superiorcorp.com

Redirect: acmecorp.com → superiorcorp.com (301)

Strategy:

1. Launch new domain with new branding
2. Set up 301 redirect from old to new
3. Maintain redirect for at least 1 year
4. Update all marketing materials
5. Notify customers of change
6. Monitor search rankings

Benefits:

• Preserves SEO value during transition
• Customers using old domain still reach you
• Gradual brand transition
• Maintains backlinks from old domain

Important: Keep redirect permanent to preserve SEO.

Marketing Campaigns

Scenario: Short, memorable domain for marketing campaign redirects to campaign landing page.

Example:

Campaign: summerpromo.com
Destination: yourbusiness.com/summer-sale

Redirect: summerpromo.com → yourbusiness.com/summer-sale (302)

Benefits:

• Easy-to-remember campaign URL
• Better for print/radio advertising
• Track campaign separately
• Can change destination as needed

Setup: 302 redirect (temporary) if campaign is time-limited

WWW Canonicalization

Scenario: Redirect www version to non-www (or vice versa) for consistency.

Example:

Option 1: www.example.com → example.com (301)
Option 2: example.com → www.example.com (301)

Why it matters:

• Search engines may treat www and non-www as separate sites
• Splits SEO value between two versions
• Creates duplicate content issues
• Choose one as canonical

Best practice:

• Choose preferred version (with or without www)
• Redirect other version permanently (301)
• Be consistent across all pages

Alternative TLD Protection

Scenario: Own .com but also registered .net, .org, .io to protect brand.

Example:

Primary: business.com
Protective registrations:
  - business.net → business.com (301)
  - business.org → business.com (301)
  - business.io → business.com (301)

Benefits:

• Prevents competitors from registering
• Protects against typos
• Consolidates traffic to main domain
• Brand protection

Localization and Internationalization

Scenario: Country-specific domains redirect to localized content on main site.

Example:

business.de → business.com/de (German)
business.fr → business.com/fr (French)
business.co.uk → business.com/uk (UK)

Or using ccTLDs as primary:

business.com (global)
business.de (German site, separate content)
business.fr (French site, separate content)

Setup depends on strategy:

• Redirect: Use 301 if consolidated site
• Separate sites: Use DNS pointing if unique content per country

Domain Sales and Transfers

Scenario: Domain sold but seller wants grace period before transfer, or buyer wants to test domain.

Example:

Sold domain: premiumdomain.com
Temporary destination: buyer-site.com

Redirect: premiumdomain.com → buyer-site.com (302 during transition)
Later: Full transfer of domain to buyer

Benefits:

• Buyer can test traffic quality
• Seller maintains control during payment
• Gradual transition period

Setting Up URL Forwarding

Step-by-step guide to URL forwarding using registrar tools.

General Setup Process

Most registrars follow similar steps:

Step 1: Log into registrar account

• Access your domain registrar
• Navigate to domain management
• Select the domain to forward

Step 2: Find forwarding option Common names:

• "Domain Forwarding"
• "URL Forwarding"
• "Web Forwarding"
• "Redirect"
• "Forwarding Settings"

Step 3: Configure redirect

• Enter destination URL
• Choose redirect type (301 or 302)
• Enable/disable path forwarding
• Enable/disable masking (usually avoid)

Step 4: Save and test

• Save forwarding settings
• Wait for propagation (5 minutes - 48 hours)
• Test by visiting forwarded domain
• Verify destination correct

Forwarding Configuration Options

Destination URL:

Format: https://destination.com
Required: Full URL including protocol

Examples:

✓ https://newdomain.com (correct)
✓ https://www.newdomain.com (correct)
✓ https://newdomain.com/page (correct)
✗ newdomain.com (missing protocol)
✗ www.newdomain.com (missing protocol)

Redirect type:

• Permanent (301): For permanent redirects
• Temporary (302): For temporary redirects
• Choose based on scenario (see 301 vs 302 section)

Path forwarding:

Disabled (default):

source.com/page1 → destination.com
source.com/page2 → destination.com
All paths go to same destination

Enabled:

source.com/page1 → destination.com/page1
source.com/page2 → destination.com/page2
Path is preserved

When to enable: If you want subpages on forwarded domain to map to same paths on destination

Domain masking (avoid):

What it does:

• Shows original domain in address bar
• Uses frame/iframe to display destination content
• Hides actual destination from visitor

Why to avoid:

• Hurts SEO (search engines see frame, not content)
• Breaks browser back button
• Causes security warnings
• Confuses visitors
• SSL certificate issues

Recommendation: Don't use masking; let redirect show destination URL

Testing Your Forward

Verification steps:

1. Browser test:

• Open incognito/private window (avoids cache)
• Type forwarded domain
• Verify redirects to destination
• Check address bar shows destination (unless masked)

2. Check redirect type:

Using curl (command line):

curl -I http://forwarded-domain.com

# Look for:
HTTP/1.1 301 Moved Permanently  (or 302)
Location: https://destination.com

Using online tools:

• redirect-checker.org
• httpstatus.io
• seoreviewtools.com/redirect-checker

3. Test with www:

Test both:
- http://forwarded-domain.com
- http://www.forwarded-domain.com

Ensure both redirect correctly

4. Test paths (if path forwarding enabled):

Test:
- forwarded-domain.com/page1
- forwarded-domain.com/path/to/page

Verify paths preserved or root redirect as expected

5. Verify in multiple browsers:

• Chrome
• Firefox
• Safari
• Edge

Setting Up DNS-Based Forwarding

For users with hosting or server control.

Using A Records

Concept: Point both domains to the same server IP address.

Step 1: Get destination server IP

# Find IP of destination
dig destination.com A +short
# Example output: 93.184.216.34

Step 2: Add A record for forwarded domain

Type: A
Name: @ (or leave blank for root domain)
Value: 93.184.216.34
TTL: 3600 (or default)

Step 3: Add A record for www

Type: A
Name: www
Value: 93.184.216.34
TTL: 3600

Step 4: Configure server

Option A: Server-side redirect

Apache (.htaccess):

<VirtualHost *:80>
    ServerName forwarded-domain.com
    ServerAlias www.forwarded-domain.com
    Redirect 301 / https://destination.com/
</VirtualHost>

Nginx:

server {
    listen 80;
    server_name forwarded-domain.com www.forwarded-domain.com;
    return 301 https://destination.com$request_uri;
}

Option B: Serve same content

Apache:

<VirtualHost *:80>
    ServerName destination.com
    ServerAlias forwarded-domain.com www.forwarded-domain.com
    DocumentRoot /var/www/html
</VirtualHost>

Nginx:

server {
    listen 80;
    server_name destination.com forwarded-domain.com www.forwarded-domain.com;
    root /var/www/html;
}

Using CNAME Records

Important limitation: CNAME cannot be used for root domain (@), only subdomains.

Valid CNAME usage:

Type: CNAME
Name: www
Value: destination.com.
TTL: 3600

Result:

www.forwarded-domain.com → points to destination.com

Invalid (won't work):

Type: CNAME
Name: @ (root domain)
Value: destination.com.
❌ Not allowed by DNS standards

Solution for root domain:

• Use A record for root
• Use CNAME for www
• Or use ALIAS/ANAME record (if supported)

ALIAS/ANAME Records (Cloudflare, DNSimple, etc.)

What they are: Proprietary DNS record type that acts like CNAME for root domains.

Providers supporting ALIAS/ANAME:

• Cloudflare (CNAME flattening)
• DNSimple (ALIAS)
• DNS Made Easy (ANAME)
• Route 53 (Alias records)
• NS1 (Linked records)

Setup:

Type: ALIAS (or ANAME, or CNAME with flattening)
Name: @ (root domain)
Value: destination.com
TTL: Auto or 3600

Benefits:

• Works for root domain
• Automatically follows IP changes
• Cleaner than hardcoded A records
• Better for managed hosting

Example (Cloudflare):

Type: CNAME
Name: @
Value: destination.com
Proxied: Yes (Cloudflare handles flattening)

Server-Side Redirect Configuration

Apache .htaccess:

Simple redirect:

RewriteEngine On
RewriteCond %{HTTP_HOST} ^(www\.)?forwarded-domain\.com$ [NC]
RewriteRule ^(.*)$ https://destination.com/$1 [R=301,L]

Redirect preserving path:

RewriteEngine On
RewriteCond %{HTTP_HOST} ^(www\.)?forwarded-domain\.com$ [NC]
RewriteRule ^(.*)$ https://destination.com/$1 [R=301,L]

Redirect to specific page:

RewriteEngine On
RewriteCond %{HTTP_HOST} ^(www\.)?forwarded-domain\.com$ [NC]
RewriteRule ^.*$ https://destination.com/landing-page [R=301,L]

Nginx configuration:

Simple redirect:

server {
    listen 80;
    server_name forwarded-domain.com www.forwarded-domain.com;
    return 301 https://destination.com$request_uri;
}

Redirect to specific page:

server {
    listen 80;
    server_name forwarded-domain.com www.forwarded-domain.com;
    return 301 https://destination.com/landing-page;
}

WordPress:

Using Redirection plugin:

1. Install "Redirection" plugin
2. Go to Tools → Redirection
3. Add new redirect:
   • Source URL: .* (regex for all)
   • Target URL: https://destination.com
   • Match: URL only
   • When matched: Redirect to URL

Or add to wp-config.php:

if ($_SERVER['HTTP_HOST'] == 'forwarded-domain.com') {
    header('HTTP/1.1 301 Moved Permanently');
    header('Location: https://destination.com' . $_SERVER['REQUEST_URI']);
    exit();
}

Registrar-Specific Setup Guides

Step-by-step instructions for popular registrars.

GoDaddy

Setup URL forwarding:

1. Log in to GoDaddy account
2. Navigate to "My Products"
3. Click "DNS" next to the domain
4. Scroll down to "Forwarding" section
5. Click "Add" next to "Domain"

Configure:

• Forward to: https://destination.com
• Redirect type: Permanent (301) or Temporary (302)
• Forward settings:
  • Forward only (recommended)
  • Forward with masking (avoid)

6. Save settings
7. Wait 15 minutes - 1 hour for propagation

Additional options:

• Update nameservers if using different DNS provider
• Set up subdomain forwarding separately

Namecheap

Setup URL forwarding:

1. Log in to Namecheap account
2. Go to "Domain List"
3. Click "Manage" next to domain
4. Select "Redirect Domain" tab

Configure:

• Redirect type:
  • URL Redirect
  • Permanent Redirect (301) or Temporary Redirect (302)
• Source URL: http:// (select protocol)
• Destination URL: https://destination.com
• Optional: Enable "Do not redirect www" if only forwarding root

5. Save changes
6. Wait 30 minutes for propagation

Note: Namecheap forwarding only works when using their BasicDNS or PremiumDNS nameservers.

Cloudflare

Setup forwarding via Page Rules:

1. Log in to Cloudflare
2. Select domain
3. Go to "Rules" → "Page Rules"
4. Create Page Rule

Configure:

• URL pattern: forwarded-domain.com/*
• Setting: Forwarding URL
• Status code: 301 (Permanent) or 302 (Temporary)
• Destination URL: https://destination.com/$1

5. Save and deploy

Note: Page Rules are limited (3 free, more with paid plans)

Alternative using Bulk Redirects (better):

1. Go to "Rules" → "Redirect Rules"
2. Create new rule
3. Configure:
   • When incoming requests match: http.host eq "forwarded-domain.com"
   • Then: Dynamic redirect
   • Expression: concat("https://destination.com", http.request.uri.path)
   • Status code: 301

Google Domains (transitioning to Squarespace)

Note: Google Domains sold to Squarespace. If you haven't migrated yet:

Setup forwarding:

1. Log in to Google Domains
2. Click domain
3. Go to "Website" section
4. Select "Forward to an existing webpage"
5. Enter destination URL
6. Choose redirect type:
   • Permanent redirect (301)
   • Temporary redirect (302)
7. Advanced options:
   • Forward path
   • Enable SSL

After migrating to Squarespace: Follow Squarespace domain forwarding process (similar interface).

Network Solutions

Setup forwarding:

1. Log in to Network Solutions account
2. Go to "My Domain Names"
3. Click "Manage" next to domain
4. Select "Redirect/Forward Domain"
5. Configure:
   • Destination URL: https://destination.com
   • Type: Permanent or Temporary
6. Save settings
7. Confirm when prompted

Hover

Setup forwarding:

1. Log in to Hover
2. Click domain name
3. Go to "Forward" tab
4. Enter destination URL
5. Choose redirect type:
   • 301 (Permanent)
   • 302 (Temporary)
6. Save changes

Additional: Hover supports path forwarding by default.

Domain.com

Setup forwarding:

1. Log in to Domain.com account
2. Go to "My Domains"
3. Click domain to manage
4. Select "Forwarding" in left menu
5. Configure:
   • Forward to URL: https://destination.com
   • Type: Permanent (301) or Temporary (302)
   • Options:
     • Forward all traffic
     • Mask URL (avoid)
6. Save settings

Advanced Forwarding Options

Beyond basic redirects—complex scenarios and solutions.

Path Preservation

Scenario: Preserve specific paths when forwarding.

Example:

Desired behavior:
forwarded.com/about → destination.com/about
forwarded.com/contact → destination.com/contact
forwarded.com/products/item1 → destination.com/products/item1

Setup:

Apache .htaccess:

RewriteEngine On
RewriteCond %{HTTP_HOST} ^(www\.)?forwarded\.com$ [NC]
RewriteRule ^(.*)$ https://destination.com/$1 [R=301,L]

Nginx:

server {
    server_name forwarded.com www.forwarded.com;
    return 301 https://destination.com$request_uri;
}

Registrar forwarding: Enable "Path forwarding" or "Wildcard forwarding" option if available.

Query String Preservation

Scenario: Preserve URL parameters.

Example:

forwarded.com?utm_source=email&utm_campaign=summer
→ destination.com?utm_source=email&utm_campaign=summer

Setup:

Apache .htaccess:

RewriteEngine On
RewriteCond %{HTTP_HOST} ^(www\.)?forwarded\.com$ [NC]
RewriteRule ^(.*)$ https://destination.com/$1 [R=301,QSA,L]

Note: QSA flag = Query String Append

Nginx:

server {
    server_name forwarded.com;
    return 301 https://destination.com$request_uri;
}

Note: $request_uri includes query string automatically

Conditional Redirects

Scenario: Different redirects based on conditions.

Example 1: Redirect based on path

forwarded.com/blog/* → destination.com/blog/*
forwarded.com/* (everything else) → destination.com/

Apache:

RewriteEngine On
RewriteCond %{HTTP_HOST} ^forwarded\.com$ [NC]
RewriteRule ^blog/(.*)$ https://destination.com/blog/$1 [R=301,L]
RewriteRule ^(.*)$ https://destination.com/ [R=301,L]

Example 2: Redirect based on device

Mobile: forwarded.com → m.destination.com
Desktop: forwarded.com → www.destination.com

Apache:

RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} "android|iphone|ipad|mobile" [NC]
RewriteRule ^(.*)$ https://m.destination.com/$1 [R=302,L]
RewriteRule ^(.*)$ https://www.destination.com/$1 [R=302,L]

Example 3: Geographic redirect

US visitors: forwarded.com → destination.com/us
UK visitors: forwarded.com → destination.com/uk
Others: forwarded.com → destination.com

Requires server-side GeoIP lookup (advanced setup).

Wildcard Subdomain Forwarding

Scenario: Forward all subdomains.

Example:

*.forwarded.com → destination.com
or
*.forwarded.com → *.destination.com

DNS setup:

Type: A
Name: *
Value: [server IP]

Apache (forward all to root):

RewriteEngine On
RewriteCond %{HTTP_HOST} ^.*\.forwarded\.com$ [NC]
RewriteRule ^(.*)$ https://destination.com/$1 [R=301,L]

Apache (preserve subdomain):

RewriteEngine On
RewriteCond %{HTTP_HOST} ^(.*)\.forwarded\.com$ [NC]
RewriteRule ^(.*)$ https://%1.destination.com/$1 [R=301,L]

Nginx (forward all to root):

server {
    server_name *.forwarded.com;
    return 301 https://destination.com$request_uri;
}

HTTPS/SSL Considerations

Scenario: Forwarding with SSL certificates.

Challenge: SSL certificate needed for forwarded domain to avoid browser warnings.

Solutions:

Option 1: Registrar forwarding

• Most registrars handle SSL automatically
• Free SSL on forwarding service
• No configuration needed

Option 2: Cloudflare

• Free SSL certificates for all domains
• Automatic HTTPS redirects
• Enable "Always Use HTTPS"

Option 3: Let's Encrypt

• Free SSL certificates
• Install on your server
• Configure for both domains

Option 4: Redirect HTTP to destination HTTPS

Apache:

<VirtualHost *:80>
    ServerName forwarded.com
    Redirect 301 / https://destination.com/
</VirtualHost>

Visitors won't see SSL warning because redirect happens at HTTP level.

Subdomain Forwarding

Forward specific subdomains to different destinations.

Single Subdomain Forward

Scenario: Forward blog.forwarded.com to main site blog.

Example:

blog.forwarded.com → destination.com/blog

Setup at registrar (if supported):

1. Add subdomain forward rule
2. Source: blog.forwarded.com
3. Destination: https://destination.com/blog
4. Type: 301

Setup via DNS + server:

DNS:

Type: A
Name: blog
Value: [server IP]

Apache:

<VirtualHost *:80>
    ServerName blog.forwarded.com
    Redirect 301 / https://destination.com/blog/
</VirtualHost>

Nginx:

server {
    server_name blog.forwarded.com;
    return 301 https://destination.com/blog$request_uri;
}

Multiple Subdomain Forwards

Scenario: Different subdomains to different destinations.

Example:

blog.forwarded.com → destination.com/blog
shop.forwarded.com → shop.destination.com
support.forwarded.com → help.destination.com

DNS:

blog.forwarded.com     A    [server IP]
shop.forwarded.com     A    [server IP]
support.forwarded.com  A    [server IP]

Apache:

<VirtualHost *:80>
    ServerName blog.forwarded.com
    Redirect 301 / https://destination.com/blog/
</VirtualHost>

<VirtualHost *:80>
    ServerName shop.forwarded.com
    Redirect 301 / https://shop.destination.com/
</VirtualHost>

<VirtualHost *:80>
    ServerName support.forwarded.com
    Redirect 301 / https://help.destination.com/
</VirtualHost>

Nginx:

server {
    server_name blog.forwarded.com;
    return 301 https://destination.com/blog$request_uri;
}

server {
    server_name shop.forwarded.com;
    return 301 https://shop.destination.com$request_uri;
}

server {
    server_name support.forwarded.com;
    return 301 https://help.destination.com$request_uri;
}

Email Forwarding

Forward emails from one domain to another (separate from web forwarding).

Email Forwarding vs Domain Forwarding

Important: Domain/URL forwarding does NOT affect email.

Example:

Web forwarding: olddomain.com → newdomain.com (website redirects)
Email: Email to [email protected] needs separate setup

To handle email during domain forwarding:

Option 1: Set up email forwarding

• Forward [email protected] → [email protected]
• Requires MX records for forwarded domain
• Registrar email forwarding or email hosting provider

Option 2: Migrate email completely

• Move all email accounts to destination domain
• Update MX records
• Notify users of new email addresses

Option 3: Use email alias

• Keep email on original provider
• Add alias addresses for both domains

Setting Up Email Forwarding

At registrar (if supported):

1. Navigate to email settings for domain
2. Select "Email Forwarding"
3. Add forwarding rule:
   • From: [email protected]
   • To: [email protected]
4. Update MX records (usually automatic)
5. Verify forwarding works (send test email)

Using Google Workspace:

1. Add domain alias in Google Workspace admin
2. Verify domain ownership
3. Update MX records to Google
4. Enable catch-all forwarding or specific addresses

Using Cloudflare Email Routing (free):

1. Go to Email → Email Routing in Cloudflare
2. Enable Email Routing
3. Add destination addresses
4. Create forwarding rules
5. Verify email address
6. Update MX records (provided by Cloudflare)

Using ImprovMX (free forwarding):

1. Visit improvmx.com
2. Add your domain
3. Update MX records:

   Priority 10: mx1.improvmx.com
   Priority 20: mx2.improvmx.com
   

4. Create email aliases
5. Verify with test email

Important: Web forwarding and email forwarding are configured separately.

Troubleshooting Forwarding Issues

Common problems and solutions.

Redirect Not Working

Symptoms:

• Domain doesn't redirect
• Shows registrar parking page
• Shows error page

Causes and solutions:

1. DNS propagation not complete

• Wait: 24-48 hours for DNS changes to propagate globally
• Test: Use whatsmydns.net to check propagation
• Solution: Be patient; avoid making multiple changes

2. Incorrect nameservers

• Check: Verify domain using correct nameservers
• WHOIS lookup: Confirm NS records match forwarding provider
• Solution: Update nameservers if using custom DNS

3. Caching

• Browser cache: Stored old redirect
• Solution:
  • Clear browser cache
  • Test in incognito/private mode
  • Try different browser

4. Forwarding not enabled

• Check: Verify forwarding activated in registrar control panel
• Solution: Re-save forwarding settings; wait 15 minutes

5. Conflicting DNS records

• Issue: A records or other DNS records conflict with forwarding
• Solution: Remove conflicting records, keep only forwarding config

Redirect Chain or Loop

Symptoms:

• Browser shows "redirect loop" error
• Page never loads
• Too many redirects error

Causes:

1. Circular redirect

domain-a.com → domain-b.com
domain-b.com → domain-a.com
(Infinite loop)

Solution: Remove one redirect; choose final destination

2. www and non-www loop

example.com → www.example.com
www.example.com → example.com
(Infinite loop)

Solution: Choose one canonical version; redirect other to it

3. HTTPS redirect loop

HTTP → HTTPS (server config)
HTTPS → HTTP (registrar forwarding)
(Infinite loop)

Solution: Ensure all redirects go to same protocol (HTTPS)

4. Multiple redirect layers

domain-a.com → domain-b.com → domain-c.com → final.com

Solution: Redirect directly to final destination (avoid redirect chains)

SSL Certificate Errors

Symptoms:

• "Not Secure" warning
• Certificate error
• SSL handshake failed

Causes and solutions:

1. No SSL certificate on forwarded domain

• Solution:
  • Use registrar forwarding (usually includes SSL)
  • Use Cloudflare (free SSL)
  • Install Let's Encrypt certificate

2. Certificate name mismatch

• Certificate for destination.com used on forwarded.com
• Solution: Get certificate covering both domains or use proper forwarding service

3. Mixed HTTP/HTTPS

• HTTP redirect to HTTPS destination
• Solution: Acceptable—no warning because redirect happens before SSL

Best practice: Use HTTPS for forwarding destination

Path Not Preserved

Symptoms:

Visiting: forwarded.com/about
Ends up at: destination.com (not destination.com/about)
Path lost

Causes and solutions:

1. Path forwarding disabled

• Solution: Enable "wildcard forwarding" or "path forwarding" in registrar settings

2. Server redirect doesn't include path

Apache fix:

# Wrong (loses path):
Redirect 301 / https://destination.com/

# Right (preserves path):
RewriteRule ^(.*)$ https://destination.com/$1 [R=301,L]

Nginx fix:

# Wrong (loses path):
return 301 https://destination.com/;

# Right (preserves path):
return 301 https://destination.com$request_uri;

Slow Redirect

Symptoms:

• Redirect takes several seconds
• Delay before reaching destination

Causes:

1. DNS lookup time

• Slow DNS resolution
• Solution: Use faster DNS provider (Cloudflare, Google DNS)

2. Multiple redirects

• Chain of redirects
• Solution: Redirect directly to final destination

3. Meta refresh delay

<meta http-equiv="refresh" content="5;url=https://destination.com">
(5 second delay)

• Solution: Use server-side 301/302 redirect instead

4. JavaScript redirect

• Client-side redirect slower
• Solution: Use server-side redirect

Best performance: Single server-side 301 redirect

SEO Impact of Redirects

How forwarding affects search engine rankings.

301 Redirect SEO Impact

Link equity transfer:

• 301 redirects pass 90-99% of link equity (PageRank)
• Effectively same as if destination URL was originally linked
• Preserves backlink value

Search engine behavior:

• Google eventually replaces old URL with new URL in index
• May take weeks to months for full migration
• Redirects should remain in place indefinitely (minimum 1 year)

Best practices:

1. Use 301 for permanent changes

• Rebranding
• Domain consolidation
• Site restructuring

2. Keep redirects in place long-term

• Minimum 1 year
• Permanently if possible
• Search engines need time to transfer signals

3. Update internal links

• Don't rely on redirects for your own internal links
• Update to point directly to destination
• Reduces redirect dependency

4. Submit new URLs to search engines

• Google Search Console
• Bing Webmaster Tools
• Request indexing of new URLs

5. Update external links where possible

• Contact high-value backlink sources
• Request update to new URLs
• Not required but helpful

302 Redirect SEO Impact

Link equity:

• 302 redirects do NOT pass link equity
• Original URL retains ranking
• New URL doesn't benefit from backlinks

When search engines see 302:

• Keep original URL in index
• May occasionally check if redirect changed
• Don't transfer ranking signals

Use 302 when:

• Redirect is actually temporary
• You plan to reverse it
• Testing or A/B testing
• Seasonal or campaign redirects

Don't use 302 when:

• Change is permanent
• You want SEO value to transfer
• Rebranding or domain consolidation

Common SEO Mistakes

Mistake 1: Using 302 instead of 301

Scenario: Rebranded from old-name.com to new-name.com
Wrong: 302 redirect
Right: 301 redirect
Impact: SEO value doesn't transfer; rankings stay with old domain

Mistake 2: Redirect chains

domain-a.com → domain-b.com → domain-c.com
Impact: Each redirect loses small amount of link equity; slower page load
Solution: Redirect directly to final destination

Mistake 3: Removing redirects too soon

Set up 301 redirect, remove after 3 months
Impact: Search engines haven't fully migrated; lose rankings
Solution: Keep redirects for 1+ years minimum

Mistake 4: Domain masking

Using frame/iframe to hide destination
Impact: Search engines see frame, not content; SEO disaster
Solution: Use proper 301 redirect instead

Mistake 5: Not updating sitemap

Old sitemap still lists old URLs
Impact: Confuses search engines
Solution: Update sitemap.xml with new URLs

Monitoring SEO During Migration

Track in Google Search Console:

1. Add both domains (old and new)
2. Monitor crawl stats on old domain
3. Watch for 301s in Coverage report
4. Track impressions shifting from old to new
5. Monitor position for key terms

What to expect:

Week 1-2:

• Redirects detected
• Google begins crawling new domain
• Rankings may fluctuate

Month 1-2:

• Gradual migration of rankings
• New domain starts appearing in results
• Traffic shifting to new domain

Month 3-6:

• Majority of migration complete
• Most rankings transferred
• Old domain rarely shown

Month 6-12:

• Migration essentially complete
• Can consider removing redirects (though not recommended)

Red flags:

• No ranking transfer after 3 months
• Significant traffic drop
• New domain not indexed

Troubleshooting:

• Verify 301 redirect working correctly
• Check robots.txt doesn't block new domain
• Ensure new domain indexed in Search Console
• Submit new sitemap

Forwarding Best Practices

Follow these best practices for reliable, effective forwarding.

Planning Your Forwarding Strategy

Before setting up forwarding:

1. Identify primary domain

• Choose your canonical domain
• All others forward to this one
• Be consistent

2. Decide redirect type

• Permanent change = 301
• Temporary = 302
• When in doubt, use 301 for domain forwarding

3. Map all domains

• List all domains you own
• Determine which forward where
• Document the strategy

4. Consider email

• Plan email forwarding separately
• Decide email migration strategy
• Test email delivery

5. Test before deploying

• Set up on staging/test domain first
• Verify behavior
• Then deploy to production

Technical Best Practices

1. Use HTTPS for destination

✓ https://destination.com (secure)
✗ http://destination.com (insecure)

2. Include www handling

Forward both:
- forwarded.com → destination.com
- www.forwarded.com → destination.com

3. Preserve query strings

• Enable if destination uses URL parameters
• Important for marketing campaigns (UTM parameters)

4. Avoid redirect chains

✗ a.com → b.com → c.com (chain)
✓ a.com → c.com (direct)
✓ b.com → c.com (direct)

5. Use registrar forwarding when possible

• Simpler than DNS + server config
• Free SSL included
• Easier to manage

6. Document your redirects

• Keep list of what forwards where
• Document redirect type
• Note when set up and why

Monitoring and Maintenance

Regular checks:

Monthly:

• Verify redirects still working
• Test in multiple browsers
• Check redirect type correct
• Monitor for any errors

Quarterly:

• Review all forwarding rules
• Remove unnecessary redirects
• Verify SSL certificates valid
• Check for redirect chains

After changes:

• Test immediately after setup
• Verify with curl or redirect checker
• Test from different locations
• Monitor Search Console

Use monitoring tools:

• DomainDetails Pro tracks domain DNS changes
• Uptime monitoring (UptimeRobot, Pingdom)
• Search Console for SEO impact
• Analytics for traffic patterns

Security Considerations

1. Keep transfer locks enabled

• Enable after setting up forwarding
• Prevents unauthorized transfer
• See Domain Theft Prevention

2. Monitor for unauthorized changes

• Watch for redirect modifications
• Track DNS changes
• Enable domain monitoring

3. Use HTTPS

• Secure destination URLs
• Prevents man-in-the-middle attacks
• Better SEO

4. Verify registrar account security

• Strong password
• Two-factor authentication
• Regular login monitoring

Frequently Asked Questions

Can I forward a domain without hosting?

Yes. URL forwarding via registrar doesn't require hosting.

How it works:

• Registrar provides forwarding service
• No website hosting needed
• Just configure forwarding in registrar control panel

What you need:

• Domain registered
• Destination URL (where to forward to)
• Registrar that offers forwarding (most do)

Limitations:

• Basic forwarding only (no custom logic)
• May not support all advanced features
• Depends on registrar's service

What's the difference between forwarding and pointing?

Forwarding (HTTP redirect):

• Browser redirected to new URL
• Address bar shows destination
• Requires no hosting for forwarded domain

Pointing (DNS A record):

• Both domains point to same server IP
• Server decides what to show
• Address bar can show original domain
• Requires hosting

When to use which:

• Forwarding: Simple redirect, no hosting
• Pointing: Same content on multiple domains, have hosting

Will forwarding work with email?

No, domain forwarding does not affect email.

Web forwarding:

• Redirects web traffic (HTTP/HTTPS)
• Browser-based

Email forwarding:

• Separate configuration
• Uses MX records
• Set up separately in registrar or email provider

To forward both:

1. Set up web forwarding (for website)
2. Set up email forwarding separately (for email)

How long does it take for forwarding to work?

Typical timeframes:

Using registrar forwarding:

• Configuration: 2-5 minutes
• Propagation: 15 minutes - 2 hours
• Full global propagation: Up to 48 hours

Using DNS + server:

• DNS changes: 30 minutes - 48 hours (depends on TTL)
• Server config: Immediate after DNS resolves

Factors affecting speed:

• DNS TTL (time to live) settings
• DNS provider propagation speed
• Browser caching
• ISP DNS caching

Speed it up:

• Lower DNS TTL before making changes
• Use fast DNS provider (Cloudflare)
• Clear browser cache when testing

Can I forward to a subdirectory?

Yes, you can forward to any URL, including subdirectories.

Example:

forwarded.com → destination.com/landing-page
campaign.com → main-site.com/special-offer

Setup:

• Use full URL as destination
• Most registrars support this
• Works with any path

Advanced: Preserve path while forwarding to subdirectory

forwarded.com/about → destination.com/landing/about
forwarded.com/contact → destination.com/landing/contact

Requires server-side configuration (not available in basic registrar forwarding).

Does domain forwarding hurt SEO?

It depends on the redirect type:

301 redirect (permanent): ✓ Does NOT hurt SEO ✓ Transfers 90-99% of link equity ✓ Properly migrates rankings ✓ Recommended for permanent forwarding

302 redirect (temporary): ⚠️ Doesn't transfer SEO value ⚠️ Original URL keeps rankings ⚠️ Fine for temporary use ⚠️ Wrong choice for permanent forwarding

Domain masking: ✗ VERY bad for SEO ✗ Search engines see frame, not content ✗ Doesn't pass link equity ✗ Never use for SEO

Best practice: Use 301 redirects for permanent domain forwarding to preserve SEO.

Can I forward multiple domains to one destination?

Yes, this is very common.

Example:

business.com (primary)
business.net → business.com (301)
business.org → business.com (301)
business.io → business.com (301)
thebusiness.com → business.com (301)

Benefits:

• Consolidates SEO value
• Protects brand variations
• All traffic to one site
• Easier to manage

Setup:

• Configure each domain separately
• All forward to same destination
• Use 301 redirects

No limit: Forward as many domains as you own to single destination.

What happens to old backlinks when I forward?

With 301 redirect:

Backlinks preserved:

• Links still work (redirect to new domain)
• Link equity transfers to new domain
• Rankings migrate to new domain
• Backlinks remain valuable

What happens:

External site links to: old-domain.com/page
User clicks link
Browser redirects to: new-domain.com/page
Search engines credit link to new domain

Best practices:

• Keep 301 redirects permanent
• Don't break old URLs
• Update backlinks where possible (but not required)

With 302 redirect:

• Links work but don't transfer value
• Original domain keeps SEO value
• Not ideal for permanent changes

Can I cancel or change a forward?

Yes, you can change or remove forwarding anytime.

To change destination:

1. Log into registrar
2. Update forwarding URL
3. Save changes
4. Wait for propagation (15 min - 2 hours)

To remove forwarding:

1. Delete forwarding rule in registrar
2. Configure domain for new use (hosting, parking, etc.)
3. Wait for DNS propagation

SEO considerations:

• Removing 301 redirect can lose rankings
• Change destination carefully
• Keep redirects in place long-term

No penalty: Changing destination or removing forward won't penalize you, but may lose ranking transfer progress.

How do I test if my redirect is working?

Method 1: Browser test

1. Open incognito/private window
2. Type: forwarded-domain.com
3. Press Enter
4. Verify: Redirects to destination
5. Check address bar shows destination

Method 2: Command line (curl)

curl -I http://forwarded-domain.com

# Look for:
HTTP/1.1 301 Moved Permanently
Location: https://destination.com

Method 3: Online tools

• redirect-checker.org
• httpstatus.io
• seoreviewtools.com/redirect-checker

What to verify:

• Redirects to correct destination
• Uses correct redirect type (301 or 302)
• Works with and without www
• Preserves path (if configured)
• Works for HTTPS

Test multiple scenarios:

• http://domain.com
• https://domain.com
• http://www.domain.com
• https://www.domain.com
• domain.com/page (if path forwarding)

Key Takeaways

Next Steps

Set Up Your Domain Forwarding:

1. Choose your primary domain
2. Configure forwards at your registrar for alternate domains
3. Test redirects to verify proper configuration
4. Set up email forwarding separately if needed

Learn More:

1. Point domain to website: How to Point Your Domain to a Website
2. Change nameservers: How to Change Domain Nameservers
3. Understand DNS: What is DNS and How Does It Work?
4. Monitor your domains: How to Monitor Domain Changes: WHOIS & DNS Tracking

Additional Resources:

• DomainDetails Lookup: Check your domain configuration
• Knowledge Base: Browse all articles
• Support: Contact us

Research Sources

This guide is based on industry standards and best practices:

1. HTTP Status Codes: RFC 7231 - Hypertext Transfer Protocol (HTTP/1.1)
2. DNS Standards: RFC 1035 - Domain Names - Implementation and Specification
3. SEO Best Practices: Google Search Central documentation
4. Redirect Performance: Web Performance Working Group guidelines
5. Registrar Practices: Analysis of major registrar forwarding implementations
6. DomainDetails Experience: Based on analyzing 100,000+ domain configurations