Why Are My Business Emails Going to Spam?

31 min readWebsite Management
GW
GoWebsited
Published 18 November 2026 · Updated 18 November 2026

Why are my business emails going to spam?

Usually because the inbox provider cannot confirm the message really came from your business, or because your domain’s sending reputation is weak or damaged. Gmail, Yahoo and Outlook check records on your domain called SPF, DKIM and DMARC, watch how many people mark your mail as spam, and Gmail also looks at how steadily you send. Start by reading the headers of a message that landed in spam to see which check failed. Then fix authentication in a safe order, SPF first, DKIM second and DMARC last, starting at a policy of none, and check the emails your website and other tools send in your name. Nobody can promise inbox placement, but these steps remove the causes you control.

Key takeaways

  • Identity comes first. Gmail, Yahoo and Outlook all check SPF, DKIM and DMARC, so prove the mail is yours before you rewrite a single subject line.
  • Diagnose before you fix. The Authentication-Results line in a filtered message tells you which check failed and where to start.
  • Set up in order. SPF, then DKIM, then DMARC at p=none, tightening to quarantine and reject only when the reports look clean.
  • Website forms need their own fix. Send form emails through an authenticated mail service, from your own domain, with Reply-To set to the visitor.
  • Guard your reputation. Gmail asks senders to keep spam complaints below 0.1%, so email only people who asked to hear from you and remove addresses that bounce.

What this guide covers

  1. How inbox providers decide what is spam
  2. Find out what is really happening first
  3. SPF, DKIM and DMARC in plain English
  4. Setting up SPF without breaking it
  5. Turning on DKIM signing
  6. Adding DMARC, then tightening it slowly
  7. What Gmail, Yahoo and Outlook now require
  8. Why your website’s form emails land in spam
  9. Newsletters and other tools that send for you
  10. New domain or new mailbox? Build trust gradually
  11. Content and links that trip filters
  12. Complaints, bounces and old lists
  13. Is your domain on a blocklist?
  14. Forwarding, free addresses and other traps
  15. The fix, in order
  16. Frequently asked questions

How inbox providers decide what is spam

It is tempting to blame the words. Maybe the subject line said free, or the invoice had one exclamation mark too many. Wording can play a part, but the published rules from the big inbox providers say far more about who is sending than about what the message says.

No provider publishes its full recipe, and filters change all the time. Their sender guidelines do show what they weigh, and it comes down to four things:

  • Identity. Is the message really from the domain in the From line? Authentication records answer that.
  • Reputation. What is the track record of the domain and of the server that sent the message? Complaints and bounces count against it.
  • Behaviour. Does the sender email at a steady pace, to people who expect it, or in sudden bursts to lists nobody remembers joining?
  • Content. Are the links clear, the subject line honest and the message built to standard?

Google’s list of the top 10 Gmail sender issues opens with identity: “Whether you send large or small volumes of email, it is important to establish a trusted online identity.” That applies to a two-person bookkeeping firm sending invoices as much as to a retailer sending newsletters. The same page talks about both “domain or IP address reputation”, which is why the server that sends your mail matters as well as your domain name.

This is why rewording an email does not fix a spam problem caused by failed authentication. Spam filters want to know who you are before they care what you wrote. If the identity check fails, even a polite, plain message can look like a forgery.

“Spam filters want to know who you are before they care what you wrote.”

Find out what is really happening first

Before you change a single DNS record, find out what is actually failing. A few minutes of checking saves you from fixing the wrong thing, or from breaking something that works. Start with three questions.

  • Is it spam, or is it a bounce? A message in the spam folder was accepted and then filtered. A message that came back to you with an error was refused. The error text usually names the reason, so read it before you delete it.
  • Is it everyone, or one provider? If only Outlook.com or Hotmail addresses miss your mail, look at what that provider requires. If every provider files you as spam, look at your domain’s setup first.
  • Is it every message, or one kind? Everyday email, invoices from accounting software, newsletters and website form notifications often leave through different systems. If only one kind lands in spam, that system is your suspect.

Then look inside a message that landed in spam. Every email carries headers: technical lines that record where it came from and which checks it passed. Gmail’s help page on how to trace an email with its full headers explains the route: open the message, open the More menu next to Reply and choose Show original. In Outlook on a computer, the same page says to click File, then Properties, and read the Internet headers box.

