Why Your ESP Won’t Fix Deliverability Without These Questions

You send emails. They don’t land. Your ESP says “check your content” — again. You’ve run the basics: DNS records, unsubscribe links, spam score. Nothing changes. You’re not alone.

Most ESP support teams respond to delivery issues with generic checklists. They don’t see your sender reputation, your list hygiene, or how ISPs evaluate your traffic. Without the right deliverability audit questions to ask ESP support, you’re guessing at the real problem.

True inbox placement is shaped by data no ESP surface-level report shows—like whether bounces come from invalid addresses or signals that hurt your sender reputation. That’s why email verification isn’t just cleanup—it’s the diagnostic tool you’ve been missing.

Key takeaways

  • ESP support often lacks access to the data needed to diagnose deliverability failures.
  • Without asking about sender reputation, blacklists, and email verification scores, you won’t get actionable fixes.
  • Email verification data reveals whether bounces stem from invalid addresses or reputation issues, helping prioritize high-impact fixes.

What’s Your Sender Reputation Score? And How Is It Measured?

Sender reputation is a real-time, multi-factor score that tells you how likely your emails are to land in inboxes. It’s built from data like IP and domain history, spam complaint rates, engagement levels (open, click), bounce rates, and volume spikes. While some ESPs provide daily reputation scores via reports, they’re not always exposed—so you need to ask. Don’t assume it’s visible; demand it.

Ask for the Full Story Behind the Score

  • Request a direct report of your daily sender reputation score from your ESP (if available). Many platforms don’t expose this openly—don’t assume it's not there.
  • Ask what data sources feed into the score: is it based on your IP, domain, sending volume, user engagement, or spam complaints? The answer shapes how you fix low scores.
  • Spam complaints carry heavy weight—just one per 1,000 emails can trigger filters. Understand how your ESP counts them and whether they’re weighted more than bounces.
  • Look for correlations: a sudden drop in inbox placement often follows spikes in hard bounces or low engagement. Link reputation to list hygiene, not just the number itself.

Use Verification to Diagnose Real Problems

A score alone doesn’t tell you why your emails are failing. It’s a symptom. Use real email verification to check the health of your list at scale.

  • Run your entire list through MailTester’s bulk verification to identify invalid, risky, or catch-all addresses.
  • Check real-time delivery with inbox placement testing—see whether your message ends up in the inbox, spam, or gets blocked.
  • Use the email verification API to scrub new leads before sending, lowering future bounce and complaint rates.
  • Compare your ESP’s reputation score against your list’s actual deliverability signals. If the score is high but delivery is low, your list may be poisoned.

Reputation isn’t static. It’s shaped by your sending behavior, list quality, and how users react. Think of it like a credit score for email: high engagement and low complaints keep it strong. If your ESP won’t show you the full picture, dig deeper—verify your list, test delivery, and act on data, not guesses. Reliable reputation isn’t just reported—it’s built.

How Do You Handle Blocklists and Blacklist Notifications?

If your ESP doesn’t proactively monitor major blocklists like Spamhaus or SORBS, you’re flying blind. You need to know immediately when your IP or domain gets listed—and whether your provider helps you get delisted, especially if you’re on a shared IP pool. Otherwise, your sender reputation risks permanent damage.

Ask These Key Questions

  • Does your ESP perform automated daily checks against major blocklists, including Spamhaus and SORBS? Many providers do this in-house, but others assume you’ll self-monitor.
  • When your IP or domain appears on a blocklist, do they send you a real-time alert? A delay of even a few hours can cost you weeks of deliverability.
  • Can you get a detailed report showing the specific reason for the listing? Some providers only confirm presence on a list without context—this isn’t enough to fix the issue.
  • If you’re on a shared IP pool, does your ESP assist with delisting, or do you have to handle it yourself? Shared environments mean one bad sender can pull down the entire pool.
  • Are delisting requests handled promptly—ideally within 24–48 hours? Delayed responses increase the time your messages are quarantined or rejected.
  • Do they provide documentation or internal processes to help you prevent future listings? Prevention is better than cure, especially in high-volume sending environments.

What to Watch For

