Vendor Email Health Evaluation | Email List Validation

Why rely on known good and known bad addresses to assess email hygiene?

You send a campaign. The open rate is low. The bounce rate is normal. But your inbox placement is terrible. You’ve checked syntax, verified domains, cleared common typos—yet the emails keep landing in spam or vanishing into thin air.

That’s because valid doesn’t mean safe. A technically correct address can still be a trap, a stale inbox, or a signal of poor list hygiene. Evaluating vendor email health with known good and known bad address filtering reveals what syntax checks never will: whether someone’s list is actually deliverable in real-world conditions.

Think of known good and known bad addresses as a control group. Known good ones validate that your vendor’s list can reach real inboxes. Known bad ones test whether the vendor’s list is contaminated with spam traps or inactive accounts—those silent destroyers of sender reputation.

Key takeaways

Known good and known bad addresses act as a practical benchmark for real-world deliverability, beyond basic syntax validation.
Testing against known bad addresses reveals whether a vendor’s list includes spam traps or role accounts used as honeypots.
Using this method exposes patterns of poor hygiene—like high concentrations of disposable domains or role-based addresses—before they damage sender reputation.

What does 'known good' really mean in email verification?

A 'known good' email address is not just valid—it’s a real mailbox with a history of engagement, consistent deliverability, and a user who opens and interacts with your messages. It’s not enough for an address to pass syntax checks or receive mail; true known good means the user is active, not a role account, disposable, or part of a catch-all system. If you’re sending to this address, you’re more likely to land in the inbox—and stay there.

Validity isn’t enough

Many tools label any address that passes basic syntax and domain checks as "valid." But that includes role accounts (like admin@, sales@), catch-all inboxes (which accept mail for any address), and disposable email domains (like tempmail.com). These may bounce, never open, or even flag your sender as spam. Just because an address is "valid" doesn’t mean it’s worth sending to.

Let’s be clear: a valid address can still be a dead end. A catch-all might accept your message, but no real person ever sees it. A role account may get delivered—but it’s usually ignored, or routed to a spam folder. In fact, high volumes of mail to such addresses can tank your sender reputation over time.

What makes an address truly known good?

A known good address is one that’s verified as both deliverable and associated with a real, engaged user. It’s not just about whether mail gets through—it’s about whether it’s seen and acted on. This means the address must have a history of opens, clicks, or other positive engagement, ideally within your own sending patterns. That’s why you can't infer known good status from verification alone.

Industry standards—like those defined in RFC 5322 and RFC 6522—focus on syntax and routing, not engagement. But real deliverability depends on more than that. The return path (RTP) and feedback loops (FBLs) used by ISPs to monitor sender behavior are the real indicators of quality. A true known good address has a proven track record in those systems.

If you’re validating a list, don’t settle for "valid." Instead, look for signals of real user activity. That’s what Email List Validation offers with its 98.9% accuracy: it doesn’t just check if an address can receive mail—it determines whether that mail is likely to be seen and interacted with. You can test this with inbox placement testing or process large lists with bulk verification to filter out dead ends. For real-time checks, the API integrates into your workflow to catch bad addresses before they’re sent.

How do 'known bad' addresses expose vendor weaknesses?

Known bad addresses—like spam traps, role accounts, disposable domains, and inactive catch-alls—are not just invalid; they signal poor list hygiene, outdated sourcing, or weak validation practices. If a vendor’s list contains many of these, it reveals a lack of discipline in acquisition, validation, or ongoing maintenance. These addresses don’t just bounce—they actively damage sender reputation and increase the risk of blacklisting.

What 'known bad' addresses reveal about vendor practices

You can’t filter what you don’t know. A high count of known bad addresses in a list is a red flag that the vendor likely relies on unverified web scraping, uses low-quality lead-generation methods, or skips validation during onboarding. Spam traps, for instance, are old or abandoned email addresses deliberately used to catch spammers. If a vendor’s list contains them, it’s a sign their source data has not been cleaned or refreshed in years.

Role accounts like admin@, sales@, or support@ often appear in lists built through automated harvesting. These are frequently non-responsive and can generate bounces or spam complaints. Disposable domains (like mailinator.com or 10minutemail.com) are used for short-term sign-ups—most don’t accept mail long-term and can trigger spam filters when used at scale.

