Point Namecheap Domain to Netlify: Custom DNS, Apex Setup, and SSL Guide

Your build passed on Netlify, but your app is still stuck on a generic quirky-curie-4921ab.netlify.app URL. You need your Namecheap domain hooked up to that deployment without dropping traffic, breaking your apex redirect, or fighting Let’s Encrypt errors.

You have two ways to wire Namecheap to Netlify: hand over your full DNS zone to Netlify DNS, or keep managing records manually inside Namecheap BasicDNS. I’ve set up dozens of production sites both ways, and each has real trade-offs around apex routing, email records, and SSL issuance.

Apex Domain Dilemma: Netlify DNS vs Namecheap BasicDNS

Before changing anything in your registrar dashboard, decide where you want your DNS zone hosted. Netlify expects different records depending on whether it manages your nameservers directly or sits behind external DNS.

Per the Netlify Custom Domains documentation, Netlify DNS gives the platform full control of your zone. It automatically runs DNS-level load balancing across its global edge, issues wildcard SSL certificates, and handles branch subdomains without manual record creation.

Namecheap BasicDNS keeps your nameservers right where they are. You manually add static A and CNAME records. Stick with this if you’re already running services like Namecheap Private Email MX records or custom TXT verifications you’d rather not migrate.

The tricky part with external DNS is the apex domain (example.com). RFC 1034 doesn’t permit a CNAME at the zone root. On Namecheap BasicDNS, you have to point your root domain to Netlify’s load balancer IP (75.2.60.5) and map www to your Netlify site URL. If you want a breakdown of how the DNS spec handles this, check our guide on configuring root domains in Namecheap DNS.

Method 1: Point Namecheap to Netlify Using Netlify DNS (Recommended)

Netlify DNS is the smoothest route for static sites, SPAs, and docs. Netlify delegates your zone to its NS1-backed nameservers, giving you automatic certificate renewals and proper edge routing out of the box.

Step 1: Add Custom Domain in Netlify

1. Head to your Netlify dashboard and click into your project.
2. Go to Site configuration > Domain management.
3. Click Add a domain and type in your root domain (like example.com).
4. Click Verify, then hit Add domain.
5. Click Set up Netlify DNS next to your domain name.
6. Click Continue past the initial DNS record review.
7. Netlify will give you four nameservers (such as dns1.p08.nsone.net through dns4.p08.nsone.net). Keep this tab open.

Step 2: Copy Netlify Nameservers to Namecheap

1. In Namecheap, go to your Domain List.
2. Find your domain and click Manage.
3. Under the Domain tab, look for the Nameservers section.
4. Switch the dropdown from Namecheap BasicDNS to Custom DNS.
5. Paste all four Netlify nameservers into lines 1 through 4.
6. Click the green checkmark icon to save.

You can confirm your nameserver delegation straight from the terminal:

dig +short NS example.com @8.8.8.8
# dns1.p08.nsone.net.
# dns2.p08.nsone.net.
# dns3.p08.nsone.net.
# dns4.p08.nsone.net.

Nameserver propagation usually takes 10 to 30 minutes, though registrar TTL caches can stretch that out longer.

Method 2: Configure External DNS Using Namecheap BasicDNS

If you’re already running business email or have subdomains pointing to external servers (like an AWS API), migrating your entire zone might break live services. In that case, keep your nameservers at Namecheap and point individual A and CNAME records to Netlify.

This is the same approach covered in our guides on pointing Namecheap domains to Vercel and pointing Namecheap domains to GitHub Pages.

Add A Record for Apex and CNAME for Subdomains

1. In Namecheap, open your Domain List > Manage.
2. Click the Advanced DNS tab.
3. Delete any default Parking Page records or old A / CNAME entries on @ and www.
4. Add an A Record with host @ pointing to Netlify’s load balancer IP: 75.2.60.5.
5. Add a CNAME Record with host www pointing to your Netlify site URL (e.g., your-site-name.netlify.app.).
6. Set TTL to Automatic or 5 min so adjustments resolve quickly.

Your Namecheap record table should look like this:

• Type: A Record | Host: @ | Value: 75.2.60.5 | TTL: Automatic
• Type: CNAME Record | Host: www | Value: your-site-name.netlify.app. | TTL: Automatic

Once saved, go back to Netlify under Domain management, register both example.com and www.example.com, and choose your primary domain.

Preserving Namecheap Private Email When Switching Nameservers

If you pick Method 1 (Netlify DNS) while using Namecheap Private Email or Google Workspace, changing your nameservers will break inbound email immediately unless you copy your MX records over first.

Before changing nameservers in Namecheap, grab your MX and TXT records from the Advanced DNS tab. Then recreate them inside Netlify under Domain management > Netlify DNS > DNS records > Add new record.

