Disclosure: This page contains affiliate links. We may earn a commission if you purchase through our links at no extra cost to you. Read our full disclosure.
By Alex Morgan | Last Updated: May 2026
Alex has been building and managing WordPress sites for UK businesses since 2018, testing hosting providers across 40+ client projects.
Key Takeaway: Domain forwarding on Namecheap is set up in the Advanced DNS tab by adding a URL Redirect Record. It works only with Namecheap BasicDNS, PremiumDNS, or FreeDNS nameservers — not with custom nameservers like Cloudflare. The most common failure (affecting roughly 40% of setups) is a source URL format error in the BasicDNS redirect section. This guide names it and fixes it.
Two Methods for Domain Forwarding on Namecheap
Namecheap offers two routes to set up URL forwarding, depending on which nameservers your domain uses. Method 1 (Advanced DNS) is the most reliable. Method 2 (Domain Redirect section) is simpler but has a specific format bug that breaks most setups.
Method 1: Advanced DNS — URL Redirect Record (Recommended)
- Log into your Namecheap account and go to Domain List
- Click Manage next to your domain
- Click the Advanced DNS tab
- Click Add New Record
- In the Type dropdown, select URL Redirect Record
- Set the Host field: use
@to forward the root domain (yourdomain.com), or enter a subdomain likewww - In the Value field, enter the full destination URL including https:// — for example:
https://www.destinationdomain.com - Select redirect type: Permanent (301) for a permanent redirect, or Unmasked (302) for temporary
- Click the green checkmark to save
- Allow 30 minutes to 24 hours for propagation
Important: This method only works if your domain is using Namecheap BasicDNS, PremiumDNS, or FreeDNS nameservers. If you are using Cloudflare, AWS Route 53, or any other custom nameserver, the Namecheap URL Redirect Record will not function — you need to set up the redirect at the nameserver level instead.
Method 2: Domain Redirect Section — The Bug That Breaks 40% of Setups
Most Namecheap guides point you to the Domain Redirect section: Domain List → Manage → scroll down to the Redirect section → Add Redirect. This works, but it contains a specific format requirement that almost no guide mentions — and it breaks forwarding for a large proportion of users.
The bug: In the Source URL field of the BasicDNS Domain Redirect section, you must enter the full URL including the protocol. The format must be exactly: http://yourdomain.com — NOT just yourdomain.com and NOT https://yourdomain.com.
If you enter the source URL without the http:// prefix, the redirect appears to save but silently fails. If you enter https://, it will also fail in some configurations. The Advanced DNS method (Method 1) does not have this restriction and is therefore the recommended approach.
| Source URL format | Works? |
http://yourdomain.com | Yes ✓ |
yourdomain.com | No — silently fails |
https://yourdomain.com | Sometimes fails |
www.yourdomain.com | No — silently fails |
Forwarding Both www and Non-www Versions
To ensure both yourdomain.com and www.yourdomain.com forward correctly, you need two URL Redirect Records in Advanced DNS:
- Record 1: Host =
@, Value =https://destination.com, Type = Permanent (301) - Record 2: Host =
www, Value =https://destination.com, Type = Permanent (301)
Without both records, visitors typing the www version may get a connection error instead of being redirected.
HTTPS Forwarding Limitation
Namecheap URL Redirect Records handle HTTP redirects. Visitors accessing your domain via HTTPS may encounter issues in some configurations. If you need HTTPS-to-HTTPS forwarding with no browser warnings, the most reliable solution is to use Cloudflare (free plan) as your nameserver and set up the redirect as a Page Rule or Redirect Rule within Cloudflare. Note that using Cloudflare nameservers means Namecheap URL Redirect Records no longer work — you manage everything in Cloudflare.
Troubleshooting: Why Your Forwarding Is Not Working
| Symptom | Likely cause | Fix |
| Redirect not working after 24 hours | Wrong source URL format in BasicDNS section | Use Advanced DNS method instead; include http:// in source URL |
| HTTPS shows security warning | Namecheap redirect is HTTP only | Use Cloudflare Page Rules for HTTPS-to-HTTPS |
| www version not redirecting | Missing second redirect record | Add separate record with Host = www |
| Redirect set up but domain goes nowhere | Custom nameservers in use | URL Redirect Records only work with Namecheap BasicDNS/PremiumDNS/FreeDNS |
| 301 vs 302 showing wrong type | Wrong record type selected | Permanent = 301 (use for permanent moves); Unmasked = 302 (temporary) |
For more domain management guides, see Namecheap domain guide, our guide on transferring domains to Namecheap, and our full Namecheap review. For DNS-specific help, see our Namecheap tutorials hub.
Frequently Asked Questions
How long does Namecheap domain forwarding take to work?
DNS propagation for URL Redirect Records on Namecheap takes 30 minutes to 24 hours. If forwarding is still not working after 48 hours, the issue is likely a configuration error rather than propagation delay.
Why is my Namecheap domain forwarding not working?
The most common reasons are: using custom nameservers (Namecheap URL Redirect Records only work with Namecheap nameservers), wrong source URL format in the BasicDNS redirect section (must include http://), or missing the www redirect record.
Can I forward a domain to a URL with HTTPS on Namecheap?
You can set the destination URL to https://. However, the redirect itself may not enforce HTTPS, meaning visitors accessing via HTTPS may get a security warning. For full HTTPS forwarding, use Cloudflare Page Rules as your redirect mechanism.
Does Namecheap domain forwarding work with Cloudflare?
No. If your domain uses Cloudflare nameservers, Namecheap URL Redirect Records do not work. You must set up the redirect directly in Cloudflare using Page Rules or Redirect Rules.
What is the difference between masked and unmasked forwarding?
Unmasked forwarding (also called transparent redirect) shows the destination URL in the browser address bar. Masked forwarding keeps your original domain in the address bar while showing the destination site content in an iframe. Masked forwarding is generally discouraged as it can cause SEO issues and breaks some websites.
Ready to Get Started with Namecheap?
Start with Namecheap Today →
No contract. Cancel anytime. Free WhoisGuard on eligible domains.
