← Back to blog

Why Are My Emails Going to Spam? Start With These Checks

August 27, 2026

When your business email goes to spam, the cause is rarely just one setting. A message can have valid SPF, DKIM, and DMARC records and still land in the spam folder. It can also have excellent content but fail because a sending platform was not properly authenticated. The useful question is not, "What is the one thing that sends email to spam?" It is: Is this an authentication problem, a sending-reputation problem, a recipient-list problem, or a message-specific problem? This guide helps you work through those possibilities in the right order.

Start with one real message

Do not begin by changing DNS records. Find a message that landed in spam and save the details:

Those details narrow the problem. For example, a password-reset email that goes to spam may point to a transactional-email setup. A newsletter sent to old contacts may point to list quality and engagement. A problem limited to Gmail may involve a different filtering decision than one limited to Outlook.

Check authentication in the message header

Every mailbox provider evaluates signals proving whether a message is really allowed to use your domain. The three main checks are SPF, DKIM, and DMARC.

SPF

SPF checks whether the server that sent the message is authorized in your domain's SPF record. A common issue is adding a new CRM, support platform, or newsletter tool without adding its required SPF entry. Another is publishing more than one SPF record, which can cause an SPF error. Read how to check an SPF record before changing it.

DKIM

DKIM adds a cryptographic signature to an email. The receiving server checks a public key in your DNS records to confirm the message was signed by the expected service. DKIM can fail because the key is missing, the selector is incorrect, a provider rotated its key, or a service was never fully authenticated. Read how to check a DKIM record.

DMARC

DMARC uses SPF and DKIM results to check whether authentication aligns with the visible From address. A message can pass SPF but still fail DMARC if the SPF domain does not align with the address your recipient sees. The same is true for DKIM. Read how to check a DMARC record. Open the message headers and look for a section usually called Authentication-Results. You are looking for SPF, DKIM, and DMARC results. This is much more useful than guessing from the message body alone.

A passing authentication check does not guarantee the inbox

Authentication proves important things about a message, but it does not guarantee inbox placement. Mailbox providers also ask questions like:

That is why a business can have a technically correct setup and still have a deliverability problem.

Check your list quality

For marketing email, the recipient list matters as much as the sending domain. Poor list quality can hurt sender reputation through:

Do not keep emailing someone just because their address is still technically deliverable. A large list of uninterested recipients is often worse than a smaller list of people who expect your messages. A practical cleanup process is:

  1. Suppress hard bounces promptly.
  2. Honor unsubscribes immediately.
  3. Remove obvious duplicates and malformed addresses.
  4. Re-engage inactive contacts carefully, rather than repeatedly sending promotions.
  5. Stop emailing contacts who do not respond after a reasonable re-engagement effort.
  6. Never buy a list or add people without a reasonable expectation that they will hear from you.

Read email list hygiene and deliverability for more detail.

Look at your sending pattern

A mailbox provider may be cautious when a domain suddenly changes behavior. Examples include:

There is no magic "safe volume" that applies to every business. The useful principle is consistency. If you are starting a new program or moving to a new sending platform, begin with engaged recipients, keep volume controlled, and watch delivery results before scaling.

Make the message easy to recognize

A recipient should quickly understand who sent the email and why. For marketing messages:

For transactional messages:

A good message cannot compensate for broken authentication, but unclear or unexpected content can hurt an otherwise healthy sender.

Check sender reputation, but do not chase one score

Sender reputation is the trust mailbox providers build over time from authentication, complaints, bounces, engagement, and sending behavior. There is not one universal score that determines whether every message reaches every inbox. A sender may perform differently at Gmail than at Outlook, and a single blocklist result is not always the explanation for a spam-placement issue. Use reputation checks as evidence, not as a verdict. Read how to check your email domain reputation for a practical approach.

Fix one confirmed cause at a time

When email goes to spam, it is tempting to change everything at once: update SPF, change the subject line, move providers, and resend the campaign. That makes diagnosis harder. Instead:

  1. Save a copy of the affected message and its headers.
  2. Identify the sending platform.
  3. Check SPF, DKIM, and DMARC.
  4. Compare results with the visible From address.
  5. Review recipient-list quality and recent sending changes.
  6. Make one documented fix.
  7. Send a new test message.
  8. Compare the new result.

This creates a record of what actually solved the problem.

Frequently asked questions

Why do my emails go to spam even though SPF passes? SPF is only one signal. DKIM, DMARC alignment, reputation, engagement, complaints, and list quality can still affect inbox placement. Will changing my DMARC policy fix spam placement? Not by itself. DMARC primarily protects your domain from unauthorized use and confirms alignment. It does not replace good sending practices or a healthy recipient list. Should I resend a campaign that went to spam? Usually not immediately. First identify why it went to spam. Repeatedly sending the same message to disengaged recipients can create more complaints. How long does it take to improve deliverability? A DNS correction may be visible after propagation, but reputation and engagement improvements take longer because mailbox providers need to observe healthier sending behavior over time.

The practical next step

Run a free check on your domain to review the public SPF, DKIM, and DMARC records. Then inspect a real spam-folder message from the sending platform you are troubleshooting. If the records are correct, move on to the list, sending pattern, and recipient experience. If a record changes later because of a new vendor or DNS edit, ongoing monitoring can help you catch it before it quietly affects important business email. Run a free Beacon domain check →

Want a free deliverability check for your domain?
Run a free check →