Why these addresses hurt deliverability

Even a single bad address can trigger a reputation penalty. ISPs like Gmail and Outlook use sender reputation as a key signal for inbox placement. Sending to spam traps or disposable emails can result in temporary blocks or long-term blacklisting. According to Return Path's [sender reputation research](https://www.returnpath.com/research/) (formerly known as Validity), even a small percentage of spam traps in a list can significantly degrade deliverability.

These issues aren’t just about bounces—they’re about trust. A vendor that sends to known bad addresses is signaling to inbox providers that they lack operational rigor. High bounce rates, spam complaints, and poor engagement all feed into the same signal: this sender is not reliable.

Let’s be clear: known bad addresses aren’t just noise—they're liabilities. Use tools like bulk email verification to identify and remove them before sending. The same goes for real-time validation via our API, which checks each address as it’s entered. It’s not about perfection—it’s about reducing harm.

How to build a reliable known good and known bad test set

You can build a trustworthy test set by starting with your own engaged users—those who opened, clicked, or purchased in the past 12 months—for known good addresses. For known bad, use isolated, controlled addresses: spam traps from Spamhaus, role accounts like [email protected], or disposable emails from services like Mailinator. Never test with live campaign addresses to avoid triggering alerts or polluting your data. This process ensures your email health checks reflect real-world deliverability, not noise.

Step-by-step: creating your test set

Identify known good addresses from your own engagement data. Pull users from your CRM or email platform who’ve opened, clicked, or made a purchase within the last 12 months. These are real, active recipients who’ve shown interest. Using your own verified users reduces false negatives and gives you a benchmark for what “healthy” email engagement looks like.
Obtain verified spam traps from trusted sources. Spamhaus maintains public spam trap lists—use their lookup tool to find valid trap addresses. These are old, inactive emails that, if accidentally sent to, can damage your sender reputation. They serve as a sensitive indicator of email hygiene.
Use isolated disposable email addresses from known services. Create test accounts at Mailinator, TempMail, or other transient email providers. These are not tied to real users and are designed to catch spam. Use them only for testing—do not send to them in live campaigns. Their primary purpose is to confirm if your system correctly flags disposable domains.
Include a role account address for robust testing. Use an address like [email protected] or [email protected] as a known bad example. Role accounts are commonly flagged by filters and are useful for testing whether your service detects problematic inboxes that don’t accept mail.
Verify each test address for accuracy before use. Run each address through an email-verification service like Email List Validation to confirm its status. This ensures you’re not testing with typos or outdated formats. You can use their real-time API to automate this step across large test sets.

Keep testing isolated

Never test with addresses in your live sender database or active campaigns. Every send to a trap or disposable domain risks triggering spam scoring or even blacklisting. Use separate test environments, dedicated test domains, and controlled send profiles. The goal is to measure health, not harm. Treat your test set like lab equipment—precise, clean, and untouched by production traffic.

Accuracy in testing begins with isolation. A single unintended send to a spam trap can distort your whole assessment.

The practical test: running a vendor’s list through known good and bad filtering

You can evaluate a vendor’s email list by uploading it to Email List Validation and filtering results through known bad patterns—like role accounts, disposable domains, and inactive catch-alls—then comparing how many invalid or risky addresses appear. This gives you hard data on list quality before sending.

Upload the vendor’s list using bulk verification. Go to Email List Validation’s bulk verification feature and upload the vendor’s email list. The tool checks each address in real time using SMTP, MX, and DNS protocols, identifying syntax errors, routing problems, and invalid domains.
Test inbox placement on a representative sample. Use the inbox-placement feature on a small, randomized subset—say, 50–100 addresses. This simulates real sends and shows how many end up in inboxes, spam folders, or bounce. This is a reliable sign of sender reputation health, as noted in industry practices around Spamhaus and email deliverability reports.
Filter by verdicts to isolate known bad patterns. After verification, apply filters based on result verdicts: invalid (syntax or routing failure), catch-all (no real mailbox), risky (role, disposable, or low engagement), or unknown. Focus on the "risky" and "invalid" groups—they represent the real threats to deliverability.
Compare bad matches against the total list size. Calculate the percentage of known bad addresses: role accounts (like admin@, contact@), disposable domains (e.g., mailinator.com), inactive catch-alls, or known spam traps. A list with more than 5% risky or invalid entries typically harms sender reputation and reduces inbox placement.

