Namecheap URL Redirect and Domain Forwarding Guide

Namecheap provides built-in URL redirect and domain forwarding features that work without a hosting plan. You can redirect your root domain, subdomains, or specific paths to any destination URL. The feature set is more capable than many registrars offer, but there are limitations you should know about before relying on it for anything complex. This guide covers every Namecheap redirect method with step-by-step setup. For background on redirect mechanics, see URL Forwarding Explained.

URL Redirect Record

Namecheap's URL Redirect Record is the primary way to set up redirects through their DNS panel. It works by pointing your domain to Namecheap's web redirect servers, which then issue an HTTP redirect to your destination URL.

Setting Up a URL Redirect Record

1. Log into your Namecheap account and go to Domain List.
2. Click Manage next to the domain you want to redirect.
3. Go to the Advanced DNS tab.
4. Click Add New Record.
5. Select URL Redirect Record from the record type dropdown.
6. In the Host field, enter @ for the root domain or a subdomain name like www or blog.
7. In the Value field, enter the full destination URL (e.g., https://newdomain.com).
8. Choose Unmasked or Masked redirect.
9. Save the record.

The redirect typically activates within a few minutes, though full DNS propagation can take longer if you recently changed nameservers.

Unmasked vs Masked Redirects

Unmasked redirect is a standard HTTP redirect. The browser's address bar updates to show the destination URL. This is what you want in almost every case. Namecheap sends a 301 permanent redirect for unmasked redirects by default.

Masked redirect loads the destination URL inside an HTML frame while keeping your domain in the address bar. The visitor sees your domain, but the content comes from the destination. This causes the same problems as any iframe-based approach: search engines cannot index the content properly, JavaScript-heavy sites break, security headers block the frame, and deep links do not work. Avoid masked redirects unless you have a very specific reason.

Permanent vs Temporary

Namecheap's URL Redirect Record sends a 301 (Permanent) redirect by default for unmasked redirects. If you need a 302 (Temporary) redirect, you must use the "Temporary URL Redirect Record" type, which appears as a separate option in the record type dropdown on some account configurations.

The distinction matters for SEO. A 301 tells search engines to transfer ranking signals to the destination and remove the old URL from their index. A 302 tells search engines the redirect is temporary and to keep the old URL. For most domain forwarding scenarios, 301 is correct. See 301 vs 302 Redirects for the full comparison.

Domain-Level Forwarding

In addition to URL Redirect Records in the DNS panel, Namecheap offers domain-level forwarding through the domain management interface:

1. Go to Domain List and click Manage on your domain.
2. Look for the Redirect Domain section (sometimes under "Domain" tab).
3. Enter the destination URL.
4. Choose permanent or temporary redirect.
5. Save.

This method configures the same underlying redirect but through a different interface. The result is identical: Namecheap's servers respond to requests for your domain with an HTTP redirect to the destination.

Redirecting Subdomains

You can set up URL Redirect Records for individual subdomains. Each subdomain can have its own destination:

| Host | Type | Destination | |------|------|-------------| | @ | URL Redirect Record | https://newsite.com | | www | URL Redirect Record | https://newsite.com | | blog | URL Redirect Record | https://medium.com/@yourname | | shop | URL Redirect Record | https://yourstore.shopify.com |

Set up the @ (root domain) and www separately. Namecheap does not automatically redirect both when you configure one.

Conditional Forwarding

Namecheap's BasicDNS and PremiumDNS do not support conditional redirects (redirecting based on the visitor's country, device, or other request properties). The redirect is the same for every visitor.

If you need conditional routing, you need a hosting plan or a service like Cloudflare that sits in front of your domain and can evaluate conditions before redirecting. See the Cloudflare Redirect Guide for an alternative approach.

Path-Based Redirects

Namecheap's URL Redirect Records work at the host level, not the path level. You can redirect example.com or blog.example.com, but you cannot redirect example.com/old-page to example.com/new-page through the DNS panel alone.

For path-level redirects, you need one of these alternatives:

• Web hosting with server-level redirect rules (.htaccess for Apache, nginx.conf for Nginx). See the htaccess Redirect Guide.
• A CDN like Cloudflare with redirect rules that support path matching.
• Your application's routing layer (WordPress, Next.js, Laravel, etc.).

This is the most common limitation that catches people off guard. If you are migrating a site and need to redirect individual URLs to their new locations, Namecheap's built-in forwarding cannot do it.

URL Redirect Record vs CNAME

A URL Redirect Record and a CNAME record serve different purposes and should not be confused.

A CNAME creates a DNS alias. It points one hostname to another hostname. The browser does not see a redirect. The URL in the address bar stays the same, and the DNS resolution happens behind the scenes. CNAMEs are used to point subdomains to hosting providers, CDNs, or SaaS platforms.

A URL Redirect Record sends an HTTP redirect. The browser sees the redirect, follows it, and the URL in the address bar changes to the destination. URL redirects are used when you want the visitor to end up at a different URL entirely.

If you want blog.example.com to show content from your WordPress.com blog while keeping the URL as blog.example.com, use a CNAME (and configure your blog platform to accept the custom domain). If you want blog.example.com to send visitors to yourname.wordpress.com and show that URL in the address bar, use a URL Redirect Record.

HTTPS and SSL with Forwarding

When a visitor types https://yourforwardeddomain.com, Namecheap's redirect servers need to present a valid SSL certificate for your domain before the redirect can happen. Namecheap provides free SSL for domains using their redirect service, but the coverage depends on your DNS configuration.

If visitors see a certificate warning when accessing your forwarded domain over HTTPS, check that:

1. Your domain is using Namecheap's nameservers.
2. The URL Redirect Record is correctly configured.
3. You have waited for DNS propagation to complete.

For critical domains where HTTPS reliability is essential, consider using a hosting service or Cloudflare, which give you explicit control over the SSL certificate.

Limitations Summary

Before relying on Namecheap's forwarding, understand what it cannot do:

• No path-level redirects (only host-level).
• No wildcard forwarding for all subdomains.
• No query string passthrough (parameters from the source URL are lost).
• No conditional redirects based on visitor properties.
• No custom status codes beyond 301 and 302.
• Only works when Namecheap nameservers are active.
• No redirect rules based on regex patterns.

For simple domain-to-domain forwarding, these limitations rarely matter. For site migrations or complex redirect requirements, you need server-level or CDN-level redirect rules.

Troubleshooting

Redirect is not working. Confirm your domain uses Namecheap's nameservers. Check the Advanced DNS tab to see if the URL Redirect Record is listed. Wait for DNS propagation (up to 48 hours, though usually much faster).

Getting a DNS error. If you have both an A record and a URL Redirect Record for the same host, they may conflict. Remove the A record if you want the redirect to work. URL Redirect Records replace A/AAAA records for the specified host.

Redirect goes to the wrong destination. Check that you entered the full destination URL including the protocol (https://). Without the protocol, the redirect may not work correctly.

Masked redirect shows a blank page. The destination site is likely blocking iframe embedding with security headers. Switch to an unmasked redirect.

References

1. Namecheap Knowledgebase, "How to set up URL redirect for a domain," https://www.namecheap.com/support/knowledgebase/article.aspx/385/2049/how-to-redirect-a-url-for-a-domain/
2. Namecheap Knowledgebase, "How to set up domain forwarding," https://www.namecheap.com/support/knowledgebase/article.aspx/9677/2049/how-to-set-up-domain-forwarding/
3. IETF, "RFC 9110 - HTTP Semantics, Section 15.4: Redirection 3xx," June 2022. https://httpwg.org/specs/rfc9110.html#status.3xx