Namecheap Registrar Servers com

Every new Webflow site publishes to a webflow.io subdomain. Launching on a branded domain requires a paid Site plan plus DNS records at the registrar that holds the domain. If that registrar is Namecheap, you set it up in Namecheap's DNS panel, and getting it wrong can block publishing or break email on the same domain.

Three DNS records in Namecheap's Advanced DNS panel point the domain at Webflow hosting. SSL certificates are issued automatically once the records resolve. Because the root domain uses an A record rather than a CNAME, Namecheap Private Email MX records coexist with the site's records, so a business can run its website and its inboxes on one domain.

Freelancers and agencies use this connection whenever they launch a client site on a client-owned Namecheap domain, while small businesses use it to keep their websites and email under the same registrar account as their domains. Developers managing dozens of domains use the Namecheap XML API to script the same DNS changes at scale.

How to integrate Namecheap Registrar Servers com with Webflow

What is Namecheap Registrar Servers com? Namecheap is an ICANN-accredited domain registrar that started in 2000 and reports more than 24 million domains under management. It sells domain registration and transfers across hundreds of TLDs, DNS services (BasicDNS, FreeDNS, and PremiumDNS), SSL certificates, and Private Email hosting. Its XML API supports domain registration and DNS management and automates the SSL lifecycle.

The Namecheap-Webflow connection runs entirely through DNS. Namecheap has no app in the Webflow Marketplace, so there is nothing to install on either side. Teams set it up at launch, during a DNS migration, or when a domain portfolio spans many client sites.

The Namecheap-Webflow integration supports three approaches:

• Manual DNS configuration points your domain at Webflow through Namecheap's Advanced DNS panel without writing code.
• Native migration, email, and forwarding options handle legacy DNS migration, Private Email records, and secondary domain redirects.
• The Webflow Data API and Namecheap XML API give you full control over DNS automation and publishing, but require server-side development.

Most implementations combine two or more of these methods depending on the complexity of the setup.

Point your Namecheap domain to Webflow with DNS records

This is the standard path for connecting a Namecheap domain, and it requires no code. You need a paid Site plan on the Webflow side. On the Namecheap side, the Host Records panel is only available when the domain uses BasicDNS, FreeDNS, or PremiumDNS, not third-party nameservers. Keep Namecheap's default nameservers; custom nameservers aren't needed for Webflow hosting.

To set up the integration:

1. In Webflow, go to Site settings > Publishing > Production, click Add a custom domain, then Manually add domain. Enter your domain and click Add domain. The exact DNS values for your site appear on this screen.
2. In Namecheap, go to Domain List > Manage > Advanced DNS > Host Records.
3. Delete Namecheap's default parking redirect, URL Redirect Record, and default CNAME records. Leftover parking records conflict with the values you are about to add.
4. Click Add New Record and add an A record with host @ and value 198.202.211.1.
5. Add a CNAME record with host www and value cdn.webflow.com. Enter only the subdomain label in the Host field; Namecheap auto-appends your domain to submitted values.
6. Add a TXT record with host _webflow and the one-time-verification=… value from Site settings, then click Save All Changes.
7. Back in Site settings > Publishing > Production, click Verify domain, then Publish and Publish to selected domains.

A few details matter while the records settle:

• Two possible sets of DNS records exist while Webflow finishes migrating its DNS infrastructure, so copy the values shown in your own Site settings > Publishing > Production rather than from any guide, this one included.
• New records at Namecheap normally take about 30 minutes to take effect, though global DNS propagation can run to 48 hours.
• Leave TTL on the default setting if you're unsure; Namecheap's default is 30 minutes.
• Remove any extra A records on the root domain, because multiple A records or duplicate CNAMEs put the domain into an error status.

After verification, set one connected domain as the default with Make default under Site settings > Publishing > Production; setting the root as default without correct DNS can cause redirect loops.

Migrate legacy DNS records automatically

Sites created before April 21, 2025 point at legacy DNS values that no longer work. Since January 13, 2026, publishing is blocked for domains that still point to the legacy records 75.2.70.75, 99.83.190.102, or proxy-ssl.webflow.com. Those sites stay online, but they stop accepting changes. Webflow's automatic migration authorizes Entri to rewrite the records and asks you to sign in with your registrar credentials, so start there and see whether your Namecheap login is accepted before doing the work by hand.

To migrate a Namecheap domain:

1. Go to Workspace settings > Domain Updates, click Update all domains, and sign in when Entri prompts you.
2. Track each site in that same panel, or click Update DNS next to one site to migrate it on its own.
3. If you'd rather migrate manually, replace the legacy values with 198.202.211.1 and cdn.webflow.com in Advanced DNS.

Before making DNS changes, Namecheap suggests lowering TTL first, to 300 seconds, so old cached values expire faster.

Keep Namecheap email and forwarding alongside your Webflow site

Webflow hosting covers the website only. The hosting overview states: "Webflow doesn't provide email hosting services. You can keep your current email hosting service (MX records) or set up a new one with any email service provider." Namecheap Private Email fills that gap on the same domain, sold as a standalone mailbox plan.

Add Private Email MX records in Advanced DNS

MX records for the root domain coexist with the site's A record, so email and website run side by side in one DNS zone.

To set up Private Email on a Webflow-connected domain:

1. In Domain List > Manage > Advanced DNS, add an MX record with host @, value mx1.privateemail.com, and priority 10.
2. Add a second MX record with host @, value mx2.privateemail.com, and priority 10, per the Private Email DNS guide.