What the numbers reveal

Even a 1% rate of disposable or role accounts can signal deeper list hygiene issues. These addresses are often harvested or auto-generated, and sending to them harms your sender reputation. ISPs like Gmail and Outlook track patterns of spammy sends, and high volume to low-quality addresses triggers automated blocks.

For example, a list with 200 invalid or catch-all addresses out of 5,000 emails (4%) will likely trigger greylisting or be flagged as high risk by DMARC policy enforcement. A real-world check shows this threshold is common in low-quality vendor lists, as documented in RFC 5322 and observed in MxToolbox diagnostics.

Let’s be clear: no list is perfect, but knowing your starting point reduces risk. Use the inbox-placement test to see how your vendor list performs under real conditions, not just checks on syntax.

Benchmarking a vendor’s list using actual verification verdicts

You can evaluate a vendor’s email health by analyzing real verification results: aim for under 1% invalid or risky addresses, limit catch-alls to under 5%, avoid disposable domains, and watch for spam trap hits. These signals reveal how the list was collected and cleaned, not just how many emails it contains. Let’s break down what each verdict means in practice.

Checklist: What to look for in verification verdicts

Under 1% invalid or risky addresses is a solid benchmark. More than that means the vendor is likely sourcing from low-quality or outdated systems. Real-world email lists from reputable vendors typically stay below this threshold.
Catch-all detection over 5% is a red flag. It suggests the list uses broad, non-specific patterns—common when data is scraped or guessed, not verified. Catch-alls accept any address, so high rates indicate poor targeting or poor source hygiene.
Disposable domains (e.g., @mailinator.com, @10minutemail.com) in higher volumes indicate scoured or aggregated data. These are commonly used for temporary signups, so a high number signals low-value sources. Lists with more than 2–3% disposable domains are usually unreliable for real engagement.
Spam trap hits are one of the fastest ways to confirm poor data hygiene. These are inactive addresses set up to catch spammers. If your list includes them, the vendor likely uses old or unverified sources. The presence of spam traps directly harms sender reputation, even if delivery seems to work. See Spamhaus for how traps are used to identify bad actors.
Use actual verification tools—not just syntax checks or free email domain lookups. Tools that simulate real delivery paths (like inbox placement tests) give clearer signals of how a list will behave in real inboxes. For example, inbox placement testing can show if a vendor’s list lands in spam folders, even if addresses appear valid.

How to act on these signals

If you’re reviewing a vendor’s list, run it through a trusted email verification service. You’re not just checking if emails exist—you’re verifying how they were sourced and maintained. A vendor that scores well on these metrics likely uses opt-in collection, regular cleaning, and avoids scraping.

For ongoing validation, integrate a real-time API for new signups—like our API. It prevents risky emails before they even enter your system. For bulk lists, bulk verification gives you a clear breakdown of each email’s status, including risk indicators and domain quality.

Remember: a clean list isn’t just about delivery. It’s about reputation. The fewer bad habits in the data, the more sustainable your outreach will be over time.

How Email List Validation enables precise filtering of known good and bad addresses

You can evaluate vendor email health by testing addresses in real time, using verified data to distinguish valid recipients from invalid, disposable, catch-all, or risky addresses — all with 98.9% accuracy. This ensures only known-good emails move forward in your campaigns, reducing bounces, protecting sender reputation, and improving inbox placement. The process is reliable, automated, and integrated directly into your workflow.

Real-time results, validated at scale

The real-time verification API lets you test individual addresses with precision, returning one of five clear verdicts: valid, invalid, catch-all, risky, or unknown. Each result reflects a specific technical condition — like whether the domain exists, if the mailbox accepts mail, or if the address is role-based or temporary. This granularity means you’re not guessing; you’re acting on facts.

