TranscomAll articlesHome

Why Are My Business Emails Going to Spam? SPF, DKIM and DMARC Explained

Updated 16 November 2026

You send a quote to a new customer. A few days later they tell you it went straight to their junk folder. It happens again with an invoice, then with a reply to an enquiry. Nothing in the message looks suspicious, so what is going on?

In a lot of cases the problem isn't what you wrote. It's that the receiving mail server can't confirm the email genuinely came from you. That confirmation relies on three DNS records: SPF, DKIM and DMARC. Here's what each one does, how to check yours, and what to fix first.

Why receiving servers are suspicious by default

Email was designed decades ago with no built-in way to prove who sent a message. Anyone can type any address into the 'From' line. Spammers and fraudsters exploit this constantly, which is why mailbox providers now treat unauthenticated mail with caution.

Google and Yahoo have tightened their requirements in recent years, particularly for bulk senders, and other providers follow similar principles. If your domain can't prove a message is legitimate, it is far more likely to be filtered, flagged or rejected outright.

SPF: who is allowed to send for your domain

SPF (Sender Policy Framework) is a TXT record in your domain's DNS that lists the servers permitted to send email on your behalf. When a message arrives, the receiving server checks whether the sending server is on that list.

A simple SPF record looks something like this:

v=spf1 include:_spf.yourprovider.example ~all

The include part authorises your email provider's servers, and ~all tells receivers to treat anything else with suspicion.

Common SPF mistakes

DKIM: a signature that proves the message wasn't altered

DKIM (DomainKeys Identified Mail) adds a cryptographic signature to every outgoing message. Your mail server signs the email with a private key, and publishes the matching public key in your DNS. The receiving server uses that public key to check the signature.

If it matches, the receiver knows two things: the message was sent by a server holding your key, and it wasn't tampered with on the way. Unlike SPF, DKIM usually survives forwarding, which makes it especially valuable.

DKIM keys are published under a 'selector', so a domain can have several keys for different services. Each service you send through should sign with its own key.

DMARC: the policy that ties it all together

DMARC (Domain-based Message Authentication, Reporting and Conformance) tells receiving servers what to do when a message fails SPF and DKIM checks. It also requires 'alignment', meaning the domain in the visible From address must match the domain that passed SPF or DKIM. That's what stops someone passing checks on their own domain while pretending to be yours.

DMARC has three policy levels:

PolicyWhat it tells receiversWhen to use it
p=noneTake no action, just send reportsWhen you're starting out and monitoring
p=quarantineSend failing mail to spamOnce you're confident legitimate mail passes
p=rejectRefuse failing mail entirelyStrongest protection against spoofing

DMARC can also ask receivers to send you aggregate reports, showing which servers are sending mail using your domain. These reports are the best way to spot a forgotten service before you tighten your policy.

How to check your own setup

You don't need special tools to get a first look. Send an email from your business address to a personal webmail account, then open the full message headers (often called 'Show original' or 'View source').

Look for a line called Authentication-Results. You want to see:

If any of them say fail, softfail, none or temperror, that's where to start. Repeat the test for every system that sends mail as your domain, not just your main mailbox.

A sensible order for fixing things

  1. List every service that sends email using your domain.
  2. Build a single SPF record that authorises all of them.
  3. Turn on DKIM signing for each service and publish the keys.
  4. Add a DMARC record at p=none with reporting enabled.
  5. Review the reports for a few weeks and fix anything unexpected.
  6. Move to p=quarantine, then p=reject when you're confident.

When authentication isn't the whole story

Correct records are the foundation, but other things affect delivery too:

Let someone else get it right

Getting SPF, DKIM and DMARC right isn't difficult once you understand it, but it is fiddly, and a single typo can quietly send your mail to junk folders for months.

If you'd rather not manage it yourself, Transcom's Managed Email handles it for you. For £12 a month you get your own domain name included, 25 mailboxes with unlimited storage, and DNS, SPF, DKIM and DMARC set up and verified by our team. Inbound mail is filtered by MxGuard, our own AI spam and virus gateway, and your mail is backed up encrypted and off-site with 30-day retention. Moving an existing domain? We handle the migration.

Working on your own? Business Email gives you a single professional mailbox on one of our established business domains, with deliverability configured for you, for £25 a year. And if you need a website as well, Managed Hosting includes a domain, email accounts and full DNS configuration alongside your site.

Ready for email that lands in the inbox? See Managed Email and let our team set it up properly.