Webflow and Your Domain: Why Email Still Needs Attention

How Webflow Works

You ran a TechSpy scan on your domain. The report came back with a surprise: "Your website is built with Webflow." Maybe you already knew that. Or maybe you just thought your site was "that thing the agency made." Either way, Webflow is a visual website builder — a tool that lets someone design pages by dragging elements around, without writing code. It also hosts the site for you, so those pages stay fast and online. What the scan doesn't say: Webflow handles your website, but it has nothing to do with your email. If you use Google Workspace or Microsoft 365 for email, that's a completely separate system. And the glue that connects your domain to both — your DNS settings — has to be set up correctly for email to work.

Real-World Analogy

Think of your domain like a street address. Webflow is the construction company that built your house. Email is the postal service delivering letters. The mailbox out front (your DNS records) has to be installed separately, and if the post office doesn't know where it is, mail won't arrive — no matter how nice the house looks.

Here's what happens when someone visits your website. You (or your designer) used Webflow's visual editor to design the pages. Webflow turns that design into clean website code and stores it on their fast, secure servers. Then you told your domain — maybe through your registrar or DNS provider — to point to Webflow. Visitors type in your domain, and they see your site.

Now here's the part most people miss: email doesn't follow that same path. When someone sends you an email, their mail server looks up your domain's MX records — a special type of DNS instruction that says "deliver messages here, not to the website." Those MX records point to Google, Microsoft, or wherever your real email inbox lives. They don't come from Webflow, and Webflow won't create them for you. The same goes for security records like SPF, DKIM, and DMARC — the digital signatures that tell the world "this email is really from us."

Technical Details

▸Webflow site detection: scans look for with content , CSS class , or the function in the page source.

▸Webflow hosting defaults: usually a CNAME record like or pointing to Webflow, while the root domain () redirects.

▸Email DNS lives at the same registrar/DNS host as the domain, not inside Webflow. Typical records: MX (e.g., ), TXT for SPF (), another TXT for DKIM under , and DMARC at .

Why It Matters for Your Business

When your email DNS records are correct, emails reach inboxes. Marketing campaigns land in front of customers, sales follow-ups don't vanish, and support replies get seen. That's the baseline of running a business.

When those records are missing or wrong, bad things happen. Your outbound emails get flagged as spam or rejected outright. Worse, someone could spoof your domain — send fake emails pretending to be you — and your customers won't have any protection to tell the difference. That damages trust, and it can hurt your domain's reputation for months.

This isn't just an IT concern. If you're in marketing, you care about deliverability rates. Sales cares about whether that proposal reached the client. Support cares about customers seeing responses. And as a founder, you care about your brand not being used to scam people.

Common Issues and Warning Signs

Problems usually show up as business friction rather than technical errors. You'll notice the symptoms long before you'd think to check a DNS panel.

Common Issues

Customers say they never got your email, even though you sent it. (Missing or misconfigured DMARC/SPF.)

Your own test emails go to spam. (No SPF record authorizing your email provider.)

Someone reports receiving a phishing email that looks like it came from your company. (No DKIM signature to prove legitimacy.)

Email bounces with messages like "rejected due to DMARC policy." (A strict DMARC record is published, but SPF and DKIM aren't aligned.)

TechSpy shows a warning about missing DMARC, SPF, or DKIM when you scan your domain. (Direct sign you need to add records.)

How to Fix or Improve Your Email Setup

You'll need to add or update DNS records at the company where your domain is managed (registrar like Namecheap, or DNS host like Cloudflare). If you don't know where that is, don't guess — ask the person who set up the domain.

Once the records are in place, give them a few hours to update. Then run a TechSpy scan again — your email security gaps should close right up.

1Find where your DNS is managed. Log in to wherever you bought the domain, or check your hosting account. Look for a "DNS" or "manage DNS" section.

2Go to your email provider's setup guide. For Google Workspace, it's under Admin > Domains. For Microsoft 365, it's in the Admin portal under Domains. They'll give you exact values for MX, SPF, DKIM, and DMARC.

3Add a TXT record for SPF that lists the email services you use. If you only use Google, it's . If you only use Microsoft, it's .

4Add a TXT record for DKIM. Your email provider will give you a name (like ) and a long value. Copy-paste exactly.

5Add a TXT record for DMARC at with the value . This starts monitoring without blocking anything. You can tighten it later.

6If you're not comfortable making these changes, forward the email provider instructions to whoever manages your IT or domain. They'll know what to do.