Point a Namecheap domain at a builder or host without breaking mail

You bought a .com at Namecheap. Somewhere else — a website builder, a brochure host, or a developer’s server — is ready to show a page. The remaining job is DNS: telling the internet that this name should resolve to that page, without destroying email that already works. This is the step that makes competent adults feel stupid. It is also the step that, done calmly, takes less time than a supply run.

We are not Namecheap support and we are not your builder’s support. When their documentation disagrees with a blog, use their documentation. What follows is the model in your head so those docs make sense. Wrong model: “move the domain to the host.” Right model: “keep the domain at the registrar, point only the records the website needs, and do not touch mail records unless you intend to move mail.”

Keep the name at Namecheap

A domain transfer is a change of registrar. It is slow, it can lock the name, and it is almost never required to launch a site. Hosts ask you to transfer because it makes you stickier, not because DNS needs it. Decline the transfer unless you have a specific, named reason (you are leaving Namecheap entirely, and you have time). Pointing is enough.

You will see two common pointing methods. Nameservers: you tell Namecheap to use the builder or host’s nameservers, and that company becomes the DNS boss for the whole name. Records: you keep Namecheap’s nameservers and you create A, AAAA, CNAME, and maybe ALIAS records that send www and the root to the site. Both work. Records are safer when mail already lives somewhere else, because you are less likely to overwrite MX by switching the whole DNS boss.

Ask the builder for the exact records

Do not guess IP addresses from a forum post. Open the builder or host’s “connect a domain” screen and copy what they show you today. Typical patterns: an A record for @ (the root) to an IPv4 address; a CNAME for www to a hostname they provide; sometimes a second AAAA for IPv6. Some builders want you to change nameservers to a pair of names like ns1.example.net. That is a nameserver change, not an A record. Do one method, not both stacked on top of each other.

If the builder also offers email, decide whether you want that mailbox before you accept their nameservers. Accepting their nameservers often means their DNS templates, which often means their MX. If you already receive mail at Google Workspace or Microsoft 365, changing nameservers without copying MX, SPF, DKIM, and DMARC is how invoices bounce on Monday. Prefer keeping Namecheap DNS and adding only the website records when mail is already working elsewhere.

MX is mail. Do not “clean up” MX by accident.

MX records say where mail for you@yourdomain.com should be delivered. They are unrelated to whether the website loads. People break mail because a host’s “reset DNS to defaults” button replaces MX with the host’s own mail product, or because they delete records that look unfamiliar. Unfamiliar is not unused. If you see records that mention google, outlook, protection.outlook, or a DKIM selector, leave them alone unless you are migrating mail on purpose.

SPF, DKIM, and DMARC are text records that help mailboxes trust your domain. You do not need to become an email engineer to launch a brochure. You do need to not delete them. If you do not have professional email on the domain yet, you can launch the website first and add mail later. Adding mail later is a controlled change. Destroying mail as a side effect of a website launch is an emergency.

Save, wait, then test on a phone that is not yours

DNS changes are not instant. TTL (time to live) is how long the internet remembers the old answer. After you save records, wait. Then test: the root name, www, and — if you use it — the exact URL on your cards. Test on cellular, not only on the shop Wi-Fi. Confirm the padlock. If you see the old site, you may be seeing cached DNS. Wait longer before you start deleting records in a panic.

If nothing resolves after a few hours, check for typos, check that you did not mix nameserver mode with leftover A records from a previous host, and check that the builder finished issuing HTTPS. A missing padlock is often the builder still provisioning a certificate, not a failed domain purchase. Do not buy a novelty SSL seal from a sidebar ad. The padlock comes from the place that hosts the page.

www and the bare domain should agree

Pick one canonical host — either https://example.com or https://www.example.com — and let the other redirect. Builders usually offer this as a toggle. Split brains (www shows the new site, the bare name shows a registrar parking page) look amateur and confuse Google Business Profile. Fix it with the builder’s redirect plus the matching DNS records, not with a third-party “SEO redirect” product.

Once the page loads with a padlock on a stranger’s phone, you are done with DNS for month one. Do not “optimize” TTL, do not add extra CNAMEs from a blog, and do not transfer the name to the host as a victory lap. The name stays at Namecheap. The page lives where you publish it. Mail lives where the MX says. Those three facts, kept separate, are the whole skill.

When to stop and call the builder instead of us

If the builder’s connect-domain wizard fails after you have entered the records they displayed, that is their ticket, not a Namecheap domain defect and not a Shopfront Stack defect. Send them a screenshot of the DNS you entered. If Namecheap’s dashboard will not save a record, that is Namecheap support. We can correct our explanation if we got a label wrong. We cannot click the buttons in your account. Keeping that boundary honest is part of not impersonating the brand.

You pointed a name you own at a page you control, and you did not take mail down to do it. That is a professional result. The next temptation will be plugins, extra pages, and a blog nobody will write. Resist it for a week. Make sure the phone number on the page is correct. Then, if you still want a more complicated stack, you will at least be complicating a site that already answers the phone.