Namecheap checks for the record every 15 minutes, and verification can take up to 4 hours while DNS propagates. For DKIM setup, subscriptions purchased on or after June 2, 2026 use the hostname privateemail._domainkey, while earlier subscriptions use default._domainkey.

Forward a secondary Namecheap domain to your Webflow site

If you hold extra Namecheap domains, such as campaign or defensive registrations, redirect them to your primary Webflow-hosted domain instead of connecting each one.

To set up a redirect:

1. Go to Domain List > Manage > Advanced DNS > Host Records and click Add New Record.
2. Choose URL Redirect Record, set the host to @, www, or *, and enter your Webflow site's URL as the destination.
3. Pick a redirect type per the URL redirect guide: Unmasked, Masked, or Permanent (301).

Redirects take effect within about 30 minutes. For path-level redirects on the primary domain, use Site settings > Publishing > 301 redirects instead; this requires a paid plan, and the recommended maximum is 1,000.

Build with the Webflow and Namecheap APIs

Agencies and developers managing many domains can script the whole connection instead of clicking through two dashboards per site. This path requires server-side development. Namecheap's production API has eligibility requirements: at least 20 domains in the account, a $50 balance, or $50 spent in the last two years. API access requires an IPv4 whitelist, and the API cannot manage domains on FreeDNS or PremiumDNS.

• The Namecheap XML API handles domain registration, availability checks, DNS host records, and SSL lifecycle through HTTP GET requests that return XML.
• Webflow's Data API v2 handles site lookups, custom domain IDs, and publishing, authenticated with a Bearer token.
• Webflow webhooks push events like site_publish and form_submission to your endpoint. Namecheap's domain and DNS API has no webhooks, so poll getHosts or getList for changes on that side.
• Namecheap caps API calls at 50 per minute, 700 per hour, and 8,000 per day across the whole key, which sets the pace for any portfolio-wide loop.

Test Namecheap calls against the sandbox at https://api.sandbox.namecheap.com/xml.response before touching production DNS.

Set Webflow DNS records with the Namecheap API

The setHosts command is destructive. Every record not included in the call gets deleted, including MX, SPF, DKIM, and DMARC records, which silently kills email. Always read first, merge, then write.

To point a domain at Webflow programmatically:

1. Read existing records with namecheap.domains.dns.getHosts:

https://api.namecheap.com/xml.response?ApiUser=ncuser&ApiKey=apikey&UserName=ncuser&ClientIp=1.2.3.4&Command=namecheap.domains.dns.getHosts&SLD=example&TLD=com

2. Merge the existing records with the Webflow records for your site.
3. Write the full merged set with namecheap.domains.dns.setHosts (use HTTP POST if the set exceeds 10 records). The request below is a non-copyable skeleton showing only the three Webflow additions; do not submit it until every record returned by getHosts has been included:

https://api.namecheap.com/xml.response
  ?ApiUser=ncuser&ApiKey=apikey&UserName=ncuser&ClientIp=1.2.3.4
  &Command=namecheap.domains.dns.setHosts
  &SLD=example&TLD=com
  &HostName1=@&RecordType1=A&Address1=198.202.211.1&TTL1=1800
  &HostName2=www&RecordType2=CNAME&Address2=cdn.webflow.com&TTL2=1800
  &HostName3=_webflow&RecordType3=TXT&Address3=one-time-verification%3DXXXXX&TTL3=1800
  &EmailType=MX

For portfolio-wide updates, enumerate every domain with namecheap.domains.getList and repeat the read-merge-write loop per domain.

Publish to the custom domain with the Webflow Data API

The Data API v2 has no endpoint to add a custom domain to a site, so that one step stays in the UI. Everything after it can run in code.

To publish programmatically:

1. Add the custom domain once in Site settings > Publishing > Production.
2. Retrieve the domain ID with the Get Custom Domains endpoint, GET https://api.webflow.com/v2/sites/{site_id}/custom_domains, scope sites:read.
3. Call POST https://api.webflow.com/v2/sites/{site_id}/publish (scope sites:write) with {"customDomains": ["<domain_id>"]} in the body.

Authenticate with a site token for single-site work; each site supports up to five tokens, and tokens expire after 365 consecutive days of inactivity.

What you can build with the Namecheap Webflow integration

Integrating Namecheap with Webflow lets you launch and manage sites on Namecheap-registered domains without transferring domains to another registrar or hiring a developer for DNS work.

• Branded site launch on your own domain: A small business publishes its Webflow site on its Namecheap .com by adding three records in Advanced DNS. With typical propagation, the site verifies and goes live the same day, with SSL issued automatically.
• Company website with matching email: A marketing site at yourdomain.com and Private Email inboxes at hello@yourdomain.com run from one Namecheap DNS zone, because MX records sit alongside the site's A and CNAME records.
• Agency client portfolio management: One Webflow partner documented twelve migrations in a single week: the first three took 90 minutes each and the last three 20 to 30 minutes. Scripting the same loop through getList and setHosts removes the per-domain dashboard work entirely.
• Campaign microsites and defensive domains: Forward secondary Namecheap registrations to Webflow landing pages with URL Redirect Records, or connect several domains to one site when a campaign needs more than one address.

For bulk DNS changes across dozens of client domains, use the API integration path to run the documented read-merge-write process for each domain. Once the sites are live, see how to apply custom code programmatically across them.