Why are my business emails going to spam?

Not spam.Just unproven.

Business emails go to spam when a mailbox provider can’t confirm they are from you, or hasn’t learned to trust them. The usual causes, in the order to check them: SPF, DKIM or DMARC missing, failing or not matching your From address; a sending address with a bad name; a new domain or a sudden jump in volume; a list with people who never asked; and a message that looks risky. The first step is to read three lines in one message’s headers. The finder below ranks the likely causes from your symptoms.

Find my cause Start free
SPF, DKIM, DMARC Read the headers no inbox promise

By the Builderify team

An example message, made up for this page

01 Read three lines 02 Fix what fails 03 Test it again
01 / The short answer

Why do business
emails go to spam?
A filter can’t vouch for them.

Spam filters work on risk, not on whether anyone has read your email. A message goes to spam when its signals look more like a scammer’s than a customer’s: it can’t prove it came from your domain, your sending address has no track record or a bad one, or the message itself looks wrong. A legitimate business email can trip all three without anyone doing anything wrong.

Of the three, proof is the one to check first, because you can see it and fix it in minutes. Google says messages that aren’t authenticated might be marked as spam or rejected, and that authenticated ones are less likely to be. Less likely isn’t never: trust and the message still count, which is what chapters 04 and 05 are for.

What a filter weighsThree groups
  • 01

    Proof

    Does it come from the domain it says?

    SPF, DKIM and DMARC: records in your DNS that say who may send as you, and a signature on the message.

    You fix it in your DNS

  • 02

    Trust

    Has this address earned a place?

    Age, sending volume, bounces, spam reports and, on shared hosting, the other senders on the same IP address.

    You build it over time

  • 03

    Message

    Does it look like what scammers send?

    Hidden text, misleading links, subjects that fake a reply, loud display names and big images with little text.

    You change it per email

The same groups run through the sender guidance from Google, Yahoo and Microsoft, read on 1 November 2026.

02 / Read the headers

How do you check why an email
went to spam?
Read three lines in its headers.

Open one message that landed in spam, or send a test to a Gmail address of your own, and read the SPF, DKIM and DMARC results in its original headers. It takes a minute, costs nothing and tells you whether the problem is setup or something else.

  1. 01

    Get a message to look at

    Use one that really landed in spam, or send a plain test from the same mailbox, tool or form to a Gmail address you own.

  2. 02

    Open its original headers

    Gmail: open the message, click the three dots next to Reply, then Show original. Yahoo Mail: More, then View raw message. Apple Mail: View, Message, All Headers. Outlook for desktop: open the message, then File, Properties, and read the Internet headers box.

  3. 03

    Read three results

    Find SPF, DKIM and DMARC. You want PASS on all three, and the domain beside SPF and DKIM should be yours: DMARC needs one of them to pass for the domain in From. The table below says what each failure means.

  4. 04

    Or paste them into Google’s tool

    Copy the headers, open Google Admin Toolbox’s Messageheader tool, paste them and click Analyze the header above. Headers hold addresses and server names, so paste them only into tools you trust.

What Gmail’s summary looks like when all three pass, with made-up values
What each result in a message’s headers usually means, and what to do about it
You see It usually means Do this
PASS on SPF, DKIM and DMARC The setup is fine for this message. Go to chapters 04 and 05: trust and content.
SPF: FAIL or SOFTFAIL The server that sent it isn’t one your SPF record allows. Add that sender to your one SPF record.
SPF: PERMERROR The domain has two SPF records, or its record needs more than ten DNS lookups. Merge them into one record and trim it.
DKIM: NONE, or no DKIM line The message wasn’t signed. Turn DKIM on at your email provider or tool.
PASS, but for another domain The sending service signed or sent it for itself, and DMARC can’t count that. Set up the tool’s custom sending domain so it uses yours.
DMARC: FAIL Neither SPF nor DKIM passed for the domain in From. Fix one of them first; both is better.
DMARC: NONE, or no result The domain publishes no DMARC policy. Publish a record that starts at p=none.

