Webflow Email: How to Get Business Email for a Webflow Site
Email Infrastructure & DevOps Specialist
TL;DR: Webflow doesn't host email and isn't a domain registrar, so your domain and its email records always live at your registrar (GoDaddy, Namecheap, Cloudflare and so on). Webflow only needs A and CNAME records for the website, plus a one-time
_webflowTXT record for verification. Your email host needs MX, SPF, DKIM and DMARC records. Keep them separate, and avoid one-click connection tools if your email is already live: they can overwrite email records.
Webflow is the cleanest case of any site builder, because there's nothing to untangle. It builds and hosts the website. Everything else, including the domain and every mailbox, sits with other companies.
The risk comes at launch, when a designer or agency connects the domain to Webflow and the client's email stops working the same afternoon.
What Webflow does and doesn't do
| Webflow | Where it actually lives | |
|---|---|---|
| Website hosting | Yes | Webflow |
| Domain registration | No | Your registrar |
| DNS records | No | Your registrar or DNS provider |
| Mailboxes | No | An email host |
| Form notification emails | Yes, from Webflow's own address | Webflow |
Because Webflow never manages your DNS, every email record you add or change is done at your registrar, not in Webflow. Find your DNS provider shows how to check where that is.
Connecting a domain without breaking your email
A domain connected to Webflow needs two A records on the root domain and a CNAME on www. Email needs a completely different set: MX for incoming mail, and TXT records for SPF, DKIM and DMARC. The two sets don't overlap, so the website and email can run side by side for as long as neither gets deleted.
Three ways email breaks at launch:
- One-click connection tools: Webflow offers a quick connect option for some registrars. Webflow's own GoDaddy integration page warns that it changes records automatically and can overwrite MX, SPF, DKIM and DMARC. If the domain already has working email, add Webflow's records by hand instead.
- Clearing "conflicting" records: Troubleshooting guides tell you to remove old records that conflict with Webflow's. That means old A or CNAME records for the website, never MX or email TXT records.
- Moving the domain from an old web host: If email came bundled with the old hosting (cPanel email, for example), it stops when that hosting is cancelled. Move the mailboxes first. The email migration guide covers how.
Before you change anything, screenshot the domain's DNS records. If email stops, you can put back exactly what was there.
Adding a mailbox to a Webflow domain
These steps use MailAfiniti, and they're the same for any host:
- Start a MailAfiniti trial, add your domain and create the mailboxes you need.
- At your registrar, add the four records MailAfiniti generates: MX, SPF, DKIM and DMARC. Leave Webflow's A and CNAME records alone. Copy your DNS records without mistakes covers each field.
- If the domain already has an SPF record, edit it instead of adding a second. Two SPF records make both invalid.
- Wait for the records to verify, usually within the hour, then connect the mailbox to your mail app.
For agencies handing a site to a client: keep the domain registered in the client's name, and give the client their own email account rather than one under the agency. It makes the handover clean if you part ways.
Where Webflow's form emails come from
Webflow form notifications aren't sent from your domain. According to Webflow's form submissions guide, they come from no-reply-forms@webflow.com on most workspaces, and from an unbranded no-reply address only on the Growth workspace plan. You also need an active site plan to receive submissions from a form on your custom domain.
What you can control:
- Reply-to: set each form's reply-to to the visitor's email field, so hitting reply goes straight to the person who filled in the form.
- Recipients: Webflow recommends sending notifications to a named address (jane@) rather than a role address (info@ or support@), since some mail systems filter role addresses more heavily. If you use info@ as an alias, point the form at the real mailbox behind it.
- Safe senders: add Webflow's sending addresses to your mail app's safe senders list so notifications don't land in junk.
If you need form notifications sent from your own domain, that takes a separate form or transactional email service. Webflow doesn't offer it natively.
Once your records are in, run the domain through the free email health check.
FAQ
Does Webflow offer email hosting?
No. Webflow hosts websites only. Mailboxes come from a separate email host, connected through your domain's DNS records at your registrar.
Can I buy a domain through Webflow?
No. Webflow isn't a domain registrar. You buy the domain from a registrar such as Cloudflare, Namecheap or GoDaddy, then connect it to your Webflow site with A and CNAME records.
Why did my email stop working after connecting my domain to Webflow?
Usually because MX or email TXT records were deleted or overwritten while adding Webflow's records, often by a one-click connection tool. Restore the MX, SPF, DKIM and DMARC records from your email host. Webflow only needs A and CNAME records.
What email address do Webflow form notifications come from?
From no-reply-forms@webflow.com on most workspaces. Growth workspaces can send from an unbranded no-reply address. You can set each form's reply-to so replies go to the visitor.
Can a Webflow site and Google Workspace or another email host use the same domain?
Yes. The website uses A and CNAME records and email uses MX and TXT records, so both run on one domain without conflict. Add both sets at your registrar.
Related reading
- WordPress.com email: for sites on WordPress.com
- Framer business email: for sites built on Framer
- How to set up business email: the full setup guide for any domain