Google’s guide to troubleshooting DKIM adds that “You can see if an email passed DKIM authentication in Gmail” by finding the Authentication-Results header. That one line is the best place to start, because it holds the receiving server’s verdict on all three checks.

What to look for in the message headers

  • Authentication-Results. The receiving server’s verdict. Look for spf=, dkim= and dmarc=, each followed by a result such as pass, fail, softfail or none.
  • Which domain passed. Each result names a domain. If DKIM passed for your newsletter tool’s domain but not for yours, that tool is not yet signing as you.
  • The From address and the return address. The address your customer sees and the hidden address that bounces go to can be on different domains. DMARC needs one of the checks to pass for the domain in the From line.
  • Received lines. Read from the bottom up, these show each server the message passed through, starting with the one that sent it. Note that first server’s name and address.

Test inboxes Create a free Gmail account and a free Outlook.com account just for testing. After every change, send an everyday message, an invoice and a website form submission to both, then check which folder each one lands in and read its headers.

If you send to a lot of Gmail users, Google Postmaster Tools adds a view from Google’s side. Google says its Postmaster Tools dashboards “let you view various data about outgoing email you send to personal Gmail accounts”, including your spam rate, authentication results and delivery errors. You have to verify your domain first, and Google notes that the dashboards “might not include all data on days when outgoing email volume is low”, so a small business may see little there at first. It is still worth setting up before you need it.

SPF, DKIM and DMARC in plain English

These three records live in your domain’s DNS, the public settings that also point visitors to your website and mail to your inbox. Each answers a different question, and they work best together.

Think of your business mail as parcels leaving a warehouse. SPF is the list of couriers allowed to collect parcels from your door. DKIM is a tamper-evident seal with your company stamp on every parcel. DMARC is the notice on your door telling everyone what to do with a parcel that claims to be yours but has neither an approved courier nor an intact seal, and asking them to send you a note about it.

SPF

A list of the servers and services allowed to send email for your domain. Receiving servers check whether the server that delivered a message is on it.

DKIM

A digital signature on each message. Receiving servers use a public key in your DNS to confirm the message came from you and was not changed on the way.

DMARC

Your policy for messages that fail. It also checks that SPF or DKIM passed for the domain in the From line, and it sends you reports.

Reputation

The track record behind your domain and your sending servers. Authentication tells receivers who you are; reputation tells them whether to trust you.

The Canadian Centre for Cyber Security’s quick guide to email configuration describes DMARC as the protocol that “chooses what to do with the information taken from SPF and DKIM”. That is why DMARC comes last in the setup order: it builds on the other two.

One idea makes the rest of this guide easier: alignment. SPF and DKIM can pass for a domain that is not yours, for example your newsletter platform’s own domain. Gmail’s email sender guidelines say that for bulk senders “the domain in the sender’s From: header must be aligned with either the SPF domain or the DKIM domain.” In plain terms, the domain your customers see has to match a domain that passed the checks.

Our guide to domain names and business email covers where these records sit alongside the rest of your DNS settings. This guide is about using them to fix delivery, one record at a time.

Setting up SPF without breaking it

SPF is a single line of text, published as a TXT record on your domain. It lists every service allowed to send mail using your domain, and it ends with an instruction about everyone else.

Here is its general shape, as a made-up illustration for example.com: v=spf1 include:(your email provider) include:(your newsletter tool) ~all. Your email provider and each sending tool give you the exact value to add, so copy theirs rather than anyone else’s record.

Google’s Workspace guide to setting up SPF says “SPF helps prevent your outgoing email from being marked as spam by receiving email servers.” It also reminds owners: “If you start using a new mail server or third-party sender, make sure to update your SPF record.” That second line is where SPF quietly breaks. A new tool starts sending, nobody updates the record, and its messages start failing.

