If your cold emails are landing in spam despite passing all authentication checks, you are not alone. Many senders assume that setting up SPF, DKIM, and DMARC guarantees inbox placement. But according to a recent analysis by Nithyanandan Ramakrishna, 60% of deliverability problems sit in the infrastructure, not in authentication. As he puts it, "The truth is out there. It was never in your authentication."

the original LinkedIn post

Why Authentication Alone Is Not Enough

SPF, DKIM, DMARC, and even BIMI serve one purpose: they prove that an email came from a domain you control. They verify identity. But they tell you nothing about the IP address sending that email. They do not reveal:

  • The IP's history
  • How it was used before
  • What types of emails it sent
  • How many spam complaints it still carries
  • When it last sent mail

Every free tool can confirm that your authentication records pass. But none of them open the file on the IP's past. This is a critical blind spot for cold outreach.

The Hidden Role of IP Reputation

Email providers like Gmail, Outlook, and Yahoo evaluate the reputation of the sending IP address as a major factor in deliverability. An IP that has been used for spam in the past, even by a previous owner, carries that baggage. Spam complaints accumulate and linger. Even if you authenticate perfectly, a tainted IP will hurt your inbox placement.

Ramakrishna's company, DNSPulse, has evaluated over 7,500 domains. Their data shows which email service providers remain tolerant of spam and which do not. They know which IPs stayed clean and which keep transmitting complaints. The clues were always in the infrastructure.

What to Look For in Your Infrastructure

To diagnose infrastructure issues, you need to go beyond authentication checks. Here are the key factors to examine:

  1. IP Age and History: How old is the IP? Has it been used for email before? If so, what kind? You can use tools like DNSPulse or manual checks against blacklists to uncover past abuse.

  2. Spam Complaint Rate: Even if you send clean emails, the IP may have a residual complaint rate from previous senders. This is not something authentication records show.

  3. Sending Patterns: ISPs look at volume, frequency, and consistency. A sudden spike in sending from a new IP can trigger spam filters.

  4. Reverse DNS and PTR Records: A proper reverse DNS record matching your sending domain adds credibility. Missing or mismatched PTR records can hurt deliverability.

  5. Shared vs. Dedicated IPs: Shared IPs pool reputation with other senders. If one sender on the IP misbehaves, everyone suffers. Dedicated IPs give you control but require careful warming.

How to Fix Infrastructure Issues

If you suspect your infrastructure is the problem, take these steps:

  • Audit Your IPs: Use a service that checks IP reputation history, not just current blacklist status. Look for past spam complaints or abuse reports.
  • Warm Up New IPs: Gradually increase sending volume over weeks to build a positive reputation. Start with highly engaged recipients.
  • Monitor Complaint Rates: Keep your spam complaint rate below 0.1% (Google's guideline). If it rises, pause and clean your list.
  • Use Dedicated IPs for High Volume: For cold outreach at scale, dedicated IPs let you control reputation. But they require careful management.
  • Check Provider Policies: Some ESPs have stricter infrastructure requirements. Choose one that maintains clean IP pools and offers transparency.

The Bottom Line

Authentication is table stakes. It proves you are who you say you are, but it does not prove you are a good sender. The real battle for inbox placement is fought in the infrastructure. As Ramakrishna warns, "Read yours today, while your ESP keeps whistling 'all clear, all clear.'"

Do not rely solely on authentication checks. Dig into the history of your sending IPs, monitor complaint rates, and ensure your infrastructure is as clean as your authentication records. That is where the majority of deliverability issues hide.

Final Thoughts

Cold email deliverability is a multi-layered challenge. Authentication solves only part of the puzzle. By focusing on infrastructure, you can address the root cause of many inboxing problems. Use the data available from tools like DNSPulse to uncover what your ESP might be overlooking. The truth is in the infrastructure, not just the authentication.