Some ESPs treat blocklist monitoring as optional. Others treat it as a core part of their infrastructure. Check whether your provider uses tools like Spamhaus or SORBS in their real-time feedback loops. These are industry-standard, so your ESP should be integrating with them.

When you’re running campaigns across multiple domains or IPs, blocklist visibility isn’t a luxury—it’s a baseline requirement. If you’re not getting real-time alerts, you’re at risk of sending to blocked recipients without knowing it.

For teams using shared IPs, the stakes are higher. The moment a single sender gets listed, you all suffer. Ask your ESP: “If one domain from our pool gets blacklisted, how quickly do you act?” If the answer is “We’ll notify you,” that’s not enough. You need proactive, documented support.

At MailTester, we help you catch issues early. Use our inbox placement tester to see if your email lands in spam, or verify your list with our bulk verification tool to reduce bounce and delivery risks before sending.

What’s the Real Reason for My Inbox Placement Drop?

Deliverability drops aren't always caused by your email content. Often, they stem from sender reputation issues, infrastructure problems, or temporary filtering by providers. You need the real reason—not guesses—so ask your ESP for detailed delivery logs showing exactly where and why messages failed to land in inboxes. Without this data, you’re guessing in the dark.

Ask These Specific Questions to Your ESP

  • Provide delivery logs from the last three campaigns, including bounces, blocks, and inbox placement rates per major provider.
  • Specify whether messages were flagged as spam, quarantined, or blocked by Gmail, Outlook, or Yahoo—and why.
  • Include timestamps and envelope-level details: sender IP, SPF/DKIM alignment, and any SMTP-level rejections.
  • Ask for a breakdown of inbox placement across real user inboxes, not just internal delivery statistics.
  • Request proof that your sender reputation (IP, domain, volume history) is not in a red zone with major filtering systems.

Validate Their Data with Your Own Testing

ESP delivery reports often use internal metrics or incomplete samples. Cross-reference their claims with independent inbox placement testing. Use MailTester’s real-time inbox placement tester to send identical messages to real Gmail, Outlook, and Yahoo inboxes and measure actual delivery rates and spam filter behavior.

For example, Spamhaus and RFC 5321 define how SMTP delivery works and how filtering systems evaluate messages. When your ESP says “high deliverability,” it’s not enough. Their logs might show “delivered”—but were they really seen by a real user?

MailTester’s inbox tester shows you the exact outcome in real inboxes, so you can spot discrepancies. If your ESP reports 92% inbox placement but MailTester shows 68% for Gmail, there’s a gap you need to address—possibly due to filtering thresholds, content scoring, or reputation issues not visible in the ESP’s internal reports.

Don’t take their word for it. You can test the same message with MailTester’s bulk verification first, then validate the results across providers. This way, you know if the problem lies with your list, sender setup, content, or the ESP’s delivery infrastructure.

Let’s be clear: if you’re not testing on real inboxes, you’re not measuring actual deliverability. That’s why a deliverability audit should include independent validation—no shortcuts.

Do You Provide Bounce Analysis Beyond ‘Invalid’ and ‘Hard’?

You should ask ESP support whether they track more than basic hard bounces—especially soft bounces, delayed deliveries, and catch-all or risky addresses. A single hard bounce might mean a typo, but repeated soft failures or delivery delays often signal underlying inbox placement issues, sender reputation strain, or problematic domains. A real audit should surface these early, not just flag obvious invalids.

What’s Missing in Standard Bounce Reports?

Most ESPs report only “hard” or “invalid” bounces—missing the nuance behind soft bounces, throttling, or delivery delays. These signals often indicate temporary server issues, high spam scores, or domains that accept mail but won’t deliver it reliably. Let’s be honest: a domain that returns a “catch-all” response isn’t necessarily fake—it’s often a gatekeeper that accepts all mail, which inflates your delivery rate but skews your engagement metrics.

How to Push for Better Insights

Ask your ESP to flag addresses that consistently trigger soft bounces, or generate delivery delays beyond 30 minutes. If a recipient’s domain accepts mail but rarely delivers it—especially across multiple sends—you’re likely hitting a grey area. These addresses aren’t “invalid,” but they’re not reliable either. Use a tool like MailTester’s bulk verification to catch these before you even hit send. Our 98.9% accuracy identifies catch-all domains, risky addresses, and disposable emails early—helping you avoid sender reputation damage before it starts.

For deeper insights, test actual inbox placement with MailTester’s inbox tester to see how your messages land in Gmail, Outlook, and Outlook.com. This reveals whether your ESP’s bounce list is complete—or whether you’re shipping to addresses that silently bounce or get filtered.

Don’t rely on basic bounce codes alone. Ask your ESP: “Can you show me the full delivery history for flagged domains?” If they can’t, you’re missing half the picture. Industry-standard tools like RFC 5322 define the structure of email addresses—but not the quality of delivery. Real deliverability requires more than a flag: it needs context.

How Are You Managing SPF, DKIM, and DMARC Alignment?

Ask your ESP whether they enforce strict alignment between the ‘From’ domain and your authentication records. Without it, even clean sending practices can fail—spammers exploit weak alignment to impersonate brands, and receivers block messages that don’t match. DMARC policies must be validated, and violations should be reported, not ignored. Use tools that test real-world alignment, not just theory.

Check Your ESP’s Alignment Enforcement

  • Confirm your ESP requires SPF and DKIM to align with the ‘From’ domain—especially for bulk sends. Misalignment breaks inbox placement even with a strong sender reputation.
  • Ask if they automatically enforce DMARC policies (e.g., quarantine or reject) based on your published policy. If not, you're leaving deliverability to chance.
  • Request access to DMARC aggregate reports (RUA) or forensic reports (RUF). These show real-world failures and help catch spoofing attempts early.
  • Verify that your ESP doesn’t allow sending from a domain different than the one used in the 'From' header unless strict alignment is enforced. Many legacy ESPs don’t, risking blocks from Gmail, Yahoo, and others.

Test Your Setup with Real-World Validation

  • Use an inbox placement tester like MailTester’s Inbox Tester to simulate delivery to major providers and check if alignment issues surface during testing.
  • Run bulk verification using MailTester’s Email List Verify to filter out addresses that might trigger alignment or authentication warnings during campaigns.
  • Integrate the MailTester API into your signup or onboarding flows to catch invalid or misaligned addresses before they get sent.
  • Check your current setup against the guidelines in RFC 7483—specifically, section 5.2 on alignment rules—which most modern ESPs are expected to follow.
The most common deliverability failure we see isn’t spam traps or poor content—it’s a missing or misaligned SPF/DKIM/DMARC configuration, often undetected until volume drops.

Weak alignment isn’t just a technical oversight—it’s a signal to receivers that your messages may not be authentic. Even trusted domains can fail if authentication doesn’t match the sending domain. If your ESP doesn’t report violations or enforce alignment, your inbox placement is at risk. Review your setup using real validation tools, and audit regularly—authentication doesn’t fix itself.

What’s Your Process for Domain and IP Warm-up?

If you're using a new domain or IP, you need clear, documented guidance from your ESP. Ask how long their warm-up cycle lasts, what sending volume they recommend per day, and whether they provide a customized schedule based on your audience size. Skipping this step risks inbox placement and can trigger spam filters. Let’s get specific.

Verify Before You Warm Up

  • Run your entire list through MailTester’s bulk verification before warm-up to remove invalid, role-based, and disposable email addresses that harm sender reputation.
  • Use the verification API to test large lists programmatically, especially if you’re automating sends.
  • Check for catch-all addresses—these can cause bounce spikes and signal poor list hygiene to ISPs.
  • Remove any addresses flagged as "risky" (e.g., high churn potential, temporary domains) to avoid early reputation damage.

Validate Your ESP’s Warm-Up Plan

  • Ask for a written warm-up schedule that aligns with your sending volume and audience size.
  • Confirm the duration of the warm-up cycle—many ESPs use 10 to 21 days for new IPs, but this varies.
  • Ensure they recommend a gradual ramp-up: start with 500–1,000 emails/day, then increase by 30–50% daily.
  • Verify they support monitoring deliverability at each stage using inbox placement testing with real inboxes—not just bounce logs.
  • Request examples of warm-up plans for similar-sized senders to benchmark their approach.
“Warm-up is not a formality—it’s a reputation-building phase. Skipping it is like launching a product with no user testing.” — Adapted from industry practices outlined in RFC 6650, which details email sender reputation and reputation signals.

Remember: your sender reputation starts the moment the first email departs. If your ESP isn’t proactive about warm-up or can’t show you how they manage it, you're relying on unverified assumptions. Use MailTester to harden your list, then validate the ESP’s plan with real-world data. That’s how you reduce bounces and boost inbox placement from day one. No guesswork.

Are Your Sending IPs Residing on Known Spam Sources?

You need to know if your sending IP has ever been flagged by third-party spam tracking services. If it has, even briefly, that can severely hurt your deliverability. Request historical logs showing bounce rates, complaint rates, and engagement trends over the last 90 days — anything showing a spike in abuse signals or consistent low engagement should raise red flags. Use tools like MxToolbox to check real-time blacklists, but don’t rely solely on them. The best defense is proactive validation: test each address before sending using real-time verification data to catch risky or invalid IPs before they harm your sender reputation.

What to ask your ESP support

  • Has our sending IP ever been listed on any third-party spam sources like Spamhaus or SORBS? Request full records, not just a yes/no.
  • Can you provide logs of historical IP performance, especially bounce rate, complaint rate, and open rate trends from the past 90 days? If the data doesn’t exist, that’s a warning sign.
  • Is the IP assigned to a known shared server or hosting environment? Shared IPs are more likely to be tainted by others’ behavior.
  • Do you monitor real-time blacklists and automatically remove IPs when listed? If not, ask how you’re alerted.
  • Can you confirm the current IP address used for sending? Some ESPs rotate IPs dynamically — validate the current one before sending.

Verify it yourself

Don’t wait for support. Check your IP in real time using MxToolbox’s blacklist check — it pulls data from major sources like Spamhaus, SORBS, and SpamCop. Still, this is reactive. Proactive detection is better. Use MailTester’s inbox placement to simulate real sends and verify whether your current IP can reach inboxes without being blocked. For bulk testing, verify your entire list with 98.9% accuracy to catch addresses linked to known spam IPs or blacklisted domains.

Even if an IP isn’t listed today, poor historical behavior can still affect deliverability. The RFC 7483 explains that spam filtering uses both real-time and historical data. Your deliverability isn’t just about today’s reputation — it’s about what happened yesterday, last week, and last month. Let’s not assume the past is clean. Validate every step.

What’s the Impact of Role Accounts and Disposable Domains?

Role accounts (like sales@, info@) and disposable domains (like tempmail.com) hurt deliverability. They signal low engagement, trigger spam filters, and damage sender reputation when used at scale. You should ask your ESP if they filter these addresses during delivery—and why.

Why Role Accounts and Disposable Domains Matter

Role addresses aren’t real people. They’re often monitored by bots or never checked, which means no engagement. If your list includes dozens of admin@ or support@ addresses, ISPs see that as a red flag. Same with disposable domains—users sign up just to get a one-time email, then abandon the address. Sending to these doesn’t improve inbox placement; it risks getting flagged.

The Mail-Tester team has seen campaigns fail just because role and disposable addresses made up 15–20% of the list. ISPs like Gmail and Outlook track engagement patterns. Repeated sends to unengaged domains—even if technically valid—can lower reputation scores over time.

How to Clean and Verify Before Sending

Let’s be clear: you can’t rely on your ESP to catch all of these. They may filter some, but not the ones that look valid on paper. That’s where a thorough deliverability audit comes in.

MailTester identifies role addresses and disposable domains with 98.9% accuracy. Our system checks against known lists of disposable domains (like those maintained by Spamhaus) and patterns of role-specific email formats. This isn’t guesswork—it’s real-time validation using proven data sources.

Before you send, verify your list. Use the bulk verification tool to detect and remove problem addresses. For developers, the real-time API can clean new signups instantly. And for confidence, test inbox placement with the inbox tester—it shows how real inboxes treat your message.

How Do You Monitor and React to Spam Complaints?

