Skip to content
RedWebDesign
Hosting and domain

Why does your business email end up in spam? SPF, DKIM and DMARC explained

You send a quote and the client finds it in the spam folder days later. Or the messages from your website’s form simply never arrive. In most cases the problem is not the content of the email but three short DNS records that are not set up properly for your domain. In this article I explain what these three are and how to check them.

Ferenc KulcsárUpdated: 31 October 2026Reading time: about 4 min

Mail app icon with a badge showing six unread messages

Why has this become important now?

The big email providers are checking more and more strictly whether an email really comes from who it claims to be from. Since 2024, Gmail and Yahoo require every sender to have at least SPF or DKIM in order, and bulk senders to have all three, including DMARC. Since 2025, Microsoft (Outlook, Hotmail) has applied similar rules to high-volume senders.

Illustration: a laptop with a red envelope icon and warning signs
Image: Freepik

A small business rarely sends thousands of emails a day, but email providers score smaller senders’ messages on the same basis. Where these records are missing, the email is more likely to land in spam.

The three records, simply

SPF: who may send in your name?

A list in the DNS of which servers may send email on behalf of your domain (for example your hosting’s mail server, Google Workspace or a newsletter service). A domain may have only one SPF record; if there are two, both are invalid.

DKIM: a digital signature on the email

The sending server signs every email, and the DNS holds the key with which the recipient can check that the email was not altered on the way and really came from your system. It has to be enabled separately with every email provider.

DMARC: what to do with a forged email?

It tells the receiving system what to do if an email arrives in your name but fails the SPF or DKIM check: let it through (p=none), put it in spam (p=quarantine) or reject it (p=reject). You can also request reports (rua=), which show who is sending in your name.

The most common mistake: the website form

Many website forms send the message as if the visitor had sent it, with the visitor’s email address as the sender. That is an email sent in the name of the visitor’s domain, which their SPF and DMARC settings do not allow, so more and more often the email never reaches you.

The right solution: the form should send from an address on your own domain (for example noreply@your-domain.com), with the visitor’s address in the reply address (Reply-To). The reply button still writes to the visitor, but the email passes the checks.

How to check

  1. Run the free website quick check: its email section shows whether you have SPF and DMARC records and whether they are set up correctly.
  2. Send an email to a Gmail address, open it, and choose “Show original” in the “More” menu. There you can see SPF, DKIM and DMARC: “PASS” or “FAIL”.
  3. If one is missing, it has to be added in your domain’s DNS management. Your email provider gives you the exact values.

In practice: a half-configured DMARC

In practice · a real case, anonymised

A strict rule, subdomains left open

Record
v=DMARC1; p=quarantine; sp=none
Problem
Anyone could send in the name of the subdomains
Recommendation
sp=quarantine and reporting

For a domain I reviewed recently, the main DMARC rule was fine: it sent forged emails to spam. The “sp=none” part, however, meant that no rule applied to subdomains (for example anything.the-domain.hu), so forged emails could still be sent in their name.

If no email is sent from a subdomain, the sp value should also be quarantine (or be left out, in which case the main rule applies to subdomains too), and it is worth enabling reports (rua) to find out if someone tries to send in the domain’s name.

If everything is fine and it still goes to spam

  • Blacklist: if the IP address of your mail server or hosting has been blacklisted (for example because of a hacked site), emails do not get through. Your hosting provider can sort this out.
  • The content: emails that are all images, a shortened link, too many exclamation marks and the word “FREE” look suspicious to filters.
  • New domain: a fresh domain has no reputation yet. Start with smaller volumes in the first weeks.
Illustration: a laptop with envelopes and a prohibition sign next to the word “Spam”
Image: Freepik
Shall I sort out your email settings? I check the SPF, DKIM and DMARC records and how your website form sends email, and set them up so that your emails arrive.

Frequently asked questions

What are SPF, DKIM and DMARC in one sentence?

SPF says who may send in your name, DKIM signs your emails, and DMARC tells the recipient what to do with forged emails. All three are short records in your domain’s DNS settings.

Can I have two SPF records?

No. A domain may have only one SPF record; if there are two, receiving systems treat both as invalid. If you send through several providers, they have to be merged into a single record.

Why do I not receive the emails from my website form?

The most common reason is that the form sends the email with the visitor’s address. The DMARC rule of the visitor’s domain forbids that. The form should send from an address on your own domain, with the visitor’s address as the reply address.

Is p=none enough for my DMARC?

To start with, yes, because the reports show what is sending in your name. Protection, however, only comes from p=quarantine or p=reject. Once all your own emails pass the check, it is worth tightening.

Share Facebook LinkedIn
Ferenc Kulcsár
Ferenc Kulcsár I have been building, fixing and running websites for businesses since 2006. About me