UK domains, DNS and business email · real people · since 200601623 650333 · Client login
Search domains

Why are my business emails going to spam? The DNS causes

Many spam problems start in DNS: a missing or duplicate SPF record, DKIM not published, records lost in a nameserver move, wrong MX records, no reverse DNS, or a DMARC policy that rejects your own mail. dijitul checks and fixes email DNS for £45 an hour + VAT, or it is included with dijihost Complete Hosting.

Updated 2026-11-12 · by the dijitul DNS team · reviewed by , founder, building websites since 1996

Key facts

  • A domain can have only one SPF record; two cause a permanent error and SPF fails.
  • DKIM only works once the provider's record is published in DNS and signing is switched on.
  • Changing nameservers drops any record not copied to the new DNS provider first.
  • MX records must point to a hostname, not an IP address or a CNAME.
  • Reverse DNS (PTR) is set by whoever owns the sending IP address, not in your domain's DNS.
  • Google and Yahoo require SPF or DKIM, and valid forward and reverse DNS, from all senders.
  • A DMARC policy of p=reject will block your own mail if a sender is not authenticated.

Start with the DNS

Spam filters weigh many things, but proof of who sent a message comes from DNS. If the records are missing, duplicated or pointing at the wrong place, even a perfectly normal email can be filtered. These are the DNS causes we see most often. Check them first, because they are quick to confirm and usually quick to fix.

You can look up any of these records yourself with our guide on how to check DNS records.

SPF problems

  • No SPF record. Receivers cannot tell which servers may send for you.
  • Two SPF records. The most common fault. Someone adds a new v=spf1 record for a newsletter or invoicing tool instead of merging it into the existing one. SPF then fails for everything.
  • A sender left out. The website's contact form, a CRM or a booking system sends as your domain but is not listed.
  • Too many lookups. SPF allows 10 DNS lookups. Pile up includes and SPF fails.

The fix is one record listing every sender, for example v=spf1 include:spf.protection.outlook.com ~all plus any other includes you need. Our SPF, DKIM and DMARC records guide lists the values for each provider.

DKIM and DMARC problems

  • DKIM not published. Microsoft 365 needs two CNAMEs at selector1._domainkey and selector2._domainkey. Google Workspace needs a TXT at google._domainkey. Until they exist and signing is on, mail goes out unsigned or fails DKIM.
  • DKIM for other tools missing. Each newsletter or sending service has its own selector and record.
  • DKIM CNAMEs proxied in Cloudflare. They must be DNS only.
  • DMARC too strict too soon. A p=quarantine or p=reject policy sends your own unauthenticated mail to spam or blocks it. Start at p=none and read the reports. See what is DMARC.
  • No DMARC at all. Bulk senders now need one, and it helps everyone else.

Records lost or pointing the wrong way

  • Lost in a nameserver move. A new web designer or host changes the nameservers and only copies the website records. SPF, DKIM and DMARC vanish overnight. Compare the live records with what your providers expect.
  • Records added in the wrong place. Changes made at the old DNS provider after the nameservers moved have no effect.
  • Wrong or stale MX records. Old MX entries left from a previous provider, or MX pointing at an IP address or a CNAME, cause bounces and odd routing. See what is an MX record.
  • No reverse DNS (PTR). The sending server's IP should resolve back to a hostname that resolves forward to the same IP. Google and Yahoo expect this. The PTR is set by whoever owns the IP, so for Microsoft 365 or Google it is already done; for your own server or website mail, ask the host.

When DNS is right but mail still lands in spam

If all the records pass and messages still go to junk, the cause is usually reputation, content or a blocklist rather than DNS. Reading message headers and checking blocklists is covered in the full emails going to spam guide on dijitulsupport. Google, Yahoo and Microsoft also have rules for bulk senders, including DMARC and one-click unsubscribe for marketing mail.

How dijitul helps

dijitul checks your SPF, DKIM, DMARC and MX records against what your providers expect, merges duplicate SPF records, publishes missing DKIM keys and sets a sensible DMARC policy. On its own this is £45 an hour + VAT, or a fixed quote for bigger clean-ups. DNS management and email hosting are included with dijihost Complete Hosting at £1 a day + VAT. See DNS troubleshooting or contact us.

Frequently asked questions

Can a DNS problem really send my emails to spam?

Yes. Receiving servers use your SPF, DKIM and DMARC records to decide whether a message really came from you. If those records are missing, duplicated or wrong, genuine mail fails the checks and is far more likely to be filtered or rejected.

Can I have two SPF records?

No. A domain should have only one TXT record starting v=spf1. With two, receivers treat SPF as a permanent error and it fails. Merge the includes into a single record, for example v=spf1 include:spf.protection.outlook.com include:_spf.google.com ~all.

My emails went to spam after a website move. Why?

The most likely cause is that the nameservers were changed and only the website records were copied. SPF, DKIM, DMARC and sometimes MX records were left behind at the old DNS provider. Compare the live records with your email provider's settings and add the missing ones.

What is reverse DNS and do I need it?

Reverse DNS, or a PTR record, maps a sending IP address back to a hostname. Google and Yahoo expect valid forward and reverse DNS from senders. It is set by whoever owns the IP address, so Microsoft 365 and Google handle it; for your own server, ask the host.

Can a DMARC record make things worse?

Yes, if the policy is too strict. With p=quarantine or p=reject, any of your own senders that fail SPF and DKIM alignment will go to spam or be blocked. Start at p=none, read the reports, fix each sender, then tighten the policy.

Can dijitul fix my email DNS?

Yes. dijitul checks and fixes SPF, DKIM, DMARC and MX records for £45 an hour + VAT, or a fixed quote for bigger clean-ups. DNS management and email hosting are included with dijihost Complete Hosting at £1 a day + VAT.

Related

Get domains, DNS and email sorted

Set up properly, records checked, and real people to call. DNS and email are included with dijihost hosting.

Call usSearch domains