Built your site with Webflow? Here's exactly how to point a custom domain at it — DNS, apex vs www, and SSL — plus what Domain Agent will soon do for you.
To connect a custom domain to Webflow, add it under Site settings → Publishing, then copy the DNS records Webflow shows for your site into your registrar: two A records on the root domain and a CNAME on www pointing to proxy-ssl.webflow.com. Verify ownership (Webflow may require a TXT record), set the root as your default domain, and publish. Webflow auto-provisions free SSL once DNS is verified.
Webflow serves your site behind its CDN. You point the apex via two A records and www via a CNAME to proxy-ssl.webflow.com. Since Webflow's April 2025 DNS migration the exact A records can differ per site, so always copy the values shown in your own Site settings → Publishing panel — the current published defaults are 75.2.70.75 and 99.83.190.102.
Webflow also requires a one-time TXT ownership-verification record before you can publish on a custom domain, and it auto-provisions free SSL after the domain connects.
| Type | Host | Value | Notes |
|---|---|---|---|
| A | @ (root) | 75.2.70.75 | Current default — confirm the exact value in your Site settings → Publishing. |
| A | @ (root) | 99.83.190.102 | Current default — confirm the exact value in your Site settings → Publishing. |
| CNAME | www | proxy-ssl.webflow.com | Older docs may show cdn.webflow.com; use what your panel shows. |
| TXT | as shown | one-time verification code | Required to verify ownership before publishing. |
Values verified from Webflow's official docs, as of June 2026. Providers can change these — confirm against Webflow's current dashboard.
Sources: Webflow — Manually connect a custom domain · Webflow — Set the root as default domain
Search and buy on JustDomain.ai today — and join the waitlist to have Domain Agent do all of this for you.