Three rules keep SPF working.

  • One record per domain. The SPF standard, RFC 7208, says “A domain name MUST NOT have multiple records that would cause an authorization check to select more than one record.” If a second SPF record appears, the check ends in an error instead of a pass. When you add a service, edit the record you already have.
  • Ten lookups at most. The same standard says “SPF implementations MUST limit the total number of those terms to 10”, meaning the parts of the record that need extra DNS lookups, and must return an error once the limit is passed. Every include counts, and some includes contain more includes, so remove services you no longer use before adding new ones.
  • Choose the ending on purpose. Google’s guide uses ~all and says it “tells receiving servers to mark messages as spam if they’re from servers that aren’t listed in the SPF record.” The Canadian Centre for Cyber Security’s email domain protection guidance recommends the stricter -all, which marks every unlisted sender as unauthorized. Either way, list every legitimate sender first.

Changes are not instant. Google says “It can take up to 48 hours for SPF authentication to start working”, so test again the next day before deciding a change did not work.

Two SPF records A second SPF record is one of the easiest ways to break your email by accident. It tends to appear when a new tool’s setup guide says to add a TXT record and someone creates a whole new SPF line instead of adding the tool to the existing one. Check for duplicates every time you add a service.

Turning on DKIM signing

DKIM adds a digital signature to every message you send. The Cyber Centre’s quick guide puts it simply: DKIM “places a signature on outgoing emails”. Your email service signs each message with a private key, you publish the matching public key in your DNS, and receiving servers use it to check the signature. If the message was changed on the way, or was never signed by you, the check fails.

Unlike SPF, DKIM is usually something you switch on rather than write yourself. The steps usually follow the same pattern:

  • Find the DKIM or email authentication setting in your email provider’s admin area.
  • Generate a key. The provider gives you a record name, usually a short label followed by ._domainkey and your domain (Google’s example is google._domainkey), and a long value.
  • Add that record at your DNS host exactly as given. Long keys can hit length limits: Google notes that you “can not enter a 2048-bit key as a single text string with a 255-character TXT record limit”, so follow your DNS host’s instructions for splitting it.
  • Go back to the provider, turn signing on, then send yourself a test and check the headers for dkim=pass on your own domain.

Do the same for every service that sends as you: the newsletter tool, the booking system, the invoicing software. The Cyber Centre’s domain protection guidance explains that for third-party mail to pass, messages “must be signed using a private key with a corresponding DKIM record published for the domain.” In practice, that usually means turning on the tool’s domain authentication setting and adding the records it gives you.

DKIM matters even when SPF passes. SPF judges the server that handed over the message: the standard notes that “SPF evaluation is based on the IP address of the “last” sending SMTP server.” A DKIM signature travels inside the message, so it can still be checked after a message has been passed along, as long as nobody changes it on the way.

Adding DMARC, then tightening it slowly

DMARC ties SPF and DKIM to the domain your customers see, tells receiving servers what to do when a message fails, and sends you reports about who is sending mail as you. It is another TXT record, published at _dmarc followed by your domain.

A starting record for example.com, as an illustration only, looks like this: v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com. The p tag is your policy. The rua tag is the address where receiving servers send aggregate reports.

The policy has three settings. The current DMARC standard, RFC 9989, published in May 2026, describes them from the domain owner’s point of view:

  • none: “The Domain Owner offers no expression of preference.” Mail is handled as it would be anyway, and you receive reports.
  • quarantine: “The Domain Owner considers such mail to be suspicious.” The Cyber Centre’s quick guide says the message is then “placed in a spam or junk folder for review”.
  • reject: the owner treats every failure as “a clear indication that the use of the domain name is not valid.” Receiving servers may refuse failing mail outright.

Start at none. The standard itself says “For best results, Domain Owners usually start with “p=none”” and gives the reason: “to ensure that nothing’s been missed in the initial SPF and DKIM deployments.” The reports are how you find out. They show, in the standard’s words, “sources of mail using the Author Domain”, so a few weeks of them will show you the services sending as your domain, including any you had forgotten.

Reports are written for software rather than for people, so a report reading tool or service makes them much easier to use. Send them to a separate address so they do not crowd your inbox.

When the reports show every legitimate sender passing, tighten in stages. The Cyber Centre’s guidance describes gradually increasing enforcement “from a baseline of none, through quarantine, to an end state of reject”. A sensible pace for a small business looks like this:

  • Several weeks at none, reading reports and fixing every legitimate sender that fails.
  • Move to quarantine and keep reading reports. Watch for customers who say your mail went missing.
  • When quarantine has run cleanly for a similar period, move to reject.

