Authentication Passed but Inbox Placement Is Still Low
Clean authentication is the floor, not the ceiling. Here's the full framework for what to fix when auth is perfect but placement is still poor.
SPF passes. DKIM passes. DMARC passes with alignment. You have 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?
What drives inbox placement beyond authentication
Authentication is the foundation, not the building. Once authentication is solid, deliverability depends entirely on reputation, behavior, content, and engagement.
- 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.
- Content quality: Spam-like content patterns, suspicious links, certain HTML structures trigger content-based filters.
- Sending patterns: Sudden volume spikes, inconsistent sending schedules, and high-volume sends to cold lists all raise red flags.
Step-by-step diagnosis
Step 1: Check Postmaster Tools
Domain reputation is the single most informative data point when authentication is clean. Check Google Postmaster Tools for current domain reputation and spam rate.
Step 2: Check blacklists
Run the blacklist checker on your domain and sending IPs. A blocklist hit can override clean authentication.
Step 3: Send a bare-bones plain text email
Zero links, zero tracking, zero HTML. Use the placement test with the simplest possible content. If it lands in inbox, the issue is content-related. If it still goes to spam, the issue is reputation-related.
Step 4: Review sending volume and patterns
Look for spikes, inconsistencies, or periods of very high volume over the last 30 days. Use the sending limit planner to verify you're within safe limits.
Step 5: Review list quality
What is your bounce rate? If above 2%, list quality is a factor. Run the burn score calculator on affected domains to get an overall health picture.
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.
If content is the issue, simplify to plain text with minimal links. Test iteratively using the subject spam tester and link checker.
Repair or replace?
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, 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.
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.