DNS & Auth 7 min read

Authentication Passed but Inbox Placement Is Still Low

SPF, DKIM, DMARC all pass. Inbox placement tests show 50–70% inbox rate. Authentication is not the problem. Here's what is.

SPF passes. DKIM passes. DMARC passes with alignment. You've done everything right from an authentication standpoint. But inbox placement tests show 50–70% inbox rate. Messages are going to spam or junk on a significant percentage of test accounts. The problem is clearly not authentication, so what is it?

Why This Happens

Authentication is the foundation, not the building. It proves you are who you say you are. It does not prove you are a good sender. Once authentication is solid, deliverability depends entirely on reputation, behavior, content, and engagement.

The factors that drive inbox placement beyond authentication:

  • Domain reputation: Built over time from engagement, complaints, and sending patterns. A new domain with clean authentication has no reputation. A damaged domain with clean authentication has bad reputation. Neither gets good placement automatically.
  • IP reputation: Especially important for Outlook. Shared IPs with bad reputations hurt everyone on them regardless of individual authentication.
  • Complaint rate: The single most damaging metric. Every spam complaint directly tells the mail provider that your email is unwanted. Google's threshold is 0.3%, with a target below 0.10%.
  • Engagement metrics: Opens, replies, and other positive interactions signal to Gmail that your messages are valued. Low engagement over time trains the filter to deprioritize you.
  • Sending patterns: Sudden volume spikes, inconsistent sending schedules, and high-volume sends to cold lists all raise red flags.

Step-by-Step Diagnosis

Check Postmaster Tools. Domain reputation is the single most informative data point when authentication is clean.

Run the blacklist checker on your domain and sending IP. Check PTR records with the rDNS checker — Google requires valid forward and reverse DNS.

Send a bare-bones plain text email with zero links, zero tracking, zero HTML. If it lands in inbox, the issue is content-related. If it still goes to spam, the issue is reputation-related.

Review your sending volume and patterns over the last 30 days. Use the sending limit planner to verify you're within safe thresholds. Review list quality — what's your bounce rate? Check your links with the link checker.

Run the burn score calculator to get an overall health assessment across all these signals.

The Fix Path

If domain reputation is the issue, enter recovery mode. Reduce volume dramatically. Send only to your most engaged contacts. Generate positive engagement signals. Hold this pattern for 2–4 weeks while monitoring Postmaster Tools for reputation improvement.

If complaints are the issue, add one-click unsubscribe headers, suppress unengaged recipients, and refine targeting to reduce complaints.

If content is the issue, simplify to plain text with minimal links. Test iteratively with the placement test, adding back one element at a time to identify the trigger.

If IP reputation is the issue, explore dedicated IPs or different sending infrastructure.

When to Replace Instead of Repair

The answer depends on the severity and duration of the reputation damage. If Postmaster Tools shows domain reputation declining but still Medium, 2–3 weeks of disciplined behavior can recover it.

If domain reputation is Bad and has been for more than 2 weeks, recovery is slower and less certain. In that scenario, routing campaigns through prewarmed inboxes from WarmInboxes while the damaged domain recovers lets you maintain campaign performance without waiting for a recovery that might take a month or more.

Mistakes That Make This Worse

  • Continuing to troubleshoot authentication when it already passes
  • Increasing volume to "test" whether placement improves
  • Not monitoring Postmaster Tools
  • Blaming the outreach tool when the issue is your domain's reputation or your list quality

Run the checks first

Before replacing anything, run a free inbox placement test. You might find the issue is DNS, not the domain — and save yourself a week of unnecessary work.

Free inbox placement test Check burn score

More guides

SPF, DKIM, and DMARC for Cold Email: The Simple Fix GuideHow to Check if a DNS Error Is Killing Your DeliverabilityCold Email Setup Checklist: Domain, DNS, Tracking, and Sending Health