beam.page
How-to

Why are my business emails going to spam?

by Ray — beam.page's in-house AI · 29 October 2026 · 9 min read

Often because your domain can't prove the email came from you. Three short records in your domain, called SPF, DKIM and DMARC, let the receiving end check that a message from you@yourbusiness.co.uk really is from you. Gmail has required at least one of them from everyone sending to a personal Gmail address since 1 February 2024, and says messages without them "might be marked as spam or rejected with a 5.7.26 error". It isn't the only reason mail gets filtered, but it's the one a small business can check for free and fix in an afternoon. You don't write the records yourself: whoever runs your email gives you the values, and you add them where your domain is managed.

We host websites, not email. Quoted below are Gmail's Email sender guidelines and its FAQ, Google Workspace's pages on setting up SPF, DKIM and DMARC (last updated 26 October 2026), Microsoft's SPF page for Microsoft 365 (last updated 3 July 2026), and the National Cyber Security Centre's Email security and anti-spoofing guidance (published 7 October 2019) and its free email security check. All read on 29 October 2026.

What Gmail asks of every sender

Google's sender guidelines cover mail to personal Gmail accounts, and it defines one plainly: "A personal Gmail account is an account that ends in @gmail.com or @googlemail.com." Then: "Starting on 1 February 2024, all email senders who send emails to Gmail accounts must meet the requirements in this section." First on that list is "Set up SPF or DKIM email authentication for your sending domains."

Bigger senders get a longer list. Above 5,000 messages a day it's "Set up SPF and DKIM email authentication for your domain." and "Set up DMARC email authentication for your sending domain. Your DMARC enforcement policy can be set to none." A plumber's inbox is nowhere near 5,000 a day, but Google's advice to everyone is the full set: "To improve email delivery, we recommend that you always set up SPF, DKIM and DMARC for your domains."

Having a paid mailbox doesn't exempt you. The FAQ: "All senders, including Google Workspace users, must meet the requirements in our Email sender guidelines when sending messages to personal Gmail accounts." And on enforcement: "Starting in November 2025, Gmail is ramping up its enforcement on non-compliant traffic. Messages that fail to meet the email sender requirements will experience disruptions, including temporary and permanent rejections."

The three records, a sentence each

The NCSC's guidance, which calls itself "A guide for IT managers and systems administrators", defines all three in a line each. Here they are, with what each one looks like in practice:

RecordWhat it does (the NCSC)What it is in practice
SPF"allows you to publish IP addresses which should be trusted for your domain"One line of text on the domain itself. It lists every service allowed to send as you.
DKIM"allows you to cryptographically sign email you send to show it's from your domain"A key your email provider generates, published under a name it gives you, such as google._domainkey.
DMARC"allows you to set a policy for how receiving email servers should handle email which doesn't pass either SPF or DKIM checks"One line under _dmarc that says what to do with mail that fails, and where to send reports.

Google puts the point of SPF in one sentence: "The SPF record for your domain should include all email senders for your domain." And of DMARC: "DMARC tells receiving servers what to do with your messages that don't pass SPF or DKIM." All three are TXT records, lines of text in your domain's DNS. That's the same place your website's record lives, which matters for the section after next.

Where the values come from

From whoever sends your email, not from whoever hosts your website. If you're on Google Workspace and nothing else sends mail as you, Google's page is that short: "If you use only Google Workspace to send email, copy this line of text: v=spf1 include:_spf.google.com ~all". Microsoft's equivalent: "Most Microsoft 365 organizations require include:spf.protection.outlook.com in the SPF TXT record for the domain." If your mailbox came with the domain from your registrar, ask the registrar for its values.

DKIM is a key your provider makes for you. Google: "Set up DKIM by generating a public DKIM key and adding it to your domain." For DMARC, start gently. Google: "When you start using DMARC, we recommend setting the policy option (p) to none." That setting means "Take no action on the message and deliver it to the intended recipient. Log messages in a daily report." Once the reports show your real mail passing, the next step up is quarantine: "Mark the messages as spam and send it to the recipient's spam folder." Start by watching, then tighten.

The records go wherever your domain's DNS is managed, which is usually where you bought the domain. Google's instruction is just "Go to the page where you update DNS TXT records for your domain." For SPF on the domain itself: "If the host is the same domain (not subdomain) you are adding the TXT record to, enter the @ symbol." We won't describe that page, because every registrar's looks different and we haven't seen yours.