Menu paths from Google’s Trace an email with its full header page. A message passes DMARC when SPF or DKIM passes for the domain in From, as Google’s DMARC troubleshooting page says; ten DNS lookups is the SPF limit in Spamhaus’s sender guidelines and one record is the rule in RFC 7208. For the records themselves, see how to set up SPF, DKIM and DMARC.

03 / Cause finder

What is sending your
emails to spam?
Five answers, a ranked list.

Answer five questions and the finder ranks the likely causes for your situation, each with its own fixes. It is a ranked guess from what you tell it: it can’t see your mail, and the headers (chapter 02) settle it. It starts with a web host mailbox, Gmail and unread headers already chosen; change anything. Nothing you pick leaves your browser.

Cause finder · for business email
How do you send the email?
Where does it land in spam?
Who is it going to?
What do the headers say?
What else is true? Tick any

Web host mailbox · Gmail · Strangers · Headers unread

Read one message’s headers first.

They show whether SPF, DKIM and DMARC pass, and that settles the biggest question in a minute. Until then this is a ranked guess.

Gmail asks every sender for SPF or DKIM, valid reverse DNS and a spam rate under 0.3%, and bulk senders for more.

Most likely causes, in the order to check

  1. 1

    SPF, DKIM or DMARC is missing or failing

    Why it’s here You haven’t read the headers yet, so this can’t be ruled out.

    The headers show FAIL, SOFTFAIL, NONE or no line at all for SPF, DKIM or DMARC. Google says messages that aren’t authenticated might be marked as spam or rejected.

    1. 1Open one message’s original headers and read the SPF, DKIM and DMARC results (chapter 02).
    2. 2Add what is missing at your DNS host: one SPF record that lists every service sending as your domain, DKIM switched on at each of them, and a DMARC record that starts at p=none.
    3. 3Send a plain test to a Gmail address you own and read the headers again.

    Read next: How to set up SPF, DKIM and DMARC

  2. 2

    The server or IP address you send from has a bad name

    Why it’s here Mail from a web host may leave from a server it shares with other customers.

    On shared hosting or a shared tool, other customers’ sending shares your IP address. Google says mail from a blocklisted IP address is more likely to be marked as spam.

    1. 1Find the sending IP address in the message’s Received lines and look it up in a blocklist checker, such as Spamhaus’s.
    2. 2If it is listed, ask your host or tool how it is handled, and check your sent items and mail logs for messages you didn’t write: a hacked mailbox or site is one way an address ends up listed.
    3. 3If it stays listed, ask to be moved to another address, or send through an authenticated service on your own domain.

    Read next: Look up an IP address at Spamhaus · What bounce codes mean

  3. 3

    The message itself looks risky

    Hidden text, misleading links, link shorteners, subjects that fake a reply and big images with little text are what scam email uses. Google asks for visible, understandable links and honest headers and names.

    1. 1Link to your own domain instead of a link shortener, and keep links few and visible.
    2. 2Write a subject that matches what is inside, and don’t start with Re: or Fwd: unless it is a reply.
    3. 3Keep the display name to your business or your name, with no “URGENT” or “Last chance”.

    Read next: What every marketing email needs

  4. 4

    Some recipients never asked, or the list has gone stale

    Why it’s here People who haven’t heard from you may report it as spam.

    Bought addresses, old lists and people who never signed up produce bounces and spam reports. Google asks senders to keep reported spam under 0.10% and never reach 0.30%: on 1,000 emails, 0.10% is one report.

    1. 1Stop writing to anyone who never signed up, and to addresses that bounce.
    2. 2Make unsubscribing easy to find, so people can leave instead of reporting you as spam. Google says spam reports lower a domain’s reputation over time.
    3. 3Confirm new sign-ups by email before adding them to a list, which Google recommends.

    Read next: What bounce codes mean · Who you may email

A ranked guess, not a diagnosis

The finder weighs what you tell it. It can’t see your mail or your DNS, so where the headers disagree with an answer, believe the headers.

Change one thing at a time

After each fix, send a plain test to a Gmail address you own and read the headers again. Google notes that it can take time for improvements to show in spam classification, so don’t stack changes and then guess which one worked.

A form, not a mailbox?

A contact form that sends through your server has checks of its own. WordPress contact form not sending email reads pasted headers and ranks the causes for forms and plugins.

04 / The usual causes

What are the usual reasons
business emails go to spam?
Nine, from setup to the message.

Work down the list: proof first, then the sending address, then your list, then the message. Proof is the cheapest to check, and until it passes every other fix is guesswork. The last row is the odd one out, because the cause there isn’t yours.

The nine usual causes of business email going to spam, how each shows up and the first fix, in the order to check them
Cause How it shows up First fix
01SPF, DKIM or DMARC is missing or failing The headers show FAIL, SOFTFAIL, NONE or no line at all for SPF, DKIM or DMARC. Google says messages that aren’t authenticated might be marked as spam or rejected. Open one message’s original headers and read the SPF, DKIM and DMARC results (chapter 02).
02A tool or form sends as your domain but doesn’t sign with it SPF or DKIM passes, but for the sending service’s domain rather than yours, so DMARC can’t count it. A message passes DMARC when SPF or DKIM passes for the domain in From. Find the tool’s setting for a custom or branded sending domain, often called domain authentication, and add the DKIM and SPF records it shows you.
03A free address is in From, but a site or tool sends it A Gmail, Outlook or Yahoo address in From can’t pass DMARC when someone else’s server sends the message. Google’s sender guidelines say not to impersonate Gmail From addresses and warn that it can hurt delivery. Send from an address on your own domain.
04The server or IP address you send from has a bad name On shared hosting or a shared tool, other customers’ sending shares your IP address. Google says mail from a blocklisted IP address is more likely to be marked as spam. Find the sending IP address in the message’s Received lines and look it up in a blocklist checker, such as Spamhaus’s.
05A new domain or mailbox has no history yet A provider has nothing to judge a new domain by, so it is careful. Google’s advice is to start with a low volume to engaged people and grow it slowly. Start with people who know you and will reply. Google says messages from an address in the recipient’s contacts are less likely to be marked as spam.
06Your sending volume jumped Google advises against sudden spikes and says suddenly doubling previous volume can lead to rate limiting or a drop in reputation. Drop back to the volume you were sending before and hold it for a while.
07Some recipients never asked, or the list has gone stale Bought addresses, old lists and people who never signed up produce bounces and spam reports. Google asks senders to keep reported spam under 0.10% and never reach 0.30%: on 1,000 emails, 0.10% is one report. Stop writing to anyone who never signed up, and to addresses that bounce.
08The message itself looks risky Hidden text, misleading links, link shorteners, subjects that fake a reply and big images with little text are what scam email uses. Google asks for visible, understandable links and honest headers and names. Link to your own domain instead of a link shortener, and keep links few and visible.
09Only some people are affected: their own filter A company’s mail filter, or one person’s rules, can send your message to spam even when your setup is sound. If the same message reaches other inboxes, the cause is on their side. Ask them to open their spam or quarantine folder, mark your message Not spam and add your address to their contacts.

Sender requirements and sending advice from Google’s email sender guidelines, Yahoo’s Sender Hub and Microsoft’s sender support, read on 1 November 2026. Link shorteners and heavy images are listed as content triggers by DNSimple.

05 / If it still lands in spam

What if SPF, DKIM and DMARC
all pass?
Then it is trust, and it takes time.

Passing proves who sent the message, not that the provider trusts you yet. What is left is your spam rate, your list and the message, and none of them changes in an afternoon. Google says it can take time for an improved spam rate to show in spam classification, so change one thing at a time.

  1. 01

    Check your spam rate

    Google’s Postmaster Tools shows how often Gmail users mark your messages as spam. Google asks senders to keep the rate below 0.10% and never reach 0.30%: on 1,000 emails, 0.10% is one report.

  2. 02

    Ask a few people to rescue it

    Ask recipients to mark a message Not spam, reply, or add you to their contacts. Google says messages from an address in the recipient’s contacts are less likely to be marked as spam, and that Not spam marks help future messages reach the inbox.

  3. 03

    Look up your domain

    Google lists a Safe Browsing check in its troubleshooting steps: look up your domain, and any domains linked to yours, on its Safe Browsing site status page.

  4. 04

    Don’t judge by open rates

    Google says it doesn’t track open rates and that low opens aren’t necessarily a sign of a spam problem. Apple Mail also loads tracking pixels whether or not an email is read: see why open rates lie.

06 / In Builderify

Builderify and spam folders:
checked before the first send.

Builderify doesn’t change how your everyday mailbox is set up: the records for Google Workspace, Microsoft 365 or your host stay in your own DNS. It covers the part where business email turns into bulk. Broadcast and Sequences send from your own domain, and the Inbox catches what comes back.

01

Checked before the first send

Broadcast checks SPF, DKIM and DMARC before your first send. You add the records shown in your dashboard, wait for them to verify, then send.

02

Your own domain, with limits

Campaigns and sequences go out from your own verified domain, and per-organization hourly limits protect your sender reputation.

03

Unsubscribes built in

Every send carries an unsubscribe link and supports one-click opt-out. Unsubscribed and bounced addresses are skipped.

04

Problems come back to you

Replies, bounces, unsubscribes and abuse reports are sorted into their own mailboxes in your Inbox, so a reputation problem shows while it is still small.

What it costs

Pay per email, not per month.

One recipient on one broadcast or sequence email costs 0.5 credits. Every account gets 250 free credits a month, and there is no monthly fee. See the pricing page for the whole rate card.

250 free

credits every month, with no monthly fee

0.5 credits

per email sent, per recipient

From $9

for a one-time pack of credits that never expire

When it isn’t the right fit

It won’t fix mail sent from your Google Workspace, Microsoft 365 or host mailbox, because those records are yours to set, and the first half of this page is how. It can’t promise the inbox: nobody can, and Google says it doesn’t accept allowlist requests from email providers. If you send a few one-to-one emails a day, you don’t need it. For the law on what a marketing email must contain, see the CAN-SPAM checklist.

Fix the records first with the SPF, DKIM and DMARC guide, then send campaigns from a domain that has passed the check, and read what comes back in your Inbox.

Start free
Questions

Business emails and spam, answered.

A mailbox provider couldn't confirm the email came from you, or hasn't learned to trust it. The usual causes are SPF, DKIM or DMARC missing or failing, a sending address with a bad name, a new domain or a sudden jump in volume, recipients who never asked, and a message that looks risky. Read one message's headers first: they show whether the setup passes.

Open its original headers: in Gmail, click the three dots next to Reply and choose Show original. Find SPF, DKIM and DMARC and look for PASS on all three. DMARC passes when SPF or DKIM passes for the domain in From, so a fail points at your setup and a pass points at trust or content.

Passing proves who sent the message, not that the provider trusts you yet. What is left is your spam rate, a new or quiet sending address, recipients who never asked and the message itself. Google asks senders to keep the user-reported spam rate under 0.10% and never reach 0.30%, and says improvements can take time to show.

Google gives no time. Authentication fixes show in the next message's headers, but trust takes longer: Google says it can take time for an improved spam rate to show in spam classification. Change one thing at a time, send a plain test to a Gmail address you own after each change, and read its headers again.

Yes. Broadcast checks SPF, DKIM and DMARC on your domain before your first send, sends from your own verified domain and applies per-organization hourly limits. It can't promise inbox placement, and the records for your everyday mailbox stay in your own DNS.

One recipient on one broadcast or sequence email costs 0.5 credits. Every account gets 250 free credits a month, enough for 500 emails if you use them on nothing else, and there is no monthly fee. One-time credit packs start at $9 and never expire.

Sources

The provider pages were read on 1 November 2026. Gmail, Yahoo and Microsoft change what they ask of senders from time to time, so check their pages before you rely on a detail. The Builderify details come from the module pages, the rate card on this site and the product itself. The shop and the message in the pictures are made up.

← All guides

Stop losing the visitors
you already paid for.

More leads from the traffic you already have, and follow-up that sends itself. Free to start. No card, no monthly fee.

Start free See what it does