You should ask your ESP whether they track and report individual spam complaints per recipient, not just totals. If they don’t, you’re flying blind—complaints from one user can trigger blocks even if your overall complaint rate is low. Confirm whether they have automated alerts or threshold triggers for spikes in complaints. High volume, even from a single domain, can signal a pattern that blacklists or ISPs will act on—sometimes within hours.

Key Questions to Ask Your ESP

  • Do you track spam complaints at the individual recipient level, not just aggregate totals?
  • Do you send automated alerts when complaints exceed a defined threshold, like 1% of sends in a 24-hour window?
  • What happens when a complaint spike is detected? Is there an automated rollback, list quarantine, or manual review process?
  • Can you provide historical data on past complaint triggers and how they were resolved?
  • Do you proactively flag accounts or domains with unusually high complaint ratios, even if below your threshold?

Why This Matters

Spam complaints are one of the fastest ways to damage sender reputation. According to Return Path’s 2022 Email Sender and Consumer Behavior Report, a 0.1% complaint rate can result in deliverability drops for even well-established senders. Even a handful of complaints from a single domain—especially a high-volume one—can trigger filters at ISPs like Gmail or Outlook. The key isn’t just tracking complaints; it’s reacting fast.

Let’s be clear: you can’t control every user’s click. But you can control how quickly you respond. If your ESP waits until the next day to flag a spike, the damage is already done. Ideally, systems should detect and act within minutes.

Tools like inbox placement testing help validate whether your messages are landing in inboxes and being marked as spam. Combined with real-time email verification, you can catch problematic addresses before they trigger complaints. This is especially important for cold outreach, where list hygiene makes or breaks reputation.

“A single spam complaint from a corporate email domain can be enough to trigger an automated block.”

You Can’t Fix What You Can’t Measure: Audit With Verification

Even the most confident ESP claims can’t replace real-world validation. Without verification, you’re guessing about list health, sender reputation, and inbox placement.

Use MailTester’s real-time API and inbox placement tests to measure what matters: open rates, bounce rates, and delivery outcomes across major inboxes. This shows whether your ESP’s promises align with actual performance.

Start with 100 free verifications. Test your list, challenge your ESP’s claims, and build a deliverability strategy grounded in data—not assumptions.

Sources

Keep reading

Ready to put this into practice? MailTester verifies emails with 98.9% accuracy — start with 100 free verifications.

Frequently asked questions

What questions should I ask my ESP about deliverability?

Ask about sender reputation metrics, blocklist monitoring, bounce analysis, inbox placement rates, warm-up practices, and spam complaint handling. Cross-check answers with verification data.

How can I tell if my ESP is hiding deliverability issues?

If they avoid sharing reputation scores, blocklist reports, or placement metrics, it’s a red flag. Use independent verification tools to confirm.

Can an ESP fix deliverability without list hygiene?

No. Even with perfect setup, sending to invalid or role addresses harms reputation. Clean lists first with tools like MailTester.

What do you do when an ESP blames ‘spam filters’?

Demand specifics. Ask which filter flag caused the block. Use inbox placement testing to verify whether the issue is consistent across inboxes.

Why should I use email verification before asking ESP support?

It exposes invalid, catch-all, and disposable addresses. ESPs often blame filters when the real issue is list quality.

How often should I run a deliverability audit with my ESP?

At least quarterly. Or before major campaigns, new domain launches, or IP changes. Consistency beats urgency.

Can a high bounce rate be a sign of poor sender reputation?

Yes—persistent hard bounces or high volume of soft bounces signal list decay or spam-like behavior, even if messages aren’t filtered.

Is it normal for an ESP to not share their deliverability score?

No. If they withhold reputation data, you can’t assess risk or track improvements. Demand transparency.

What’s the role of DMARC in deliverability?

DMARC ensures that only authorized senders use your domain. Misalignment can break delivery and trigger spam filters.

Can disposable domains hurt my deliverability?

Yes. They typically never engage and can inflate spam complaint rates. Remove them with accurate verification.

How does MailTester help during an ESP deliverability audit?

It identifies invalid, catch-all, role, and disposable addresses—proving list quality before sending. Use it to challenge ESP claims with data.

What if my ESP says ‘we handle all reputation issues’?

That’s unverifiable. Ask for logs, reports, and thresholds. Use independent testing to verify performance and hold them accountable.