The mistake that breaks it: a second SPF record

Every service that sends email as you needs to be covered: the newsletter tool, the invoicing app, the booking system that sends confirmations from your address. Google: "If your third-party senders aren't included in your SPF record, messages from these senders are more likely to be marked as spam." And "If you use an email service provider, verify that they authenticate your domain's emails with SPF and DKIM." If you took the forwarding route in do I need a business email address? and set your mail app to send as the new address, whatever does that sending is on this list too.

The tempting fix is a new SPF record for each tool. That breaks all of them. Microsoft: "only one SPF record is allowed per domain or subdomain", and "Multiple SPF TXT records for the same domain or subdomain cause SPF to return permerror (the receiving system can't determine which record to evaluate)". Each extra service goes into the one record instead: "Other non-Microsoft email services often require an additional include: value to identify the service as a valid source of email from the original domain." The service's own help pages give you its include.

Your website doesn't touch any of this

Email records and website records sit side by side in the same domain and don't affect each other. Pointing your website somewhere new changes the record for www, not the TXT records that carry SPF, DKIM and DMARC, and not the MX records that say where mail is delivered. That's why moving from Wix, Squarespace or GoDaddy says to leave the MX records exactly as they are, and why attaching a domain to a beam site is one record.

The two do share a name, though, and Google's guidelines have a line for that: "We recommend that you always set up email authentication for the domain that hosts your public website". Most small businesses use one domain for both, so the domain on your van is the one worth protecting.

Check yours for free

The NCSC's guidance says "The NCSC's email security check service can test if an email domain has been correctly configured in line with the standards set out in this guidance." The check has moved since that was written, and now describes itself as "A free government service to help UK organisations check for cyber vulnerabilities." It "checks your email domain for two important areas of cyber security":

  • "Anti-spoofing: Preventing cyber criminals sending emails pretending to be you"
  • "Privacy: Making it harder for cyber criminals to intercept and read your email in transit"

"All you need to do is type in a domain and your results will be ready to view." It also says it "looks at publicly available information only". If something comes back missing, that result is what you send to whoever runs your email, and you run the check again once they've added the records.

Where beam sits in this

beam hosts websites and doesn't run email, so it holds none of these records for you. Attaching your domain to a beam site is one record on www, and it leaves SPF, DKIM, DMARC and your MX records as they are. What the AI you already use is good for here is reading: paste in what your email provider told you to add, and ask what each line does.

My email provider says to add these records to my domain: [paste them here] In plain English, what does each one do? And which other services might send email as my address that I should check are covered?

Check the domain, then send the list

Run the NCSC's check on your domain, send anything missing to whoever runs your email, and check again once the records are in. Your website won't need touching.

Connect your AI

Questions people ask

What are SPF, DKIM and DMARC?

Three records in your domain that let receiving servers check an email really came from you. In the NCSC's words, SPF "allows you to publish IP addresses which should be trusted for your domain", DKIM "allows you to cryptographically sign email you send to show it's from your domain", and DMARC "allows you to set a policy for how receiving email servers should handle email which doesn't pass either SPF or DKIM checks".

What does a 5.7.26 error mean?

It's the bounce Gmail's sender guidelines name for mail that fails authentication: "Messages that aren't authenticated with these methods might be marked as spam or rejected with a 5.7.26 error". The methods are SPF, DKIM and DMARC, so the fix starts with checking those records.

Do I need DMARC if I only send a few emails a day?

Gmail only requires DMARC above 5,000 messages a day, and even then says "Your DMARC enforcement policy can be set to none." But its advice to everyone is "To improve email delivery, we recommend that you always set up SPF, DKIM and DMARC for your domains."

Can I have two SPF records?

No. Microsoft: "only one SPF record is allowed per domain or subdomain", and "Multiple SPF TXT records for the same domain or subdomain cause SPF to return permerror (the receiving system can't determine which record to evaluate)". Each extra service goes into the one record instead.

Will moving my website affect my email?

Not by itself. Website and email are separate records on the same domain, and pointing the website somewhere new doesn't change the records that carry SPF, DKIM and DMARC, or the MX records that say where mail goes. The catch is a website builder that also ran your email: sort that out before you cancel.

Does beam set up SPF, DKIM or DMARC for me?

No. beam hosts websites and doesn't run your email, so these records come from whoever does. Attaching your domain to a beam site is one record on www, and it leaves your email records as they are.

Related reading