Never start at reject Publishing a reject policy before every legitimate sender passes can block your own invoices, newsletters and form notifications, and you may not notice until a customer asks why they never heard from you. Start at none, read the reports, then tighten one step at a time.

What Gmail, Yahoo and Outlook now require

In 2024 and 2025 the biggest inbox providers turned long-standing advice into written rules. Google’s sender guidelines FAQ says Gmail’s requirements for bulk senders began in February 2024, and Yahoo’s sender best practices name the same month as the start of its enforcement. The rules for every sender already include authentication, so they matter even if you only send a few dozen emails a day.

Gmail and Yahoo: rules for every sender

  • SPF or DKIM authentication for the domain you send from.
  • Valid forward and reverse DNS records for the servers that send your mail.
  • A spam complaint rate below 0.3%. Gmail asks senders to stay below 0.10% and avoid ever reaching 0.30%.
  • Messages formatted to the internet message standard, RFC 5322.
  • Gmail also asks for a TLS connection, and says: “Don’t impersonate Gmail From: headers.”

Then come the rules for bulk senders. The same FAQ defines a bulk sender as one that “sends close to 5,000 messages or more to personal Gmail accounts within a 24-hour period”. It adds that “Messages sent from the same primary domain count toward the 5,000 limit” and that senders who reach that level once “are permanently considered bulk senders.”

Extra rules for bulk senders

  • Both SPF and DKIM, not just one of them.
  • A DMARC record. Gmail says your policy “can be set to none”, and Yahoo asks for “at least p=none”.
  • The domain in the From line aligned with the SPF or DKIM domain.
  • One-click unsubscribe on marketing and subscribed messages. Yahoo also asks bulk senders to “Honor unsubscribes within 2 days”.

Microsoft followed in 2025. Its announcement for Outlook.com, the service behind hotmail.com, live.com and outlook.com addresses, covers domains “sending more than 5,000 emails per day”. For those senders SPF and DKIM must pass, and DMARC must be “At least p=none and align with either SPF or DKIM (preferably both).” An update to the post says messages that fail are rejected rather than sent to junk, with an error that begins “550; 5.7.515 Access denied”.

Enforcement keeps tightening. Google’s FAQ says “Starting November 2025, Gmail is ramping up its enforcement on non-compliant traffic”, and that messages from senders who do not meet the requirements “might be rejected or delivered to recipients’ spam folders.”

Under 5,000 a day? If you send far fewer than 5,000 emails a day, meet the bulk rules anyway: part of them already applies to every sender, one large newsletter can push you over the line, and Gmail treats a sender that crosses it once as a bulk sender permanently.

Why your website’s form emails land in spam

If customers say they filled in your contact form and you never saw it, check your spam folder first, then look at how your website sends email. Form notifications are easy to overlook because nobody sends them by hand.

When someone submits a form, the website builds an email and hands it to a mail system. On many WordPress sites that is the web server itself: WordPress’s developer documentation describes its wp_mail function as one that “Sends an email, similar to PHP’s mail function”. A web server sending this way often has no DKIM signature for your domain and may not be listed in your SPF record, so the message fails the very checks this guide is about.

Two common settings make it worse.

  • A From address the server cannot vouch for. WordPress’s own code builds a default From address of wordpress@ followed by your site’s domain. If your SPF record does not include the web server and nothing signs the message with DKIM, that address fails.
  • The visitor’s address in the From line. Some forms send the notification as if it came from the visitor, perhaps from a Gmail address. Your web server is not allowed to send for that domain, and Google’s guidelines are blunt: “Don’t impersonate Gmail From: headers.”

A success message proves less than it seems, too. The same WordPress documentation says “A true return value does not automatically mean that the user received the email successfully.” The form can thank the visitor while the email goes nowhere useful.

On shared hosting there is one more problem: your website’s server address is shared with other websites. Google’s sender issues list warns that “Using the same IP address or domains for multiple senders can result in a low domain or IP address reputation”, and you have no control over what the other sites send.

The fix has three parts:

  • Send form email through an authenticated mail service (SMTP), using an account with your email provider or a transactional email service that is included in your SPF record and signs with DKIM for your domain.
  • Keep the From address on your own domain, such as website@ followed by your domain, so it passes your own checks.
  • Set the Reply-To address to the visitor’s email, so pressing Reply still answers them.

Keep a copy of every submission inside the website as well, so an enquiry is never lost even if an email is. Our guide to website hosting for small business explains why email and hosting are better kept separate, and our website launch checklist includes testing every form before a site goes live. Test again after any change to your email provider or DNS.

A hand on a laptop trackpad with an email open on the screen, beside a small potted plant on a light table
Most delivery problems are invisible from the sending side: the email leaves your outbox and never reaches the inbox.

Newsletters and other tools that send for you

Count the systems that send email with your domain in the From line. It is often more than you think: your mailbox provider, the website, a newsletter platform, invoicing or accounting software, a booking system, a customer database, an online shop. Each one is a sender, and receiving servers judge all of them by your domain’s records.

Each needs to be authorized. The Cyber Centre’s quick guide warns that mail from “third-party domains that are not included may be labelled as spam”. For every tool on your list:

  • Add it to your one SPF record if it sends from its own servers using your domain.
  • Turn on its domain authentication so it signs with DKIM for your domain.
  • Check that the domain in its From line matches a domain that passes, so DMARC alignment works.
  • Send yourself a test and read the headers before the first real campaign or invoice run.

Google’s guidelines add a check on the tool itself: “Verify that the provider follows the guidelines on this page.” A tool that cannot authenticate as your domain will keep failing your checks.

Marketing tools carry extra duties. Gmail requires that “Marketing messages and subscribed messages must support one-click unsubscribe” for bulk senders, and Yahoo asks bulk senders to honour unsubscribes within 2 days. Check that your platform supports one-click unsubscribe, and never remove or hide its unsubscribe link to keep people on your list.

Make one person responsible for the list of senders. When a tool is retired, remove it from SPF. When one is added, authenticate it before it sends anything. Old includes that nobody uses still count toward SPF’s ten-lookup limit.

New domain or new mailbox? Build trust gradually

A brand-new domain has no sending history, and receiving servers have nothing to judge it by except its setup and its first messages. Google’s list of sender issues notes that steady sending is “particularly important for new domains as they establish their sending reputation.” That is why a new business email can land in spam even when nothing is misconfigured.

Gmail’s guidelines say to “Start with a low sending volume to engaged users, and slowly increase the volume over time”, and to “Avoid introducing sudden volume spikes if you do not have a history of sending large volumes.” In practice:

  • Set up SPF, DKIM and DMARC before the first email leaves the new domain, not after the first complaint.
  • Start with everyday conversations: replies, quotes and invoices to people who expect to hear from you.
  • Do not import a large list and send a campaign on day one. Grow your volume week by week.
  • If a regular contact finds one of your messages in spam, ask them to mark it as not spam and reply.

The same caution applies when you change things. Moving to a new email provider, rebranding to a new domain or moving your website can all change which servers send as you. Gmail’s guidelines say that after “any significant changes to your sending infrastructure” you should “increase the modified segment of traffic separately.” Our website migration checklist has a step on protecting your email and DNS records during a move, because a DNS change that drops your SPF or DKIM records sends you straight back to square one.

A new mailbox on an established, authenticated domain is a different case. If one new staff address lands in spam while everyone else’s mail arrives, look at how that mailbox sends: a phone app, a scanner or a tool connected with the wrong settings can send through a server your records do not cover.

Content and links that trip filters

Content still matters. Gmail’s sender guidelines are less about banned words than about honesty and clarity. Among them:

  • “Web links in the message body should be visible and easy to understand.”
  • Do not start subject lines with Re: or Fwd: unless the message really is a reply or a forward.
  • “Don’t use HTML and CSS to hide content in your messages.”
  • “Don’t mix different types of content in the same message.”
  • “Don’t use emojis or other non-standard characters to imitate graphic elements in messages.”

Habits that follow from those rules:

  • Use full, readable links to your own domain, so readers and filters can see where a link goes.
  • Write a subject line that says what the email is. “Invoice 1042 from Example Plumbing” beats “Quick question!!”
  • Keep invoices, receipts and appointment reminders free of promotions, and send offers separately to people who asked for them.
  • Make sure the message still makes sense if images do not load. A single large image with no text gives readers little to go on.
  • Send attachments people expect, named clearly. An unexpected attachment from an unfamiliar address is exactly what a phishing email looks like.

Fix the identity first. A better subject line cannot rescue a message that fails authentication. But if one specific message keeps landing in spam while your everyday mail arrives, content becomes the likely suspect: compare it, line by line, with a message that gets through.

“Fix the identity first. A better subject line cannot rescue a message that fails authentication.”

Complaints, bounces and old lists

Every click on Report spam counts against you. Gmail’s guidelines say to “Keep spam rates reported in Postmaster Tools below 0.10% and avoid ever reaching a spam rate of 0.30% or higher.” Yahoo’s sender hub sets its own line at the same level: “Keep your spam rate below 0.3%”. In plain numbers, 0.3% is 3 complaints for every 1,000 messages, and 0.1% is 1 in 1,000.

Google is also clear about what happens if you stay above it: “Maintaining a high spam rate can result in increased spam classification for your messages.” Complaints come from people who do not remember agreeing to hear from you, or who cannot find a way out. Gmail’s answer is simple: “you should send email only to people who want to get messages from you.”

Bounces are the other warning sign. Yahoo’s sender hub says to “Monitor hard and soft bounces as well as inactive recipients” and to “Remove invalid recipients from your list promptly”. Microsoft’s Outlook guidance gives the same advice: “Remove invalid addresses regularly”.

Old lists combine both problems. Addresses go out of use, people forget they signed up, and a list that sat untouched for a long time can produce a burst of bounces and complaints in a single afternoon. Before you email a list you have not used in a long time:

  • Remove every address that has bounced.
  • Separate people who clearly opted in from everyone else.
  • Send a short reconfirmation to inactive subscribers, as Yahoo suggests, and keep only those who say yes.
  • Never buy or rent a list.

In Canada there is a legal side as well. Our guide to CASL for small business websites covers consent, identification and unsubscribing, which happen to be the same habits that keep complaint rates low. It is a plain-language overview, not legal advice.

Is your domain on a blocklist?

Blocklists, sometimes called blacklists, are lists of domains and server addresses seen sending spam, which mail servers consult when deciding what to refuse or filter. MxToolbox’s page on blacklist problems describes a blacklist as “a spam blocking list, that can prevent your mail server from sending email” and warns that while you are listed, some of your email “may never be delivered”.

The same page recommends starting with a Blacklist Check, its lookup tool, and other blocklist checkers work the same way. Check two things:

  • your domain
  • the address of the server that sent a message which landed in spam, taken from the first Received line in its headers

If you are listed, find the cause before you ask for removal. Look for problems like these:

  • A hacked mailbox or website sending spam in your name. Change passwords and turn on two-step verification.
  • A contact form abused by bots, especially one that sends a copy of each message to whatever address the visitor types in.
  • A campaign sent to an old or bought list, which brings bounces and complaints together.

Each list explains its own removal process on its website. Fix the cause first, or the listing is likely to come back. And if a shared web server your site sends through is listed because of someone else, sending your form email through your authenticated email service, as described above, takes that server out of the picture.

Forwarding, free addresses and other traps

A few setups cause trouble even when your records are correct.

Automatic forwarding. If your business address forwards to another inbox, the forwarding server passes along mail it did not originally send. Because SPF judges the last server in the chain, the standard acknowledges that SPF can “return “fail” for mail that is ultimately legitimate”, giving mail that has passed through an alias as its example. Yahoo asks anyone who forwards email to “implement ARC (Authenticated Received Chain)”, a way of recording the checks a message passed before it was forwarded. For your own business mail, the simplest fix is to read it in a real mailbox at your domain rather than forwarding it to a personal account.

Free addresses on business mail. Sending business email from a free personal account is a trust problem with customers before it is a spam problem. If your website or newsletter tool is set to send from a free address, change it to an address at your own domain, because that tool cannot authenticate as a domain it does not control.

A Reply-To nobody reads. Microsoft’s Outlook guidance recommends a From or Reply-To address that is valid and “reflects the true sending domain”. Use real, monitored addresses, not a no-reply address that bounces.

Domains you never send from. Spare domains, old brand names and look-alike domains you bought to protect your name can be used by others to send mail that looks like yours. The Cyber Centre’s domain protection guidance gives the records for a domain that sends no email: an SPF record of v=spf1 -all and a DMARC policy of reject, so receiving servers refuse anything claiming to come from it.

