Your Webflow Site Will Go Down on June 1 If You Have Not Done This.

What Is the Webflow DNS Migration and Why Does It Matter?

Webflow is migrating its entire hosting infrastructure from legacy servers to Cloudflare. If your Webflow site was created before April 21, 2025, and you have not updated your DNS settings, your site will experience downtime on June 1, 2026. Webflow will begin turning off legacy hosting infrastructure on that date. Sites that still point to old DNS records will go offline until the records are updated.

This is not a theoretical risk. Webflow has already blocked publishing for sites that have not migrated since January 13, 2026. If you have tried to push an update to your custom domain and received an error, this is why. The next enforcement phase on June 1 is more severe. Your site will stop loading entirely for visitors.

The migration itself takes less than five minutes. But if you do not know it needs to happen, or if you assume someone else handled it, your business website could go dark without warning. I have already helped several clients through this process, and the most common reaction is surprise that it was even required. Let me walk through exactly what to do.

How Do You Know If Your Site Is Affected?

Every Webflow site created before April 21, 2025, needs to have its DNS records updated to point to Webflow's new Cloudflare-powered infrastructure. Sites created after that date are already on the new system and require no action. The fastest way to check is to log into your Webflow dashboard, go to Site settings, then Publishing, then Production. If you see an "Update needed" badge next to your custom domain, your site has not been migrated.

Workspace owners and admins can also check the migration status of all sites at once by going to Workspace settings and then Domain Updates. This page shows every site published to a custom domain along with its current migration status. Any site showing a yellow "Update needed" status requires action before June 1.

Webflow has been sending email notifications, in-app alerts, and dashboard badges to affected workspace owners since the migration was announced. If you have been ignoring those notifications, now is the time to act. The June 1 deadline is less than two months away.

What Are the New DNS Records You Need?

The migration requires changing two DNS records at your domain registrar (GoDaddy, Namecheap, Cloudflare, Google Domains, IONOS, or wherever you purchased your domain). The old records pointed to Webflow's legacy IP addresses 75.2.70.75 and 99.83.190.102 with a CNAME of proxy-ssl.webflow.com. The new records are simpler and faster.

You need one A record with the hostname @ (your root domain) pointing to the IP address 198.202.211.1. You also need one CNAME record with the hostname www pointing to cdn.webflow.com. If you have any other A records or CNAME records with the same hostnames, remove them. Duplicate or outdated records will prevent the migration from completing and may leave your domain stuck in an "Update pending" status.

Before making these changes, lower your TTL (Time To Live) setting for the domain to the lowest value available, often 30 seconds. This helps the changes propagate worldwide more quickly. After the migration is confirmed and your site is working normally, you can restore the TTL to its previous value.

Can You Do This Automatically Without Touching DNS Records?

Yes. Webflow offers an automatic migration option that handles the DNS changes for you. Go to Workspace settings, then Domain Updates, and click "Update all domains." Webflow uses a service called Entri that connects to your domain registrar, authenticates with your credentials, and updates the records automatically. You will be prompted to log in to your registrar (GoDaddy, Namecheap, IONOS, etc.) and authorize the changes.

This is the easiest path for non-technical site owners. It eliminates the risk of entering wrong values, forgetting to remove duplicate records, or accidentally breaking other DNS configurations. The automatic process typically completes in under two minutes.

If you manage multiple Webflow sites across the same workspace, you will need to repeat this process for each site that shows "Update needed" status. The automatic migration handles one site at a time.

What If You Use Cloudflare for Your Domain?

If you already manage your domain through Cloudflare (not just Webflow's Cloudflare hosting, but your own Cloudflare account), the process has an additional consideration. Webflow now supports Cloudflare Orange-to-Orange (O2O) configuration, which allows you to layer Cloudflare's security and performance features (WAF, bot protection, caching rules) on top of Webflow's hosting.

To use O2O, your site must first be migrated to the new infrastructure. Set your DNS proxy status to "DNS only" (grey cloud) for the initial migration. Once the migration is confirmed and your SSL certificate is issued, you can enable the orange cloud proxy and configure O2O following Webflow's documentation.

One important caveat: if your domain uses Cloudflare's Zone Hold feature, SSL certificate generation may fail during migration. This happens because Cloudflare blocks Webflow from issuing certificates for held zones. Release the Zone Hold temporarily, wait for the SSL certificate to generate, then re-enable it.

What Happens If You Miss the June 1 Deadline?

After June 1, 2026, three things happen to sites that have not migrated. Your site experiences downtime and becomes unavailable to visitors. Publishing remains blocked, meaning you cannot push any changes even if you want to. And the fix is the same as it would be today: update your DNS records. The difference is that between now and June 1, your site stays live while you update. After June 1, your site goes down first and comes back only after you update.

There is no data loss involved. Your Webflow project, CMS content, and design remain intact. Only the connection between your custom domain and Webflow's servers is affected. Updating your DNS settings restores your site immediately. But every hour your site is down means lost traffic, lost leads, and potential damage to your search rankings. Google and other search engines will eventually deindex pages that return errors for extended periods.

For businesses that depend on their website for lead generation, e-commerce, or brand credibility, even a few hours of downtime can have meaningful financial consequences.

Why Webflow Is Making This Change

The migration to Cloudflare brings meaningful improvements to every Webflow site. Cloudflare operates over 300 data centers worldwide, providing faster global response times than Webflow's legacy infrastructure. The new setup includes superior DDoS mitigation, protecting your site from malicious traffic attacks. SSL certificate management is handled automatically through Cloudflare's infrastructure, reducing the likelihood of certificate expiration issues.

For sites that want to add advanced security or performance features, the Cloudflare O2O integration opens up capabilities like Web Application Firewall (WAF) rules, custom caching policies, and bot protection that were not available on the legacy infrastructure. These features are particularly valuable for e-commerce sites, sites handling sensitive form submissions, and businesses in regulated industries.

The practical impact for most site owners is faster page loads, better uptime, and improved security with no increase in cost. The migration is a net positive for every Webflow site. The only risk is not doing it.

What You Should Do This Week

Log into your Webflow dashboard and check whether your sites need migration. If you see "Update needed" on any custom domain, use either the automatic migration tool or manually update your DNS records. The entire process takes less than five minutes per site. Verify the changes propagated by visiting your site in an incognito browser window after updating.

If you manage client sites as an agency or freelancer, audit every workspace you have access to. Client sites that you built and handed off may still be on legacy DNS. Reach out to those clients proactively. Sending a quick message explaining the deadline and offering to handle the migration is a simple way to add value and prevent an avoidable crisis.

If you want to understand more about why Webflow is investing heavily in infrastructure alongside these changes, my article on Webflow's transformation into an agentic marketing platform covers the broader strategy. For details on the other major platform changes shipping this month, check out my breakdown of the next-gen CMS and single-page publishing. And if you are handing off migrated sites to clients, my guide on how to hand off Webflow sites without everything breaking covers the workflow.

The June 1 deadline is real. The fix is simple. Do not let your site go down because of a five-minute task you put off. If you need help with the migration or want someone to audit your Webflow sites, I am happy to assist. Let's chat.