Business Email Going to Spam? Audit SPF, DKIM and DMARC

Website layout sketches and a tablet arranged on a desk with teal and orange design swatches
Language: English | Español

If business email is going to spam, first inspect a failed message and identify which system sent it. Then verify that the sending domain passes aligned SPF or DKIM authentication under DMARC. Do not begin by copying a generic DNS record: your correct configuration depends on every platform that sends as your domain.

Email authentication can improve trust and reduce spoofing, but it does not guarantee inbox placement. Recipient complaints, sending reputation, list quality, message content and sudden volume changes also affect filtering.

Run this diagnostic before changing DNS

  1. Send separate tests from employee email, the website contact form, invoicing software, CRM and marketing platform.
  2. Open the received message’s full headers or “show original” view.
  3. Record the results for spf=, dkim= and dmarc=.
  4. Compare the visible From domain with the SPF MAIL FROM domain and DKIM signing domain.
  5. Check rejection notices for an SMTP code and the receiving provider’s explanation.

A message can show SPF “pass” yet fail DMARC when the authenticated MAIL FROM domain does not align with the address customers see. The same issue occurs when DKIM passes using a vendor’s domain rather than yours. Microsoft provides a useful explanation of DMARC alignment and troubleshooting.

Implementation sequence

1. Inventory every legitimate sender

List Google Workspace or Microsoft 365, website forms, newsletters, appointment tools, help desks, payment systems and any application that sends notifications. Include rarely used systems such as recruiting or event platforms. An old integration can break when DMARC enforcement begins.

2. Correct SPF without creating duplicates

SPF authorizes systems to send for the envelope domain. A domain should publish one SPF TXT record, with all approved sources combined according to provider instructions. Two records beginning with v=spf1 can cause a permanent error. Also review nested includes so the record does not exceed SPF’s DNS-lookup limit.

Use the exact value supplied by your email provider. See Google’s SPF setup instructions or Microsoft’s Microsoft 365 SPF guidance.

3. Enable DKIM for each sending platform

DKIM adds a cryptographic signature that recipients verify through DNS. Generate or retrieve the selector and DNS value inside each provider, publish it, and then enable signing. Do not reuse an example key from documentation. Google Workspace and Microsoft 365 each generate domain-specific records; follow their official Google DKIM or Microsoft DKIM procedures.

4. Introduce DMARC gradually

DMARC checks whether SPF or DKIM passes and aligns with the visible From domain. Start with a monitoring policy such as p=none and send aggregate reports to a mailbox or reporting service that your team actually reviews. Identify legitimate sources, correct alignment and only then consider staged quarantine or rejection. Google’s recommended DMARC rollout warns against enforcing a strict policy before SPF and DKIM are working.

Common mistakes

  • Adding a second SPF record instead of updating the existing one.
  • Forgetting WordPress forms, CRMs, scanners or billing applications.
  • Publishing DKIM records but not enabling signing in the provider.
  • Moving directly to p=reject without reviewing reports.
  • Testing only DNS instead of checking a message sent through each system.
  • Assuming authentication fixes purchased lists, high complaint rates or poor sending practices.

What to verify after changes

Allow for DNS propagation, then repeat the original tests. Confirm that SPF and DKIM results identify expected domains, DMARC passes through at least one aligned method, website-form messages arrive, and no business application was omitted. Monitor bounce logs and DMARC aggregate reports for unfamiliar sources or rising failures.

Google’s current email sender guidelines apply authentication requirements to mail sent to personal Gmail accounts, with additional requirements for bulk senders. Requirements from receiving providers can change, so review official documentation rather than relying on an old DNS screenshot.

Need help auditing business email?

CyberTek Group can review your sending inventory, DNS records, message headers and implementation responsibilities as part of an IT and cybersecurity project. Authentication improves an important part of deliverability, but no provider can guarantee placement in every inbox.

For more practical guidance on websites, security and business technology, visit the CyberTek Group resource center.

Related ArticlesArtículos relacionados