Important
As of January 13, 2026, you can't publish to a custom domain that points to Webflow's legacy DNS records. After June 1, 2026, domains that still point to legacy records will experience downtime — your site will be unavailable to visitors until you update your DNS settings.
To restore publishing access and prevent downtime, update your custom domain's DNS settings.
Webflow is upgrading its hosting infrastructure to improve performance, reliability, and security. As part of this enhancement, we’re migrating secure network connections to Cloudflare, which offers superior DDoS mitigation and faster global response times.
If your site was created before April 21, 2025, you must update your custom domain’s DNS settings to point to Webflow's new DNS records. As of January 13, 2026, you can’t publish to a custom domain that points to Webflow’s legacy hosting infrastructure.
On June 1, 2026, Webflow will begin turning off legacy hosting infrastructure. If your custom domain still points to legacy DNS records after this date, your site will experience downtime and be unavailable to visitors.
Learn more about what happens if you don’t update your DNS settings by the deadline.
Note
If you use a reverse proxy, you may still see "Update needed" in Site settings > Publishing > Production even after you've updated your proxy origin to Webflow's new DNS records. If you've already updated your proxy origin, your site won't be affected by the June 1, 2026 enforcement — you can ignore the dashboard alert and continue publishing.
What to expect
- Admins of affected Workspaces have received emails, in-app notifications, and Dashboard badges
- These updates direct you to the specific sites that still need action
- You’ll also see tools in the Dashboard to help you complete the migration
If you don’t see migration prompts in the Dashboard, go to Site settings > Publishing > Production to find the correct DNS records for your custom domain(s).
How to update your DNS
You can update your DNS settings in one of two ways: