Skip to content

NewExtra 20% Off on 3-Month Plans! πŸŽ‰ Order your VDS server for 3 months and get an extra 20% off in the cart!

Blog

Tutorials, guides, product news and engineering insights from the team that runs your hosting.

Guides

Why Do Business Emails Go to Spam? A Guide to SPF, DKIM and DMARC

11 October 2026 21 min read
Share this post

Reading time: about 15 minutes Β· Level: Beginner - Intermediate Β· Topic: Email security and deliverability

You sent a quote, and the other side said "your email never reached us". Then you found out it was sitting in the spam folder. With business email, this usually isn't a "bad content" problem; it comes from your domain being unable to prove that you really sent the email.

In this guide, we explain step by step why business emails land in the spam folder, what SPF, DKIM and DMARC records do, how to set them up and how to test whether they work correctly. The goal isn't for you to memorize DNS records, but to understand the logic and know where to start when a problem occurs.

Short answer

Business emails usually go to spam for one of three reasons: missing authentication (SPF, DKIM, DMARC), poor sender reputation, and content or list quality issues. The first layer, and the easiest to fix, is authentication.

Section 1

What Is Checked Before an Email Goes to Spam?

Before deciding whether an incoming message goes to the inbox, the spam folder or is rejected, the recipient's mail server runs an evaluation made up of several layers. The details vary from provider to provider, but the basic layers are similar:

  • Authentication: Was the email really sent by an authorized server for the domain? SPF, DKIM and DMARC answer this question.
  • Sender reputation: How have the sending domain and IP address behaved in the past? Have they received complaints before, are they on a blacklist, are they new?
  • Content and format: Do the message's headers, links, HTML structure and text resemble typical spam patterns?
  • Recipient behavior: Do recipients open and reply to this sender's messages, or mark them as spam?

Authentication is the most technical part of this list, but also the easiest to fix. Without authentication, your message may be considered suspicious even if everything else is fine.

Info: Requirements of the major providers

Since February 2024, Gmail and Yahoo require SPF, DKIM and DMARC for senders who send more than 5,000 messages a day. Microsoft has also announced similar requirements for high-volume senders to Outlook.com. Although these requirements aren't strictly mandatory for low-volume senders, messages without authentication are significantly more likely to go to spam.

Spam folder or rejection?

Distinguish between the two situations. An email can reach the recipient and land in the spam folder; in that case, the sender gets no error message. If the recipient server rejects the message entirely, a bounce message comes back to the sender. For example, Gmail may reject unauthenticated messages with something like 550-5.7.26 This mail is unauthenticated. The error code in the bounce message is the most valuable clue to the cause of the problem; always read it.

Section 2

Where to Look Based on the Symptom

How the problem looks determines where you should start. The list below gives quick guidance:

  • The email never arrives and a bounce message comes back: Read the error code. Most often it's authentication or IP reputation (Reasons 1, 2, 3 and 5).
  • It arrives but lands in spam, only with some providers: Check the authentication results in the message headers; if they're fine, look at reputation and content (Reasons 5, 6 and 7).
  • Emails sent from or by your website forms go to spam: Reason 4.
  • Newsletters or bulk sends go to spam: Reasons 5, 6 and 7.
  • Someone is sending fake emails using your domain: The DMARC section.
  • Forwarded emails go to spam: The DKIM section and the frequently asked questions.
Section 3

8 Common Reasons Emails Go to Spam

The first three reasons relate directly to SPF, DKIM and DMARC; you'll find the details in the following sections. The others can cause your email to go to spam even when your records are correct.

Reason 1

No SPF record, or an incorrect one

SPF declares in DNS which servers can send email on behalf of your domain. Without the record, the recipient server can't know whether the sending IP address is authorized. Having more than one SPF record for the same domain, or exceeding the 10 DNS lookup limit in the record, also breaks validation.

Solution: Create a single valid SPF record for your domain. Details are in the SPF section.

Reason 2

No DKIM signature, or an invalid one

DKIM is a digital signature that proves the message wasn't altered in transit. If no signature is added at all, or the public key in DNS can't verify the signature, the recipient server trusts the message less. Copying the key incorrectly (a missing character, an extra space) is the most common cause.

Solution: Enable DKIM signing in your mail system and add the provided public key to DNS in full. Details are in the DKIM section.

Reason 3

No DMARC, or alignment fails

DMARC links the SPF and DKIM results to the domain in your "From" address and tells the recipient what to do if authentication fails. Without a DMARC record, the recipient makes its own decision. With a record in place, DMARC still fails if the domains aren't aligned, even if SPF or DKIM passes.

Solution: First add a DMARC record in monitoring mode, review the reports and then tighten the policy. Details are in the DMARC section.

Reason 4

Third-party services aren't included in the records

You may not be sending email only from your mailbox. Your website's contact form, CRM, invoicing system, newsletter service or helpdesk software also send email with your domain. If these services aren't included in your SPF and DKIM records, their messages fail authentication.

A very common case with WordPress contact forms: the plugin sends email with the server's default mail() function and without authentication. The result is the spam folder instead of the inbox.

Solution: Make an inventory of all services that send on behalf of your domain. For each one, check the requirements for inclusion in SPF and for DKIM signing. Configure your website forms to send over SMTP with an authenticated mailbox.

Reason 5

Poor domain and IP reputation

Receiving providers assign senders a reputation score. Suddenly sending hundreds of messages from a newly registered domain, sending from an IP address that was previously blacklisted or using a domain that received spam complaints in the past lowers your reputation. Abuse by someone else on a shared IP address can also affect you.

Solution: Increase sending volume gradually on new domains. Check whether your IP address is on blacklists. Monitor your domain reputation with tools such as Google Postmaster Tools.

Reason 6

Content and format issues

Filters also look at the message itself. The following increase the risk:

  • Messages made up only of images, with no text.
  • Shortened links (such as bit.ly) or links that don't match their text.
  • Excessive capital letters, exclamation marks and spam patterns such as "free" or "you've won".
  • Broken or unnecessarily complex HTML, large attachments, suspicious attachment types.
  • A mismatch between the subject line and the content.
  • The sender (From) and reply address (Reply-To) using different domains.

Solution: Keep a balance of text and images, keep links on your own domain, use simple and clean HTML, and add a real signature and contact details.

Reason 7

List quality and low engagement

If you send in bulk or regularly, the quality of your recipient list directly affects your reputation. Lists without consent, addresses that haven't been updated for years (bounced emails), low open rates and high spam complaint rates tell providers that you're an unwanted sender. Not having a visible unsubscribe link in newsletters also increases the complaint rate.

Solution: Only send to people who've given consent, remove invalid addresses from the list, make unsubscribing easy and periodically clean out people who haven't engaged for a while.

Reason 8

Infrastructure details and compromised accounts

Even when the records look correct, small inconsistencies in the infrastructure cost points:

  • Reverse DNS (rDNS/PTR): If the sending IP address has no reverse DNS record, or it doesn't match the server's identity, filters may treat this negatively.
  • Encrypted connection (TLS): Unencrypted transmission between servers is a negative signal, especially for the major providers.
  • MX and domain configuration: Incorrect MX records or missing DNS records reduce the domain's trustworthiness.
  • Compromised mailbox: If an account is taken over because of a weak password, attackers start sending spam from your domain and your reputation drops very quickly.

Solution: Use strong passwords and, if possible, two-factor authentication on mail accounts, monitor unusual sending volume and make sure your rDNS and TLS configuration is correct.

Section 4

SPF, DKIM and DMARC at a Glance

The three records don't replace one another; each answers a different question and they complement each other:

SPF Sender Policy Framework

The question it answers: Is the server sending this email authorized to send on behalf of the domain?

Where it's stored: In the domain's root DNS record (TXT).

What it checks: The sending IP address and the envelope sender domain.

DKIM DomainKeys Identified Mail

The question it answers: Was this message really signed by this domain's system and not altered in transit?

Where it's stored: In the _domainkey TXT record under the selector name (the public key).

What it checks: The digital signature added to the message's headers and body.

DMARC Domain-based Message Authentication, Reporting and Conformance

The question it answers: If SPF or DKIM passed, is that result aligned with the visible "From" domain, and what should be done if it fails?

Where it's stored: In a TXT record named _dmarc.

What it checks: The alignment of the SPF and DKIM results; it sets the policy and the reporting address.

Section 5

What Is SPF and How Do You Set It Up?

SPF (Sender Policy Framework) is a TXT record that lists in DNS the servers authorized to send email on behalf of your domain. The recipient server looks at the IP address the message came from and checks whether that address is on your list.

Example SPF record

DNS record: SPF
Name (Host): @
Type: TXT
Value: v=spf1 mx include:spf.example-provider.com ~all

The spf.example-provider.com in this record is an example. You should take the real value from the information your email service provider gives you. The parts of the record are:

  • v=spf1 indicates that the record is an SPF record.
  • mx says that the servers listed in your domain's MX records can send.
  • include: includes another service's SPF record (for example your mail provider's or newsletter service's) in yours.
  • ip4: and ip6: allow specific IP addresses or ranges.
  • ~all sets a "soft fail" (softfail) policy for anything not on the list, and -all a "hard fail" (fail) policy.

Things to watch out for with SPF

  • The single-record rule: A domain can have only one SPF record. Adding a second v=spf1 record invalidates validation. When adding a new service, edit the existing record.
  • The 10-lookup limit: When SPF is evaluated, include, a, mx, ptr, exists and redirect can make at most 10 DNS lookups. Domains that add many services often exceed this limit. ip4, ip6 and all don't count as lookups.
  • Envelope sender: SPF doesn't look at the email's visible "From" address, but at the envelope sender (Return-Path / MAIL FROM) domain used in the background. This difference matters for DMARC alignment.
  • Forwarding: When an email is forwarded to another address, SPF may fail because the forwarding server isn't on your SPF list. DKIM usually solves this.
Section 6

What Is DKIM and How Do You Set It Up?

DKIM (DomainKeys Identified Mail) signs every outgoing message with a private key. The recipient server verifies the signature using the public key published in your domain's DNS record. If the signature is valid, the message was sent by your domain's authorized system and wasn't altered in transit.

Example DKIM record

DNS record: DKIM
Name (Host): selector1._domainkey
Type: TXT
Value: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA...

This value is only an example; the real key is generated by your mail system. The selector1 part of the record name is the "selector" name. Different selectors can be used for different services on the same domain.

  • The p= value is the public key itself. The private key stays only on your mail system and is never written to DNS.
  • A 2048-bit RSA key is recommended today. Some DNS panels may ask you to split long TXT values into 255-character chunks.
  • When copying the key, don't leave extra spaces, line breaks or missing characters. A broken key is the most common reason a signature can't be verified.
Security

Don't share the DKIM private key with anyone and don't send it by email. For security reasons, it's good practice to renew the key at intervals (rotation); creating a new selector and retiring the old one is enough for this.

Why is DKIM separate from SPF?

SPF checks the sending server's IP address; DKIM signs the message itself. That's why even if the message is forwarded to another address, the signature remains valid as long as the content doesn't change. The two are used to complement each other, not to replace each other.

Section 7

What Is DMARC and How Do You Set It Up?

DMARC (Domain-based Message Authentication, Reporting and Conformance) ties the SPF and DKIM results to a higher-level policy. It tells the recipient server two things: what to do if authentication fails, and how to report the results to you. DMARC is the primary tool for preventing the domain in the visible "From" address from being used fraudulently (spoofing).

The concept of alignment

For DMARC to pass, at least one of SPF or DKIM must both pass and be aligned with the domain in your "From" address. For example, if a newsletter service uses its own domain as the envelope sender when sending on your behalf, SPF may pass; but because that domain doesn't match yours, alignment fails. In that case, the message needs to be DKIM-signed with your domain.

Example DMARC record (monitoring mode)

DNS record: DMARC
Name (Host): _dmarc
Type: TXT
Value: v=DMARC1; p=none; rua=mailto:[email protected]; adkim=r; aspf=r
  • p= is the policy: none (monitor only), quarantine (treat as suspicious, usually send to the spam folder) or reject (reject).
  • rua= is the address where aggregate reports are sent. The reports show which sources send email on behalf of your domain and whether they pass authentication.
  • adkim and aspf set the alignment mode: r (relaxed, allows subdomains) or s (strict, exact match).
  • sp= defines a separate policy for subdomains, and pct= specifies the percentage of messages the policy applies to.
Caution

Don't start DMARC directly with p=reject. If there's a service that sends email on behalf of your domain and that you haven't yet included in SPF or DKIM, your legitimate emails will be rejected. First monitor with p=none, then tighten step by step.

DMARC reports arrive in XML format and are hard to read directly. There are many free and paid DMARC report analysis services that make these reports human-readable. If you want to send the reports to an address on a different domain from your own, an additional authorization record is needed on the receiving side.

Section 8

Moving to a DMARC Policy Gradually

The goal is to tighten the policy without losing any legitimate email. The recommended order is as follows:

Stage 1

Monitoring (2-4 weeks)

Set the policy to p=none and collect the reports. During this time, identify all sources that send email on behalf of your domain: your mail server, website, CRM, invoicing system, newsletter service and helpdesk software. Make sure each one is included in SPF and DKIM.

Stage 2

Quarantine (gradual)

When the reports show that all legitimate sources pass authentication, set the policy to quarantine and start with a low pct value. Increase the percentage over a few weeks:

DNS record: DMARC (quarantine, 25%)
Name (Host): _dmarc
Type: TXT
Value: v=DMARC1; p=quarantine; pct=25; rua=mailto:[email protected]
Stage 3

Reject

As long as you see no problems during the quarantine stage, set the policy to p=reject. This is the strongest protection against your domain being used in fake emails.

DNS record: DMARC (reject)
Name (Host): _dmarc
Type: TXT
Value: v=DMARC1; p=reject; rua=mailto:[email protected]
Info

When you add a new service (for example a new newsletter tool), update your SPF and DKIM records first, then start using the service. Reviewing DMARC reports regularly also reveals unauthorized sources.

Section 9

How to Test Your Records

Adding the records isn't enough; you should check that they're published correctly and that real messages pass authentication.

1. Look up the DNS records

Replace example.com and selector1 with your own domain and DKIM selector:

Terminal (Linux / macOS)
dig TXT example.com +short
dig TXT selector1._domainkey.example.com +short
dig TXT _dmarc.example.com +short
dig MX example.com +short

On Windows, you can use the commands nslookup -type=TXT example.com and nslookup -type=TXT _dmarc.example.com for the same lookups. In the output of the first command, you should see only one v=spf1 record.

2. Check the reverse DNS record

Check whether a reverse DNS record is set for the sending server's IP address. 203.0.113.10 is an example IP address:

Terminal
dig -x 203.0.113.10 +short

3. Read the headers of a real message

Send a test email from your domain to a Gmail or Outlook account. In Gmail, open the message and choose "Show original"; in Outlook, open the message properties to view the headers. The Authentication-Results line summarizes the result:

Example message header (successful authentication)
Authentication-Results: mx.google.com;
       dkim=pass [email protected] header.s=selector1;
       spf=pass [email protected];
       dmarc=pass (p=NONE) header.from=example.com

The goal is for all three results to be pass. Wherever you see fail, softfail, neutral or none, that's the record you need to fix.

4. Use online testing and monitoring tools

  • Email testing services that score you after you send a test email to a unique address show authentication and content problems in a single report.
  • Blacklist checking services show whether your sending IP address is listed.
  • Google Postmaster Tools lets you monitor your domain reputation, spam rate and authentication status for messages sent to Gmail (it shows data above a certain sending volume).
Info: When does a DNS change take effect?

DNS changes usually propagate within minutes, sometimes longer. The time depends on the record's TTL value and the previous record. If you don't see the test result, wait a few hours and try again.

Section 10

Common Mistakes

  • Adding two separate SPF records: Creating a separate TXT record for each new service invalidates the existing record. Combine all permissions in a single record.
  • Exceeding the 10-lookup limit in SPF: Clean up unnecessary include entries; remove unused services from the record.
  • Copying the DKIM key incorrectly: An extra quote, space or missing character makes the key invalid.
  • Starting DMARC directly with p=reject: This can cause legitimate emails to be rejected.
  • Never reading the reports: If you set an rua address but don't review the reports, you miss DMARC's most valuable information.
  • Adding the records in the wrong place: Make sure you add them where the DNS for the domain you use for email is managed (your registrar or DNS provider). If the nameservers point elsewhere, the record must be there.
  • Forgetting third-party senders: Website forms, CRMs and newsletter services are often overlooked.
  • Not thinking about subdomains: Sending marketing emails from a separate subdomain rather than the main domain helps protect the main domain's reputation.
  • Assuming the records are correct and ignoring reputation and content: Passing all three authentication checks doesn't guarantee you won't go to spam; reputation and content are decisive too.
Section 11

15-Minute Setup Checklist

The list below is a summary of this guide. Work through it by ticking each item in order:

  • βœ“ I listed all services that send email on behalf of my domain (mailbox, web form, CRM, newsletter).
  • βœ“ I created a single SPF record for my domain and checked that I don't exceed the 10-lookup limit.
  • βœ“ I enabled DKIM signing in my mail system and added the public key to DNS in full.
  • βœ“ I added the DMARC record with p=none and a report address.
  • βœ“ I looked up the records with dig or nslookup.
  • βœ“ I sent test emails to Gmail and Outlook and confirmed in the headers that all three results are pass.
  • βœ“ I made sure my website forms send over SMTP with an authenticated mailbox.
  • βœ“ I checked that my sending IP address isn't blacklisted and that a reverse DNS record is set.
  • βœ“ I created a calendar reminder to monitor DMARC reports.
Section 12

Choosing a Business Email Service

In terms of authentication and deliverability, what your email service supports matters. When evaluating a provider, check the following:

  • Does it offer email addresses on your own domain?
  • Are the record values required for SPF, DKIM and DMARC provided and supported?
  • Is there antispam and antivirus protection for incoming email?
  • Are IMAP, POP3 and SMTP supported, with Outlook and mobile device compatibility?
  • Are there everyday tools such as a web interface, calendar and contact management?
  • Can you get technical support when a problem occurs?
What Netiyo Business Email offers
  • βœ“ 25 GB of total mail storage
  • βœ“ Email on your own domain
  • βœ“ SmarterMail webmail panel
  • βœ“ IMAP / POP3 / SMTP support
  • βœ“ Outlook and mobile device compatibility
  • βœ“ Calendar and contact management
  • βœ“ Antispam protection
  • βœ“ Antivirus protection
  • βœ“ SPF / DKIM / DMARC support
  • βœ“ Expert technical support

Antispam and antivirus protection protect your inbox. Whether your outgoing emails avoid the recipient's spam folder depends on the DNS records described in this article, your sender reputation and your content. To find out the record values you'll use for SPF, DKIM and DMARC and to get help with setup, you can find service details on the Netiyo Business Email page and contact our technical support team.

Section 13

Frequently Asked Questions

Which of SPF, DKIM and DMARC is enough to set up?

None of them is enough on its own; the three work together. SPF verifies the authorized server and DKIM the integrity of the message; DMARC links these results to your "From" address and instructs the recipient on what to do about spoofing. For the best results, set up all three.

My records are correct, but my emails still go to spam. Why?

Authentication is necessary but not sufficient. Domain and IP reputation, content, list quality, recipient engagement and infrastructure details also determine the result. After confirming in the headers that all three checks pass, review these factors one by one.

Can I set DMARC to p=reject right away?

We don't recommend it. First monitor the reports with p=none, make sure all legitimate senders pass authentication, then move to quarantine and finally to reject.

Is it normal for email to reach Gmail without problems but go to spam in Outlook?

Yes. Each provider uses its own filter rules and reputation system. Having a problem with one provider doesn't mean your authentication records are wrong; you may be hitting reputation, content or a rule specific to that provider.

Should I use a separate subdomain for bulk email?

Sending marketing and newsletters from a separate subdomain such as newsletter.example.com is a common best practice. That way, a reputation problem that may occur with bulk sending doesn't directly affect the main domain used for your everyday business correspondence. The subdomain also needs its own SPF, DKIM and DMARC configuration.

Why does email forwarding break SPF?

The forwarding server relays the message from its own IP address, not on your behalf. Because that IP address isn't in your SPF record, SPF fails. Since the DKIM signature can remain valid when the message is forwarded unchanged, it can allow DMARC to pass. That's why enabling DKIM is important.

I've added the DNS records but don't see a result. How long should I wait?

DNS propagation depends on the record's TTL value and usually completes within minutes to a few hours. If you still can't see the record in lookups after a few hours, check that it was added to the right domain and the right DNS provider.

Section 14

Conclusion

Behind business emails landing in the spam folder there are usually a few recurring causes: missing or incorrect SPF, DKIM and DMARC records, third-party services not included in the records, poor domain and IP reputation, content and list problems, and infrastructure details. Chief among them, authentication is the easiest layer to fix and the one whose effect is seen fastest.

Follow an ordered path: first list all sources that send email on behalf of your domain, set up SPF and DKIM, turn on DMARC in monitoring mode, review the reports and tighten the policy gradually. After each change, verify the result by reading the headers of a real message. Once authentication is in place, also pay attention to list quality, content and account security to protect your reputation.

Business Email on Your Own Domain

Explore Netiyo Business Email, which offers email addresses on your own domain, antispam and antivirus protection, SPF, DKIM and DMARC support, and expert technical support.

Explore Business Email
Never Miss a Post

Get our latest tutorials, guides and product news in your inbox.

You're subscribed to our newsletter.