For example, a “catch-all” verdict indicates the domain accepts all emails, which means the address might exist but won’t reliably deliver. A “risky” flag may signal a disposable domain or a high bounce rate pattern. These distinctions matter when filtering vendor lists or assessing inbox placement potential. The 98.9% accuracy rate means these decisions are data-driven, not speculative.

Seamless integration, smarter filtering

You can integrate Email List Validation with platforms like SendGrid, Mailchimp, and Klaviyo to automatically clean incoming vendor lists before you send. This means invalid or low-quality emails are filtered out before they impact deliverability, reducing abuse-related blocklist risks and sender reputation damage.

When you run a list through the tool, it flags role accounts (like sales@) and disposable domains before they even hit your campaign flow. That’s critical because role accounts and temporary addresses often lead to high bounce rates and poor engagement — directly hurting your domain score. By catching them early, you maintain a clean, trustworthy send profile.

Want to understand why certain addresses were flagged? The in-app AI assistant helps interpret results and surface atypical patterns—like a spike in role accounts from a single vendor or unusual domain behavior across a batch. It’s not a replacement for human judgment, but it reduces the time needed to triage and validate vendor data.

For continuous validation, use our bulk verification to clean entire vendor lists at once: check your list health now. For live integration, access the real-time API at: integrate with your system.

Why known good and bad filtering beats generic spam score tools

Generic spam score tools assign risk based on outdated patterns and surface-level traits—like suspicious domains or misspellings—without testing what actually happens when you send. They often mark role accounts (e.g., sales@, info@) or catch-all domains as safe, even when they never receive mail, creating false confidence. Real email health comes from behavior, not theory. Known good and bad filtering uses real-world verification data to show what inboxes actually accept and what gets blocked—because it tests delivery, not just prediction.

Spam scores don’t test delivery behavior

Most spam score tools rely on static rules and databases that date back years. They check for red flags like IP reputation or common spam keywords, but they can’t tell you whether an email address actually received your message. A score of “low risk” doesn’t mean delivery. It just means the address passed a checklist. Many role accounts and catch-alls score well—because they’re not technically invalid—but they never deliver. If you’re sending to them, your campaigns are wasting bandwidth, hurting sender reputation, and failing inbox placement.

Real-world data shows the truth

Known good and bad filtering runs actual SMTP tests against real mail servers. It doesn’t guess—whether a given email is deliverable. It checks. This includes detecting catch-alls (which accept all mail, but never deliver it), role accounts (which often bounce or go to spam), and disposable domains (which are designed to vanish). This is how you uncover the real health of your list—no models, no assumptions.

For instance, a 2021 study from Return Path found that up to 17% of email campaigns failed to reach the inbox, even with clean lists. Much of that came from addresses that were technically valid but not actually deliverable. Tools that only check syntax or spam score miss this entirely. They can’t see what’s happening in real SMTP interactions. You can’t fix what you can’t measure.

That’s why tools like Email List Validation focus on actual delivery behavior. By simulating real sends and verifying domains through SMTP, we surface hidden health issues that scores miss. Whether you're validating a list of 10,000 or checking a single email via our API, you get answers rooted in real-world response—not theoretical risk. It’s how you build a list that actually delivers.

How to use inbox-placement testing to validate vendor performance

You can evaluate a vendor’s email health by sending test emails to 20–50 known good and known bad addresses from their list using Inbox Placement testing. If the known good addresses land in the inbox, you’ve confirmed deliverability. If they’re flagged as spam or bounce, the vendor’s list quality or sender reputation is likely compromised — even if all addresses passed syntax checks.

Run a test with a sample of 20–50 addresses from the vendor’s list using Email List Validation’s inbox-placement tool. Include a mix of known good (verified, active) and known bad (invalid, role-based, disposable) addresses to assess filtering behavior.
Review delivery outcomes for each address. Check if the message landed in the inbox, was marked as spam, or bounced. Spammers often get filtered aggressively by modern inbox providers, so a high spam rate indicates problems with list hygiene or sender reputation.
Calculate deliverability rate by dividing the number of known good addresses that reached the inbox by the total number of known good addresses tested. For example, if 42 out of 50 good addresses landed in the inbox, deliverability is 84%. This gives you a real-world measure of how well your messages are being received.
Assess results against thresholds. A deliverability rate below 85% suggests systemic issues — possibly outdated data, poor sourcing, or compromised sender reputation. Even if all addresses pass syntax checks, a low inbox placement rate means your mail won’t perform well at scale.
Repeat with different vendors or at different times to spot trends. Some vendors may appear clean now but show higher spam rates over time, indicating inconsistent list maintenance. Use the inbox placement report to track changes and make comparisons.