DNS changes that drop records. Moving your website, your DNS host or your nameservers can quietly remove SPF, DKIM or DMARC records. Write every record down before any change, and test sending straight afterwards.

A simple record sheet helps with all of these: one document listing every DNS record on your domain, what each one is for and who added it. When something breaks, it shows at a glance what changed, and it makes the next change far less risky.

The fix, in order

If your emails are going to spam and you are not sure where to start, work through this list in order. Each step builds on the one before it.

  1. Confirm the symptom. Find a message that landed in spam, note which provider filtered it and read its Authentication-Results line.
  2. List every sender. Write down every service that sends email using your domain: mailboxes, website, newsletters, invoicing, bookings and anything else.
  3. Fix SPF. One record, every legitimate sender included, unused services removed and no more than 10 lookups.
  4. Turn on DKIM. Enable signing for your domain with your email provider and in every tool that sends for you, then check for dkim=pass.
  5. Publish DMARC at p=none. Add a reporting address and read the reports for a few weeks to find any sender you missed.
  6. Repair your website forms. Send through an authenticated mail service, from an address on your domain, with Reply-To set to the visitor.
  7. Clean your lists. Remove bounced addresses, stop emailing people who never opted in and make unsubscribing a single click.
  8. Check your reputation. Look up your domain on a blocklist checker and, if you send to many Gmail users, set up Postmaster Tools.
  9. Tighten DMARC slowly. Move to quarantine, then reject, only when the reports show every legitimate sender passing.
  10. Re-test after every change. Send to your free Gmail and Outlook.com test accounts and confirm where each message lands.

Steps 1 to 6 deal with identity. Steps 7 to 10 protect your reputation once your mail can prove where it came from.

Email setups drift. A new tool gets added, a record gets edited, a staff member connects an app on a phone. Put a short check on the calendar every few months: re-read your SPF record, glance at your DMARC reports and send a test to each of your test accounts. It takes minutes, and it catches problems before your customers do.

Want business email that is set up properly?

Every GoWebsited plan includes professional email at your own domain, set up for you, along with your hosting, domain and SSL. Nothing here is billed separately.

See our plans

Frequently asked questions

Why are my emails going to spam all of a sudden?

A sudden change usually means something changed on your side. A new tool may have started sending as your domain, a DNS change may have removed or duplicated your SPF record, a campaign may have drawn complaints, or a mailbox or website may have been compromised. Read the headers of a recent message in spam to see which check failed, then work back to what changed.

How do I stop my business emails going to spam?

Start by reading the headers of a filtered message to find the failing check. Then make sure SPF, DKIM and DMARC are set up for every service that sends as you, fix the emails your website forms send, email only people who asked to hear from you, and remove addresses that bounce.

Do I need SPF, DKIM and DMARC?

Gmail and Yahoo require SPF or DKIM from every sender, and bulk senders need all three. Below the bulk threshold, having all three set up correctly is still the clearest way to show receiving servers that your mail is really yours.

What does DMARC do, in simple terms?

DMARC tells receiving servers what to do with mail that claims to come from your domain but fails SPF and DKIM, and it sends you reports on who is sending mail as you. Its policy can be none, quarantine or reject.

Why do my website contact form emails go to spam?

Form emails are often sent by the web server without authentication, or from an address the server is not allowed to use, such as the visitor’s own address. Send them through an authenticated mail service, keep the From address on your own domain and set Reply-To to the visitor.

How do I check if my domain is blacklisted?

Use an online blocklist checker to test your domain and the address of the server that sent a filtered message. If you are listed, fix the cause first, then follow that list’s own removal process.

Does Gmail require DMARC for small businesses?

Gmail requires DMARC from bulk senders, meaning those that send close to 5,000 or more messages a day to personal Gmail accounts, and a policy of none is accepted. Every sender needs SPF or DKIM, and adding DMARC is a sensible step for any business domain.

Why is my new business email going to spam?

A new domain has no sending history yet, and new setups often miss SPF, DKIM or DMARC. Publish all three before you start, begin with everyday conversations rather than bulk campaigns, and increase your volume gradually.

Ready to Stop Worrying About Your Website?

Plans start at $49/mo. No setup headaches, no tech stress.

See Plans & Pricing →