Blog / Cybersecurity

Why Your Company Email Lands in Spam (and the Three DNS Records Behind It)

DeliverabilityDevOpsEmailSME
Aviram Galim5 min read

I’ve lost count of how many times a client has come to me with the same complaint: Their emails are landing in their customers’ spam folders, and they don’t know how to fix it.

A typical scenario goes like this: An invoice is sent out on Monday. By Thursday, the customer claims never to have received it. Someone checks the spam folder, and there it is.

The odd part is that the same company can send a test message to a Gmail account, see it arrive, and conclude that everything is fine. It isn’t. Delivery to one inbox on one day proves very little.

When a company email lands in the spam folder, it’s usually not due to the content. The problem is usually three short text records in your domain’s DNS settings that were not set up properly or were set up years ago and never updated.

What the three records do

You don’t need to be tech-savvy to understand this. Each record provides an answer to a question that the receiving mail server asks about your message.

  • SPF answers the question, “Is this server allowed to send mail for this domain?” It is a list of approved senders.
  • DKIM answers the question, “Was this message really signed by the domain, and was it changed on the way?” It is a digital signature.
  • DMARC answers, “What should I do when the first two fail?” DMARC provides instructions to the receiver and sends reports about who is sending mail in your name.

A message that passes all three tests appears to have come from you. A message that fails them could have come from anyone, and mail providers treat it as such.

Why this matters more than it used to

Since 2024, Gmail and Yahoo have required authentication from senders. Domains that send 5,000 or more messages per day to their users must implement SPF, DKIM, and DMARC. Microsoft has announced similar rules for Outlook.com, which will take effect in May 2025. Non-compliant mail will first be sent to the junk folder.

A small company sending a few hundred messages a day isn’t considered part of that category. In practice, however, it still matters. Email without authentication is more likely to be treated as suspicious. Those published thresholds can change, so check your provider’s current guidance.

It also protects you in the other direction. Without DMARC, anyone can send an email that appears to come from your domain, and your customers may receive it.

Where it usually goes wrong

Most companies send emails from more than one place. One is the company mailbox. Others include the invoicing tool, newsletter service, CRM, and contact form on the website. Each of these sends emails with your domain in the “From” address.

The most common problems are:

  • It’s a sender that nobody told the DNS about. The newsletter tool was added last year but was never authorized.
  • DKIM was never activated. Many tools require a record to be added to the DNS before they can sign messages.
  • There are two SPF records. A domain may only have one. If a new tool asks you to “add this SPF record,” you need to merge the old one instead of leaving it beside it. Having two records will break SPF completely.
  • There are too many includes. SPF only allows 10 DNS lookups. Each authorized tool uses some, and exceeding the limit causes the entire record to fail.
  • A missing DMARC record. This is the most common issue.

None of these are difficult to fix. The hard part is finding them.

How to check in about 15 minutes

Send a message from your company email address to a Gmail account. Open the message and choose “Show original.” Look for SPF, DKIM, and DMARC at the top. You want to see “PASS” next to each one.

Then, do the same with every tool that sends mail for you, such as the invoicing app, newsletter service, and website form. People often skip this step, and it is where most failures occur.

Free checkers, such as MXToolbox and Mail-Tester, show you what your DNS records say today.

How to set up DMARC without breaking your own email

DMARC has three policies: none, quarantine, and reject. The goal is to have the strictest policy, but starting there is a mistake. If one of your tools is not set up correctly, a reject policy will block your own invoices.

The safe approach takes weeks, not hours.

  • Publish a DMARC policy of “none” with a reporting address. Mail will flow as before.
  • Read the reports for a few weeks. They show every system that sends mail from your domain, including ones you forgot about.
  • Fix each legitimate sender until it passes.
  • First, move to quarantine, then reject once the reports are clean.

Since raw DMARC reports are unreadable XML, use a free or low-cost reporting service to read them.

What I can and can’t promise

Correcting these records eliminates a common cause of spam placement. However, it doesn’t guarantee inbox delivery. Sender reputation, list quality, and message content also play a role, and a newsletter that readers mark as spam will be affected regardless of the DNS.

For a simple setup with one email provider and two or three tools, the technical fix typically takes an hour or two. That is my own estimate, not a measured figure. The longer part is the DMARC monitoring period.

One practical point: The person who registered the domain years ago may no longer be available, and no one may know where the DNS is managed. Finding that login information is often the first real task.

If your company email is landing in spam, or you aren’t sure what your domain is allowed to send, feel free to get in touch.
I reply within 24 hours.
Contact Me

Keep reading