top of page

SPF, DKIM and DMARC: Stop Business Emails Going to Spam

2 days ago
7 min read

If your business emails keep landing in spam, the cause is usually not your words. It is that your domain cannot prove the mail really came from you. SPF, DKIM and DMARC are three small records you add to your domain that do exactly that proving. Set them up and Gmail is far more likely to deliver your mail to the inbox. Skip them and, since February 2024, Gmail can mark your mail as spam or reject it outright.

This post explains what each record does in plain words, how to check what you already have, how to add them, and which rules actually apply to a small business sending a few hundred emails rather than a bulk sender. Where a record format appears, it is copied from Google's own help pages, not from memory.

Key takeaways

What they are: SPF, DKIM and DMARC are three DNS records that prove your email is really from your domain.

Why it matters: without them, mail providers are more likely to send your business email to spam or reject it.

Gmail's 2024 rule: all senders need at least SPF or DKIM, and bulk senders need SPF, DKIM and DMARC together.

Start safe: add SPF and DKIM, then set DMARC to p=none first and watch the reports before tightening it.

Why do business emails go to spam?

Because the receiving server cannot confirm the mail is genuinely from your domain. Spammers forge "from" addresses all the time, so mail providers now trust a domain only if it proves itself with authentication.

Google made this concrete. Its sender guidelines state that starting 1 February 2024, all senders who send email to Gmail accounts must set up SPF or DKIM. Mail that is not authenticated "might be marked as spam or rejected." So a missing record is no longer just untidy, it is a direct cause of your mail not arriving.

What SPF, DKIM and DMARC each do

Three records, three jobs.

SPF says which servers are allowed to send mail for your domain. Google describes it as preventing "spammers from sending unauthorized messages that appear to be from your domain." It is a list of your legitimate senders.

DKIM adds a signature to each message that proves it was not tampered with and really came from your domain. Google: receiving servers "use DKIM to verify that the domain owner actually sent the message."

DMARC tells receiving servers what to do with mail that fails SPF or DKIM, deliver it, send it to spam, or reject it. It also sends you reports on who is sending mail as your domain.

Together: SPF lists your senders, DKIM signs your mail, DMARC sets the policy and watches for abuse.

How to check your domain today

Before you add anything, see what you already have. Many domains come with some of this set up by default.

Google's own advice is to "use one of many free tools available on the internet" to check whether SPF, DKIM and DMARC already exist on your domain. Search for a free domain or email authentication checker, enter your domain, and it shows which of the three records are present.

Do this first. You may find SPF is already there and you only need DKIM and DMARC, or that a record exists but is set up wrong. Fixing the gap is faster than rebuilding all three.

How to add the records at your domain host

All three are added as DNS TXT records at your domain host, the company where you bought your domain, not inside your email tool. The exact screen differs by host, so follow your host's own help, but the shape is the same.

SPF. A single TXT record listing your senders. Google's example for a domain that sends only through Google Workspace is:

v=spf1 include:_spf.google.com ~all

Each sender gets an include: tag, and Google notes a record can hold up to 10 of them. The ~all at the end tells servers to treat mail from unlisted servers as suspicious, and Google recommends using it. If you send through more than one service (your website, a newsletter tool, your mailbox), each one needs its include tag in this single record.

DKIM. You generate a key pair. The public key goes into a TXT record at your host; the private key stays on your mail server and signs your outgoing mail. Google's DKIM record uses a host name like google._domainkey and a value in the form v=DKIM1; k=rsa; p=yourkey. One important detail from Google: sending to personal Gmail accounts requires a DKIM key of 1024 bits or longer, and 2048 bits is recommended.

DMARC. One TXT record that sets your policy. Google's example:

v=DMARC1; p=none; rua=mailto:you@yourdomain.com

The p tag is the policy: none (just monitor and report), quarantine (send failing mail to spam) or reject (block it). Google's advice is to start with p=none while you watch the reports, then tighten to quarantine or reject once you are sure your real mail passes. The rua tag is where DMARC reports are sent. Google also says to set up SPF and/or DKIM first and wait 48 hours before adding DMARC.

