Service status

Insights

Email that lands in the inbox: SPF, DKIM, DMARC

Why good email ends up in spam, and the practical steps that fix it: one SPF record, DKIM on every sender and a DMARC policy you tighten step by step.

  • The GOLDNET team
  • Published
  • 4 min read
  • Hosting

Few things are as frustrating as an invoice or a quote that quietly lands in your customer's spam folder. You did nothing wrong, and the email was real. So why did it end up there?

Usually because the receiving mail server couldn't prove the message really came from you. Email was designed in a more trusting time: anyone can type any "From" address. Big mail providers now protect their users by checking three things on every message, SPF, DKIM and DMARC, and they treat mail that fails as suspect.

The good news is that these checks are completely in your control. Here's how they work in practice, and the mistakes we see most often.

The rules got stricter

In February 2024, Google and Yahoo started requiring bulk senders (thousands of messages a day to their users) to have SPF, DKIM and DMARC in place, keep spam complaints low and offer one-click unsubscribe. Microsoft announced similar rules for Outlook.com in 2025. Even if you only send a handful of emails a day, the same checks decide how your mail is treated. A domain without them looks more and more like a domain that can't be trusted.

SPF: the guest list

SPF is a DNS record that lists which servers may send email using your domain. When a message arrives, the receiving server checks whether it came from a server on your list.

What goes wrong in practice:

  • Forgotten senders. Your mailboxes are covered, but your accounting system, your website's contact form, your online shop and your newsletter tool all send email "from" your domain too. Each one needs to be on the list, usually with an include: the service gives you.
  • Two SPF records. Someone adds a new service by creating a second SPF record. That breaks both. There must be exactly one, with everything in it.
  • Too many look-ups. SPF allows at most 10 DNS look-ups. Every include: uses at least one, and some use several. Go over and SPF fails for everyone.

DKIM: the signature

DKIM adds a digital signature to every message. Your mail server signs with a private key; you publish the matching public key in DNS; the receiver checks the signature. If the message was changed on the way, or didn't come from a server holding your key, the check fails.

In practice:

  • Every service that sends for you should sign with its own key: your mailbox provider, your newsletter tool, your invoicing system. Most give you a DNS record to add; it's worth the five minutes.
  • Copy keys exactly. DKIM keys are long. A missing character, or a key split badly across lines, breaks the signature.

DMARC: the policy and the feedback

DMARC ties it all together. It tells receivers what to do with mail that claims to be from your domain but fails the checks, and asks them to send you reports.

DMARC also checks alignment: the domain that passed SPF or DKIM must match the domain in the "From" address your reader sees. That's what stops someone passing SPF with their own domain while showing yours.

The policy has three settings, and the safe way is to go through them in order:

  1. p=none for a few weeks. Nothing changes for delivery, but you get reports showing every server sending mail as your domain. You'll often find a forgotten sender or two.
  2. p=quarantine once your real mail passes. Fakes go to spam.
  3. p=reject when you're confident. Fakes are refused outright. This is the strongest protection against someone sending invoices "from" you with their own bank details.

Jumping straight to reject without reading the reports is how businesses lose their own invoices.

Beyond the three records

The records are the foundation. A few habits matter just as much:

  • Send through a proper mail server, not straight from a web server. A website that sends with PHP's built-in mail function, from a server with no SPF or DKIM, is a spam folder waiting to happen. Use authenticated SMTP (port 587) with a real mailbox instead.
  • Keep lists clean. Sending to old or bought addresses causes bounces and complaints, and receivers notice.
  • Make unsubscribing easy for newsletters and marketing.
  • Running your own mail server? You'll also need a reverse DNS (PTR) record for its address that matches its name. On GOLDNET Cloud, outgoing email on port 25 is closed on new servers to protect our addresses from spammers, so talk to support before you plan this. For most businesses, hosted email is far less work.

What we set up for you

On GOLDNET web hosting and email hosting, we set up SPF, DKIM and DMARC for your domain as part of the service. If your domain uses our nameservers, the records are in place from the start. If your DNS is hosted somewhere else, we give you the exact records to add there, so you can copy them across.

If you add other services that send mail as you, add them to your SPF record and set up their DKIM keys, or ask us and we'll check your records with you.

A five-minute check

  1. Send an email from your domain to a Gmail address.
  2. Open it, choose "Show original" from the menu, and look for SPF: PASS, DKIM: PASS and DMARC: PASS.
  3. If any of them fails, compare your records with our guide Email DNS records explained.

Getting this right takes an afternoon at most, and it protects both your inbox placement and your customers. Read more about email hosting, or contact support and we'll look at your domain's records with you.

All insights

Talk to a person, not a call centre

Our teams in Gqeberha and Durban answer Monday to Friday, 09:00 to 18:00. Our WhatsApp assistant answers any time, and the network is monitored around the clock.