Namecheap Redirect Domain Guide to Fix Namecheap Redirect Not Working 2026 Easily

Log in to Namecheap and go to Domain List in the left-hand dashboard menu. You'll see every domain you own with its status, auto-renew setting, and expiration date, and a Manage button on the right side of each row. Click Manage on the domain whose redirect isn't working — that takes you into the domain's full settings page, which is where nameservers, DNS records, and the redirect tool all live together.

Scroll to the Nameservers section on the domain's management page. If it shows Custom DNS with values like ns1.dns-parking.com and ns2.dns-parking.com, that's very likely why forwarding isn't working — Namecheap's page spells this out directly next to Redirect Domain and Redirect Email, noting you must first change your nameservers to Namecheap default before those functions will run. Custom or third-party nameservers hand DNS resolution off to another provider entirely, so Namecheap's redirect tool has no way to intercept the traffic.

Open the Nameservers dropdown and select Namecheap BasicDNS (or Namecheap PremiumDNS if you already own that add-on). This tells Namecheap to handle DNS resolution itself, which unlocks the Redirect Domain section that was previously grayed out with an explanatory note. Give the change a little time to propagate — nameserver updates aren't instant — before assuming the redirect still isn't taking effect.

With BasicDNS active, the Redirect Domain section becomes a working form: a Source URL column showing your domain, and a Destination URL field where you type the full address you want visitors sent to, including the http:// or https:// prefix. Click Add Redirect if there isn't an entry yet, type the destination, and confirm it. In the example shown here, the domain forwards to its own www version — the same mechanism works identically for sending visitors to a completely different domain.

Namecheap's basic redirect tool applies a standard forward rather than exposing a dropdown for redirect type on every plan, but the distinction still matters conceptually: a 301 tells browsers and search engines the move is permanent and transfers SEO value to the destination, while a 302 signals a temporary change that doesn't pass that value along. If you need explicit control over which type fires, that's typically configured at the DNS or hosting level rather than in the basic domain forwarding panel, so factor that into your choice of redirect method if SEO continuity matters.

If the redirect still doesn't fire after nameservers are correct, check the Advanced DNS tab for leftover A records or CNAME entries pointing your root domain or www subdomain somewhere else. A stray A record pointing at an old host will often win out over the redirect rule, since browsers resolve DNS records directly rather than going through Namecheap's forwarding logic. Delete anything that conflicts with the destination you've set, then retest in a fresh incognito window to rule out cached results from before the fix.