A note on timing: Google says it can take up to 48 hours for each record to start working. Add them, then give them a day before you judge the result.

Gmail's sender rules: what changed in 2024

Here is the part that decides which rules apply to you, because they split by how much mail you send.

All senders (any volume) to Gmail must, since 1 February 2024, set up SPF or DKIM, keep valid reverse DNS, and not impersonate Gmail addresses. Google recommends setting up all three regardless.

Bulk senders, which Google defines as more than 5,000 messages per day to Gmail accounts, must set up SPF, DKIM and DMARC together, support one-click unsubscribe on marketing mail, and keep their spam rate in Postmaster Tools below 0.30 percent.

For most small businesses sending a few hundred emails, you fall under "all senders", so SPF or DKIM is the hard requirement. But set up all three anyway. Google recommends it, DMARC protects your domain from being forged, and you are then ready if your volume grows.

Mistakes that break email

The common ones, so you can avoid or spot them:

Two SPF records. A domain must have only one SPF record. A second one breaks SPF. If you add a new sender, edit the existing record, do not create another.

The sender does not match. To pass DMARC, Google says the domain in your "from" address must align with your SPF or DKIM domain. Sending as your domain through a tool that signs with its own domain can fail this.

Missing DKIM on a sending tool. Every service that sends as your domain needs to be authenticated. A newsletter tool or CRM that is not set up will fail even when your main mail passes.

Jumping straight to p=reject. Set DMARC to reject before you have checked the reports and you can block your own legitimate mail. Start at none.

Sending from several tools as one domain

Most businesses send mail from more than one place: the website contact form, a newsletter tool, a CRM, and the owner's own mailbox. They all send "as" your domain, and every one of them has to be authenticated or it risks the spam folder.

A simple worksheet: list every tool that sends email as your domain. For each, note whether it is in your SPF record and whether DKIM is set up for it. Any tool not covered is a candidate for the spam folder. Google's SPF guidance says plainly to include all your senders, and if a new tool starts sending, update the record.

What to do if you only use a Gmail address

If you send only from a plain @gmail.com address and have no domain of your own, you do not set up SPF, DKIM or DMARC. Google already authenticates gmail.com. These records are for mail sent from your own domain (you@yourbusiness.com).

The honest upgrade path: if you want business mail that lands well and looks professional, send from your own domain with authentication set up, rather than a gmail.com address. That is when this whole checklist starts to matter.

FAQ

What are SPF, DKIM and DMARC in simple terms?

Three records on your domain that prove your email is really from you. SPF lists your allowed senders, DKIM signs each message, and DMARC tells servers what to do with mail that fails and reports abuse.

Do I really need all three for a small business?

Google requires all senders to Gmail to have SPF or DKIM since February 2024. Bulk senders (over 5,000 a day) must have all three. Google recommends all three for everyone, so set them up even if you send little.

Where do I add SPF, DKIM and DMARC?

As DNS TXT records at your domain host, where you bought your domain, not inside your email tool. Follow your host's help for the exact screen.

Why are my emails still going to spam after adding the records?

Check for two SPF records, a sender domain that does not align, a sending tool with no DKIM, or records that have not finished propagating. Google says each record can take up to 48 hours to work.

What DMARC policy should I start with?

Start with p=none so you only monitor and get reports. Once you confirm your real mail passes SPF or DKIM, tighten to quarantine or reject.

I only use a gmail.com address. Do I need this?

No. These records apply to mail sent from your own domain. Gmail already authenticates gmail.com addresses. Set them up when you move to sending from your own business domain.

Once your mail reaches the inbox, make it worth opening with email subject lines that get opened. Tag your links with UTM parameters and read the WhatsApp broadcast limit guide for your other channel.

Book a consultation

If your business emails keep landing in spam and you are not sure which record is missing, I can check your domain and set up SPF, DKIM and DMARC so your mail reaches the inbox. You can book a consultation at pratiksinghrajput.com/book-online.

Sources

Comments

Rated 0 out of 5 stars.
No ratings yet

Add a rating
bottom of page