Why known good vs. known bad filtering matters

Testing both types reveals how the vendor’s list behaves under real-world conditions. Known bad addresses should bounce or be rejected — if they don’t, the list contains low-quality or disposable domains. Known good addresses should reach the inbox, not spam. If they don’t, the issue isn’t the address — it’s sender reputation or content.

Benchmarking against industry standards

According to industry benchmarks, inbox placement rates above 85% are considered strong for transactional mail. Rates below this range often correlate with poor list management, outdated data, or blacklisted IPs — all of which hurt long-term campaign performance. You can validate your vendor’s delivery performance against these real-world expectations through consistent inbox placement testing.

For a complete view of vendor email health, pair inbox placement with bulk list verification. Use bulk list cleaning to flag invalid, catch-all, or role accounts before sending. This reduces bounce rates, preserves sender reputation, and improves your overall deliverability.

The bottom line: how to make vendor email health a measurable standard

Treat vendor list quality as a performance metric, not a pass/fail check. Define clear thresholds—like capping risky addresses at 1%, banning disposable domains, and blocking known bad addresses—to turn subjective judgment into objective standards.

How to enforce those standards

Use real verification data to assess vendor lists—never rely on assumptions or unverified claims.
Reject vendors whose lists exceed your thresholds; this removes guesswork from vendor selection.
Re-test vendor emails periodically: even clean lists degrade over time due to churn, inactive accounts, or outdated sources.

Quality isn’t static. Monitoring vendor list health continuously ensures ongoing deliverability and inbox placement.

Sources

Segmented campaigns also protect list health, driving 9.37% fewer unsubscribes, 4.65% fewer bounces, and 3.90% fewer abuse reports than unsegmented sends. — Mailchimp (2025)
HubSpot's list-health benchmarks show an average bounce rate of 2.48% and an average unsubscribe rate of 0.22% across industries. — HubSpot (2025)

Keep reading

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

Frequently asked questions

How do I identify if a vendor’s email list is using role accounts?

Use email verification to detect addresses like admin@, support@, or sales@. These fall under 'risky' or 'role' verdicts. High volumes signal poor list sourcing.

Can disposable email domains be reliably detected?

Yes—Email List Validation detects disposable domains like @10minutemail.com and @mailinator.com with high accuracy, classifying them as 'risky' at the point of verification.

What’s the difference between a catch-all and a valid address?

A catch-all accepts mail for any address on the domain but may lack a real user. These are typically 'risky' or 'catch-all' verdicts—useless for deliverability.

How often should I recheck a vendor’s list?

Recheck every 3–6 months or after a major data acquisition. List health degrades over time due to churn and poor hygiene practices.

Can known bad addresses appear in a 'valid' list?

Yes—some tools mark invalid addresses as 'valid' if they pass syntax checks. Email List Validation identifies them as 'risky' or 'catch-all', preventing false confidence.

Why trust a 98.9% accuracy rate?

It’s based on real-world testing across domains, ISPs, and delivery scenarios. Accuracy includes detection of disposable, role, and catch-all addresses.

Do verified addresses always deliver to the inbox?

No—verification confirms the address is syntactically valid and routing is functional. Inbox placement depends on sender reputation, content, and engagement, not just validity.

How do I use the in-app AI assistant during list reviews?

It analyzes verification results and flags patterns like excessive catch-alls, disposable domains, or high-risk role accounts—offering insight into vendor issues.

Are there free tools to test email list health?

Some tools offer free checks, but they lack the depth and accuracy of Email List Validation. It offers 100 free verifications to start, with no expiry on purchased credits.

What happens if a vendor has a high rate of catch-alls?

It suggests the list relies on broad, unverified inputs. These addresses don’t represent real users and hurt deliverability, even if they don’t bounce.