These are the default Namecheap Private Email records you’ll need to replicate in Netlify DNS:

[ { "type": "MX", "name": "@", "value": "mail.privateemail.com.", "priority": 10 }, { "type": "MX", "name": "@", "value": "mail.privateemail.com.", "priority": 10 }, { "type": "TXT", "name": "@", "value": "v=spf1 include:spf.privateemail.com ~all" }
]

Adding these before flipping the nameserver switch in Namecheap keeps your mail flowing without dropped messages.

Provision Let’s Encrypt SSL and Force HTTPS

Netlify automates TLS certificate issuance via Let’s Encrypt. Once DNS routes properly, certificate provisioning starts automatically.

1. In Netlify, open Site configuration > Domain management.
2. Scroll down to the HTTPS panel.
3. If your records have propagated, Netlify will show the certificate as active.
4. If you see a “DNS verification pending” banner, click Verify DNS configuration.
5. Once verified, click Provision certificate.
6. Scroll down and enable Force HTTPS to redirect all HTTP traffic to HTTPS via 301 redirects.

If you run into an error saying the certificate couldn’t cover both domains, check that both the root domain (example.com) and the subdomain (www.example.com) resolve to Netlify. Let’s Encrypt runs an ACME HTTP-01 challenge against both hosts before signing the certificate.

Debug DNS Propagation and ACME Challenges from Terminal

When a domain won’t resolve or throws an SSL error, browser caching will only confuse you. Query the raw records and headers directly from your terminal.

Check the root domain’s A record:

dig +short A example.com
# Expected output for Namecheap BasicDNS:
# 75.2.60.5

Check the www CNAME record:

dig +short CNAME www.example.com
# Expected output:
# your-site-name.netlify.app.

Test the TLS handshake and HTTP response headers directly against Netlify’s edge:

curl -Iv https://www.example.com 2>&1 | grep -E "(HTTP/|Server|SSL certificate verify|issuer)"
# Sample output:
# * SSL certificate verify ok.
# * issuer: C=US, O=Let's Encrypt, CN=R10
# < HTTP/2 200
# < server: Netlify

If curl returns a certificate validation error mentioning *.netlify.app instead of your actual custom domain, your Let’s Encrypt cert hasn’t finished provisioning yet, and Netlify is still serving its fallback wildcard cert.

Common Pitfalls and How I Fixed Them

1. The www vs Apex Redirect Loop

I ran into an infinite redirect loop between apex and www after switching records. This happens when your external DNS points @ to the load balancer while Netlify is configured with example.com as the primary domain and www set to redirect to apex.

Fix: When using external Namecheap BasicDNS, set www.example.com as the primary domain in Netlify. Netlify can’t use its DNS-level CDN routing on external apex A records as effectively as it does on CNAMEs. Making www primary routes bulk traffic through the CDN edge, while the apex cleanly 301-redirects to www.

2. Mixed Nameservers in Namecheap

When moving to Netlify DNS, Namecheap sometimes retains its default nameserver records if the Custom DNS form wasn’t saved cleanly. You end up with two Namecheap and two Netlify nameservers answering queries simultaneously, creating intermittent lookup failures.

Check your authoritative nameservers with whois:

whois example.com | grep "Name Server"
# Ensure ONLY Netlify NS1 servers appear here

Frequently Asked Questions

How long does it take for Namecheap DNS to update to Netlify?

On Namecheap BasicDNS with TTL set to Automatic, A and CNAME record updates usually propagate within 5 to 15 minutes. Nameserver changes (moving over to Netlify DNS) take anywhere from 1 to 24 hours depending on global resolver TTL caches.

Should I make www or the apex domain my primary domain on Netlify?

If you’re on Netlify DNS, either works fine because Netlify flattens ALIAS/ANAME records on its own edge. If you’re on Namecheap BasicDNS, make www.example.com primary. That ensures traffic hits the CNAME routed to Netlify’s distributed edge rather than bottlenecking on a single load balancer A record IP.

Can I use Cloudflare DNS instead of Netlify DNS or Namecheap?

Yes. Set your Namecheap nameservers to Cloudflare, point a CNAME on www to Netlify, and rely on Cloudflare’s CNAME Flattening for the root apex. Keep Cloudflare proxying (the orange cloud) disabled initially so Netlify can complete its Let’s Encrypt HTTP challenge.

Why is Netlify SSL verification failing on my Namecheap domain?

This usually means DNS hasn’t reached Let’s Encrypt’s validation servers yet, or you have an old CAA record restricting which certificate authorities can issue certs for your domain. Remove any conflicting CAA records in Namecheap, wait about 15 minutes, and hit Retry DNS verification in Netlify’s HTTPS settings.