The three redirect types
Namecheap offers three URL Redirect record types: Permanent (301), Unmasked (302) and Masked, also called URL Frame. [1] They are available when the domain uses Namecheap BasicDNS, PremiumDNS or FreeDNS. [1] Namecheap's host records guide describes 301 as the permanent option and URL Frame as the one that keeps your domain visible in the browser. [2]
Google treats permanent redirects (301 and 308) as a signal to show the target URL in search results and to treat it as canonical, and says to use them when you are sure the redirect will not be reverted. Temporary redirects (302, 303, 307) keep the source URL in results. [3] Google's redirect guide does not list framing among the methods it treats as a redirect, so do not rely on masking to carry search signals to the new site.
| Type | Browser address bar | Search treatment per Google | Use it for |
|---|---|---|---|
| Permanent (301) | Shows the new domain | Target shown and favored as canonical [3] | Rebrands, moved sites, typo domains |
| Unmasked (302) | Shows the new domain | Source stays in results [3] | Short-term campaigns you will undo |
| Masked (URL Frame) | Keeps the old domain | Not a redirect method Google lists [3] | Rarely; vanity URL for a page you do not control |
Set it up in Advanced DNS
Namecheap describes two routes: an Advanced DNS record, or the Redirect Domain section on the Domain tab. [1] The Advanced DNS route is shown below because it gives you control over each host. The redirect adds a hidden A record pointing to Namecheap's forwarding server; it does not appear in Advanced DNS and is removed when you delete the redirect. [1]
- Open Domain List and click Manage next to the domain, then the Advanced DNS tab. [1]
- Delete any A, CNAME, ALIAS or older URL Redirect record on the same host; Namecheap says to remove conflicting records with different values. [1]
- Click Add New Record and choose URL Redirect Record. [1]
- Host: @ for the bare domain. Add a second record with Host www so both versions forward. [1]
- Value: the full destination address including its https prefix, for example the new site's www.newbrand.example home page. [1]
- Choose Permanent (301), Unmasked or Masked, then save. [1]
- Optional: Host * catches requests for subdomains that do not exist. [1]
- Wait around 30 minutes, then test. [1]
How it behaves over HTTPS
This is where most redirect complaints come from. Namecheap says redirects over a secure connection work only to a different destination domain, and that redirecting between two HTTPS domains requires both domains to have SSL certificates installed. [1] Redirecting from plain HTTP on your domain to a separate HTTPS website works as simple forwarding. [1]
In practice: someone typing oldbrand.example or clicking an old HTTP link is forwarded fine. Someone following an old HTTPS link to oldbrand.example needs a certificate on oldbrand.example, or the browser shows a security warning before the redirect runs. If old links were HTTPS, plan for a certificate on the old domain or a host-level redirect instead. Namecheap also says a same-domain HTTP-to-HTTPS redirect cannot be done with this record; it needs .htaccess or the SSL plugin on hosting. [1] Pointing a redirect at a plain HTTP destination can itself trigger browser warnings. [1]
| Visitor requests | Redirects to | Works with URL Redirect alone? |
|---|---|---|
| oldbrand.example (HTTP) | www.newbrand.example (HTTPS) | Yes [1] |
| oldbrand.example (HTTPS) | www.newbrand.example (HTTPS) | Only with SSL on both domains [1] |
| oldbrand.example (HTTP) | oldbrand.example (HTTPS) | No; use hosting .htaccess or SSL plugin [1] |
| Any | An HTTP destination | Works but may show browser warnings [1] |
SEO and email effects
For a permanent domain move, Google says to keep redirects for as long as possible, generally at least a year, and to consider keeping them indefinitely. [4] It recommends its Change of Address tool when moving between domains, submitted for every verified variant of the old domain, and says it can take a few weeks or more for the new URLs to appear for a medium-sized site. [4] Namecheap's article does not say whether the path is kept, such as oldbrand.example/pricing forwarding to newbrand.example/pricing, so test several deep URLs before relying on old links.
Email is separate. The redirect only adds a hidden A record for the host it is set on [1]; MX records are their own record type. [2] If people still email you at the old domain, leave its MX, SPF, DKIM and DMARC records in place. If you delete everything in the zone to tidy up, mail to the old domain stops.
Worked example: old brand domain to new brand
Scenario: you rebranded from oldbrand.example to newbrand.example, the site now lives at www.newbrand.example over HTTPS, and two colleagues still receive mail at oldbrand.example addresses through Namecheap Private Email. Target zone for oldbrand.example:
| Type | Host | Value | Purpose |
|---|---|---|---|
| URL Redirect Record, Permanent (301) | @ | www.newbrand.example over HTTPS (full https address) | Bare domain forwards [1] |
| URL Redirect Record, Permanent (301) | www | www.newbrand.example over HTTPS (full https address) | www forwards [1] |
| MX | @ | Unchanged mail server records | Old mailboxes keep receiving |
| TXT | @ | Unchanged SPF record | Old address can still send |
| TXT | _dmarc | Unchanged DMARC record | Policy stays published |
| Removed | @ and www | Previous A or CNAME records | Avoid conflicts [1] |
Test checklist
- Load oldbrand.example and www.oldbrand.example over plain HTTP in a private window; both should land on the new site.
- Run curl -I against oldbrand.example over plain HTTP and confirm the status line shows 301 for a permanent move, not 302.
- Try oldbrand.example over HTTPS; if you see a certificate warning, install a certificate on the old domain or accept the limitation. [1]
- Test three old deep links and note whether the path survives.
- Send an email to an old-domain address and confirm it arrives.
- Submit Change of Address in Search Console if the old domain was verified there. [4]
Questions before you decide
Which redirect type is best for SEO?
Google says permanent redirects (301, 308) show the new target in search results and signal that it should be canonical, while temporary redirects keep the source in results. Namecheap labels its 301 option Permanent.
How long until the redirect works?
Namecheap says a URL redirect usually starts working in around 30 minutes.
Does a URL redirect stop email on the old domain?
The redirect adds a hidden A record for the host it is on. MX records are a separate record type in Advanced DNS, so mailboxes on the old domain keep working as long as you leave the MX and authentication records in place. Namecheap's redirect article does not discuss email.
Why do I get a certificate warning when the old domain is opened over HTTPS?
Namecheap says redirecting between two HTTPS domains requires both domains to have SSL certificates installed. Without a certificate on the old domain, browsers warn before the redirect can happen.
Sources & verification
Product details and prices can change. Check the linked provider before buying.
- Namecheap Knowledgebase: How to set up a URL redirect for a domain Accessed 30 Oct 2026
- Namecheap Knowledgebase: How do I set up host records for a domain? Accessed 30 Oct 2026
- Google Search Central: Redirects and Google Search Accessed 30 Oct 2026
- Google Search Central: Site moves with URL changes Accessed 30 Oct 2026
Sources link directly to providers. Product buttons may use separately labeled affiliate links. Read our disclosure.