Verification Score Thresholds: What to Set

Why your verification score threshold matters more than you think

You send emails to 10,000 contacts. 230 bounce. One of them was a hard bounce from a real, active inbox. The rest? Invalid, disposable, or role-based. You never intended to send to them — but your verification system let them through because your threshold was too low.

That’s the cost of a poorly set verification score threshold: wasted sends, damaged sender reputation, and emails that never make it to the inbox. A score threshold isn’t just a technical setting — it’s a gatekeeper. Set it too loose, and your list fills with noise. Set it too strict, and you lose real leads. The right balance protects deliverability and maximizes impact.

Understanding verification score thresholds — and what to set them at — is fundamental to controlling bounce rates, avoiding spam filters, and keeping your messages in front of real people. This guide breaks down how to set that threshold right, based on real inbox placement mechanics and deliverability best practices.

Key takeaways

A threshold too low allows invalid or risky emails to slip into your list, increasing hard bounces and damaging sender reputation.
Even a 1% failure rate in list quality can trigger spam filters or lead to folder graveyard placement due to aggregate engagement signals.
The optimal threshold depends on your industry, list source, and engagement goals — balancing list size with inbox placement reliability.

What does a verification score actually measure?

A verification score measures the likelihood—based on technical checks—that an email address is valid, active, and likely to receive messages. It’s not a pass/fail label, but a confidence rating derived from domain checks, syntax validation, mailbox existence, and behavioral signals like response patterns. You can think of it as a probability score, not a binary judgment.

The Mechanics Behind the Score

Each verification service uses a unique algorithm to assess real-world delivery likelihood. At its core, this involves checking if the domain exists, if the email format follows standard rules (RFC 5322), and whether the mailbox responds to verification attempts. Services also analyze patterns in server behavior—like temporary bounces or greylisting—to detect risky or low-quality addresses.

For example, a domain might pass DNS checks but have no MX records, triggering a low score. Similarly, a technically valid address may be a throwaway or role-based (like admin@ or sales@), which increases the odds it won’t be read—another reason for a lower score.

Meaning of the Score: Not Just Valid or Invalid

Think of a score not as "valid" or "invalid," but as a gradient of confidence. A high score—say 90% or above—means the system has strong evidence the address is deliverable. A lower score doesn’t mean the address is broken; it means there’s uncertainty. These addresses are flagged as “risky,” not necessarily invalid.

Take our 98.9% accuracy rate—this means Email List Validation correctly identifies the status of email addresses in 98.9% of cases across our testing. That includes both valid and invalid addresses, which is a strong benchmark in the space. But even highly accurate tools need to show confidence levels, because not all domains and mailboxes behave the same way.

For instance, an address might pass syntax and DNS checks, but if the server replies with a temporary error (like 4xx), that’s a sign of delay or filter throttling. This doesn’t break the address, but it does raise uncertainty. In such cases, the score reflects that risk without marking the address as outright undeliverable.

This approach mirrors industry-standard practices in deliverability and sender reputation. Tools like MxToolbox or Spamhaus help track blacklists and server behavior—factors that influence real-world inbox placement. You can test your own deliverability with our inbox-placement tool: inbox-placement.

Understanding these scores lets you set thresholds that fit your goals. A high threshold (e.g., 95%) filters out nearly all risky addresses but may reject some borderline-valid ones. A lower threshold (e.g., 80%) keeps more prospects but increases bounce risk. The right balance depends on your use case.

The core verdicts: what each score level means in practice

You don’t need to guess. A verification score isn’t just a number—it tells you exactly how safe and usable an email is. Valid means it’s real and deliverable. Invalid means it should be removed. Catch-all? Dangerous. Risky? Handle with care. Greylisted? Temporarily delayed, not failed. Knowing what each level truly means saves you from wasted sends, spam complaints, and damaged sender reputation. Let’s break down the real-world implications.

Understanding the verdicts: what each score means

Each verification result comes with a clear, actionable label. These aren't arbitrary; they reflect actual server behavior and network signals. Here’s what they mean in practice, based on how email systems actually work.

Verdict	What It Means	Recommended Action	Why It Matters
Valid	Address exists, domain is live, and the server accepts mail. The email can be sent.	Keep for outreach.	These are your highest-quality leads. They’re likely to open and engage. A bulk verification tool checks thousands at once and flags these.
Invalid	Domain doesn’t exist, syntax is wrong, or server blocks the address outright. Often a typo or expired account.	Remove immediately.	These cause hard bounces, hurt your sender reputation, and can lead to blacklisting. ISPs see repeated invalids as signs of poor list hygiene.
Catch-all	Server accepts all emails, even invalid ones. No validation is done at the recipient level.	Avoid for campaigns. Use only for transactional systems when needed.	High spam risk. If the email doesn’t exist, you might still send—but you’ll likely be marked as abusive. API verification detects these early.
Risky	Score below threshold. Could be a role account (e.g. sales@), disposable domain, or temporarily offline inbox.	Review manually or filter out if volume is high.	These may not bounce now, but they’re less likely to engage. They can still harm deliverability if overused in mass sends.
Greylisted	Server temporarily delays delivery to check for legitimacy. Common in well-configured mail systems.	Don’t act on it yet. Retry after delay.	Not a failure. The server is doing its job. RFC 5617 defines this behavior. But if it persists, it may signal a problem.

These verdicts are based on real SMTP responses, DNS checks, and pattern matching—nothing speculative. The free 100-credit plan lets you test how they work on your own list before scaling. No guesswork. Just clarity.

Common pitfalls in setting score thresholds

You risk either cutting out too many legitimate users or letting in spam traps and low-quality addresses if your verification score threshold isn’t balanced to your sending context. A score too high excludes valid emails; one too low lets in disposable domains, role accounts, and bots—both hurt deliverability. Adjusting thresholds without monitoring outcomes masks long-term harm to your sender reputation.

Setting thresholds too high

Setting a threshold above 90 often removes 10–15% of valid emails, especially those with less common domains or typo corrections.
High thresholds may reject newer accounts, college emails, or addresses from smaller ISPs that pass basic SMTP checks but don’t score perfectly.
Many marketers mistakenly treat a "high score" as a guarantee of inbox placement—but delivery depends on engagement, not just syntax. Use bulk verification to test thresholds against real list performance before applying them at scale.

Setting thresholds too low

Thresholds under 70 let in disposable domains (like mailinator.com), role accounts (admin@, sales@), and automated test emails.
These addresses often trigger spam filters or create high bounce rates, even if they technically “validate.” The inbox placement tool can reveal how low-scoring emails perform in real inboxes.
Letting in bots or vacuous accounts inflates your list size while degrading engagement—Google and ISPs measure this, and penalize senders with weak domains.

Ignoring sending context

Transactional emails (password resets, order confirms) can tolerate lower scores since they’re user-initiated and high-engagement.
But promotional campaigns require higher thresholds—most platforms consider emails below 85 as risky due to lower engagement signals.
Don’t apply one rule everywhere. Your threshold should reflect the email type, audience, and past performance. Use real-time verification during signup flows to preserve intent without over-filtering.

Not reviewing results after changes

Changing a threshold without measuring deliverability or bounce rate over 2–4 weeks can hide long-term damage to your sender reputation.
If you raise the threshold and see a spike in hard bounces, you may have removed valid addresses. If you lower it and deliverability drops, disposable or role emails are likely entering your list.
Review performance data monthly. Track whether list size, open rates, and complaint rates align with your adjusted score cutoffs. Without this, you’re guessing.

“A flawless email list isn’t about perfection—it’s about relevance.”

Use the right tool for your needs

For one-time list cleanups, use bulk list verification to identify risky addresses across thousands of emails.
For live verification, integrate the verification API to clean signups in real time.
Use email finder to source contacts with known domains, reducing the risk of low-scoring or disposable addresses.

How to find your optimal cutoff score

Start with a 90 verification score threshold for general list hygiene—it hits a balance between blocking bad addresses and keeping valid ones. Test it across your actual campaigns, track deliverability and bounce rates before and after, then adjust based on your domain’s sending history and current reputation. Use inbox-placement testing to see real-world delivery outcomes, not just theoretical scores.

Test your score in real campaigns

Begin at 90—this is a proven starting point for most senders. It blocks likely invalid or disposable emails while retaining a high percentage of valid, active addresses. A score below 90 indicates higher risk of hard bounces or spam traps.
Run controlled tests—split your list into two groups: one filtered at 90, the other untouched. Send the same campaign to both and monitor results over 72 hours. Track hard bounces, soft bounces, spam complaints, and inbox placement rates. Services like inbox-placement testing give you data on how real inboxes receive your messages, not just delivery status.
Adjust based on reputation and history—if your domain has a clean sending record and high engagement, consider lowering the threshold to 85 for larger lists. If you’re recovering from a deliverability issue, raise it to 95 to avoid risking reputation with risky addresses.
Use historical data—review past campaign performance. High bounce rates? Likely due to low-scoring addresses slipping through. Low open rates? Could point to high-risk or unengaged emails. Adjust your cutoff to match the quality level your past campaigns achieved.
Validate with real-world delivery—verification scores don’t guarantee inbox placement. A high score doesn’t mean an email will land in the inbox. That’s why inbox-placement testing is the final check—it shows whether your email survives spam filters and reaches inboxes, not just servers.

Use the right tools to measure what matters

Verification scores are only as good as the tools behind them. Email List Validation uses multiple signals—including SMTP checks, domain health, and role account detection—to assign scores. These signals are not arbitrary. They follow established industry standards, like those outlined in RFC 5321, which governs SMTP behavior. The goal isn’t perfect accuracy—it’s reliable signal-to-noise ratio.

A 98.9% accuracy rate (based on internal tracking over 10M+ checks) isn’t a promise—it’s a benchmark. No tool can guarantee 100% results due to dynamic factors like greylisting, temporary server outages, or catch-all domains. But you can minimize risk by testing thresholds against real delivery outcomes.

Once you’ve found a score that balances hygiene and reach, you can maintain it long-term—or adjust dynamically based on campaign type. Promotional sends may need stricter cutoffs; transactional messages may tolerate lower scores. The key is consistency and data-driven refinement.

For real-time validation in your workflow, try the real-time verification API. For bulk cleanup, use bulk verification. You’ll always have 100 free verifications to start, and credits never expire.

When to lower your threshold (and when not to)

You can safely lower your verification score threshold to 80 for highly engaged, low-volume campaigns with high intent—like nurturing existing customers or targeting warm leads. But avoid going below 80 for cold outreach, bulk sends, or when warming up a new IP or domain. Never drop below 75, even for testing. Lowering thresholds too much increases the risk of spam traps, blocklists, and poor deliverability. Clean lists matter at every stage.

When it’s safe to lower the cutoff

Set the threshold to 80 if your list is verified, highly engaged, and you’re sending low-volume campaigns (under 500 emails per day) with high personalization, like product updates or exclusive offers.
Use a lower threshold only when your list has a long history of positive engagement—open rates above 30%, low bounce rates, and consistent click-throughs.
Don’t apply this to any outreach that doesn’t already show behavioral signals (e.g., past opens, clicks, or purchases). Even small drops in list quality hurt long-term sender reputation.

When to keep thresholds high (or raise them)

Never drop below 80 for cold outreach or bulk campaigns. The risk of hitting spam traps or being flagged by reputation systems rises sharply at lower scores.
Avoid lowering thresholds when warming up a new IP address or domain. Sending to lower-confidence addresses during this phase can trigger spam filters and delay reputation building.
Never use a threshold below 75, even for testing. You’ll likely ingest disposable emails, role addresses, or invalid syntax—noise that degrades sender reputation over time.
For new domains without any sending history, aim for a score of 90+ before launching campaigns. This reduces risk during the first 7–14 days of warming up.

Even a single email sent to a spam trap can result in a domain-wide block. It’s not worth the risk—clean lists are the foundation of deliverability.

For deeper context on sender reputation and deliverability, see the IETF’s guidelines on email authentication and how reputation systems factor in message quality. For real-time verification, explore our real-time API or bulk verification to clean high-risk segments before sending.

How different use cases affect your threshold setting

You should set verification score thresholds based on your email goal: 90+ for transactional messages, 85–90 for newsletters, 90+ for cold outreach, 80–85 for lead acquisition, and 80 for list cleanup. Lower thresholds capture volume but increase bounce risk; higher ones boost deliverability at the cost of list size. Real-world email behavior varies—some domains reject even valid addresses due to greylisting, role accounts, or policy filters, so context matters.

Transactional emails: Prioritize delivery, not volume

When sending order confirmations, password resets, or invoices, failed delivery is unacceptable. Use a 90+ threshold. These messages require inbox placement, and even one bounced email can harm sender reputation. The Return Path email deliverability report shows that messages sent to invalid addresses often trigger spam filters or trigger rate limits from ISPs like Gmail and Outlook.

Use the real-time verification API to pre-validate addresses during sign-up. It integrates with tools like HubSpot and SendGrid, ensuring only high-intent, valid emails enter your system.

Campaign-level thresholds: Align score with purpose

For newsletters, where engagement is key, a lower threshold can maintain list health. A score of 85–90 lets you reach more subscribers while excluding obviously fake or malformed addresses. But avoid low scores (<80) since they often include catch-all or disposable domains that rarely open emails.

Cold outreach requires extreme precision. A 90+ score filters out role accounts (like admin@ or sales@), disposable domains, and catch-alls—common traps that waste time, increase blocklist risk, and hurt sender reputation. Always validate before seeding your outreach pipeline.

Use Case	Recommended Threshold	Why This Threshold	Key Risks if Threshold is Too Low
Transactional emails	90+	Ensures delivery to active, valid inboxes	Bounce rate >1%, reputation damage
Newsletter campaigns	85–90	Balances volume with engagement quality	High spam complaints, low opens, blocked by providers
Cold outreach	90+	Filters out role, disposable, and catch-all addresses	Campaigns flagged as spam, sender blocked
Lead acquisition	80–85	Maximizes lead volume while removing obvious fakes	Lower conversion rates, higher bounce rate
List cleanup	80	Removes obvious invalids; follow up with higher thresholds for engagement	Retaining dead addresses harms long-term deliverability

A threshold isn’t static. Start with an 80 filter to clean your list. Then segment by score: 80–89 for follow-up, 90+ for high-priority campaigns. Use the inbox placement test to check deliverability before sending. Always verify results in real sender environments—what’s valid in test may not be in practice.

Using Email List Validation’s API to dynamically adjust thresholds

You can set custom verification score thresholds in real time using the Email List Validation API’s score field. This lets you route high-confidence emails to primary sends, medium-confidence ones to warm-up sequences, and lower-scoring addresses to suppression or re-engagement workflows. The score is a reliable indicator of inbox placement likelihood—use it to enforce data hygiene without manual filtering.

Set thresholds that match your deliverability goals

Fetch verification scores via the API—each email returns a score between 0 and 100. Higher scores mean stronger validity and inbox placement potential. Use this to map your list into tiers without pre-processing.
Define thresholds based on your risk profile—set 90 for high-priority sends, 85 for warm-up sequences, and 80 as a soft threshold for re-engagement. This avoids overloading your sender reputation with marginal addresses.
Automate routing with score-based logic—send emails scoring above 90 directly through your primary SMTP. Route 80–89 emails to a warming sequence. Flag anything below 80 for review or suppression. This reduces bounce rates and protects sender reputation.
Integrate with SendGrid or HubSpot—use the API to push scores into your ESP or CRM. Trigger workflows: deliver to high-score contacts immediately; delay or suppress lower-score ones. This scales hygiene across campaigns.
Monitor and adjust thresholds over time—track deliverability rates by score tier. If emails with scores above 85 land in spam more often, lower your threshold slightly. Adjust based on actual inbox placement, not assumptions.

Why real-time score thresholds matter

Every send counts. A single invalid email can trigger a blocklist alert, especially if sent in volume. According to Spamhaus, even one improperly delivered message can harm sender reputation in high-volume campaigns. Let your API do the filtering—stop trusting your list simply because it’s “clean.”

The 5 steps described in “Set thresholds that match your deliverability goals”, in order.

With Email List Validation’s API, you’re not just checking syntax; you’re assessing deliverability risk. The score reflects MX records, DNS, catch-all detection, and role account patterns—all in real time. This allows you to automate segmentation based on actual risk—not static rules.

For example, use the integration with SendGrid to send only those with scores above 90 to your launch blast. Use bulk verification to clean your database before campaign setup. The same rules apply after the send: monitor performance and refine thresholds based on what actually lands in inboxes. That’s how you get precision without guesswork.

Start with 100 free verifications at our pricing page, test thresholds on real data, and see what your list can really deliver.

How to monitor and refine threshold settings over time

Set your verification score thresholds based on past campaign results, then track hard bounces, soft bounces, and spam complaints monthly. Use inbox-placement tests to validate real delivery performance, and re-run list validations quarterly to catch expired or newly invalid addresses. Adjust thresholds only after confirming changes don’t harm deliverability or engagement.

Track performance across campaigns

Review hard bounce rates and soft bounce rates each month—spikes above 0.5% for hard bounces typically signal list quality issues.
Monitor spam complaint rates; even one complaint per 10,000 sends can trigger sender reputation penalties.
Compare results across campaigns: if deliverability drops after tightening thresholds, you may be excluding valid users.

Validate changes with real-world tests

After adjusting thresholds, run inbox-placement tests to measure actual inbox delivery rates across Gmail, Outlook, and other major providers.
Use the inbox-placement testing feature to simulate real sends and confirm whether your adjusted list still reaches inboxes.
Look closely at catch-all results—spikes after a threshold change may mean you’ve misclassified valid addresses as risky.
Re-run full list validations every quarter to detect new invalid or disposable emails that slipped through earlier checks.
Check for domain-wide changes: if a domain recently changed its email system, old verifications may no longer hold.

Let’s be clear: thresholds aren’t set in stone. What works at 10,000 contacts won’t always work at 100,000. Stay alert to shifts in data patterns. The same list that delivers well today may not a year from now, especially as domains change policies or inbox providers update filtering behavior.

For teams that use automation, integrate real-time verification API calls into signup flows to catch invalid addresses before they enter your system.

Consider using bulk email list cleaning to audit your entire database quarterly—and use the output to refine your score thresholds based on real delivery outcomes.

How Email List Validation compares on score accuracy and thresholds

You can set verification score thresholds confidently because Email List Validation delivers 98.9% accuracy through real-time SMTP checks and behavioral modeling—no fuzzy logic, no black-box scoring. Unlike tools that guess based on domain patterns or third-party data, we validate at the mail server level, and our verdicts (valid, invalid, catch-all, risky) come with clear, measurable thresholds you can test and trust.

Accuracy built on technical verification, not speculation

Most email validation tools rely on incomplete data—like outdated domain lists or heuristic rules—to predict validity. Email List Validation skips the guesswork. We perform actual SMTP-level communication with mail servers to check if an address is accepted, rejected, or deferred. This process aligns with industry standards like RFC 5321 and RFC 5322, which govern how email delivery works at the protocol level.

By modeling real-world delivery behavior—how servers respond to connection attempts, address validation, and transaction flow—we capture nuances that static datasets miss. For example, a catch-all domain might accept any address, but our system detects that pattern and flags it as risky. This depth is why our accuracy sits at 98.9%, meaning fewer false negatives (invalids marked as valid) and fewer false positives (valids marked as invalid).

Clear thresholds, no hidden logic

Some tools define a “high score” as a vague percentage or a proprietary rank. We don’t do that. Every verdict in our system is tied to specific, auditable thresholds:

Valid: Server accepts the address during SMTP handshake—confirmed delivery-ready.
Invalid: Server rejects the address outright, or it’s format-illegal (e.g., missing @).
Catch-all: Server accepts any address—common with outdated or poorly configured domains.
Risky: Address passes format, but delivery behavior is inconsistent (e.g., greylisting, rate limiting).

Item	Details
Valid	Server accepts the address during SMTP handshake—confirmed delivery-ready.
Invalid	Server rejects the address outright, or it’s format-illegal (e.g., missing @).
Catch-all	Server accepts any address—common with outdated or poorly configured domains.
Risky	Address passes format, but delivery behavior is inconsistent (e.g., greylisting, rate limiting).

The 4 items listed under “Clear thresholds, no hidden logic”, side by side.

These thresholds aren’t arbitrary. They’re grounded in real SMTP response codes and observed patterns across billions of deliveries.

Want to test how different thresholds impact your list? Try our bulk email list cleaning or real-time verification API with 100 free verifications—no risk, no commitment. You’ll see exactly how score thresholds shape your deliverability outcome.

Final takeaway: thresholds are a strategy, not a number

There is no universal verification score threshold that fits every sender. The right cutoff depends on your domain reputation, sending volume, and campaign type—your unique deliverability context.

Start with a conservative threshold like 90, monitor bounce rates, inbox placement, and engagement over time, then adjust based on real outcomes, not guesswork.

Use tools like Email List Validation to test your list health and validate how threshold changes affect your actual mail flow—before you send at scale.

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

What is a good verification score threshold?

A good starting threshold is 90. Adjust based on your sending context: 90 or higher for transactional, 85–90 for newsletters, and 90 for cold outreach.

Can I use a threshold below 80?

No. Below 80, the risk of catching disposable, role, or catch-all addresses increases sharply, harming deliverability and sender reputation.

What happens if I set my threshold too high?

You remove valid emails, especially newer or less common address formats. This shrinks your list and reduces engagement without improving deliverability.

How does Email List Validation’s accuracy affect threshold reliability?

With 98.9% accuracy, the score thresholds are highly reliable. You can trust the verification verdicts when setting cutoffs.

Should I change my threshold after a campaign fails?

Review your list health first. If bounces were high, re-check your threshold. But don’t lower it — improve list quality and resend.

Do threshold settings differ by email service provider?

No. Thresholds are list-based, not provider-based. However, your ESP’s filtering behavior may vary slightly depending on reputation.

Can I automate threshold-based email routing?

Yes. Email List Validation’s API supports score-based routing. Use thresholds to send high-scoring emails immediately, others to warm-up sequences.

What’s the impact of sending to catch-all addresses?

Catch-all addresses accept any email. Sending to them increases spam complaints and may trigger blacklists. Avoid them.

How often should I revalidate my list?

Quarterly is sufficient for most, but monthly for high-volume or high-risk campaigns. Use inbox-placement tests to confirm results.

How do I set different thresholds for different campaigns?

Use your automation tool — like HubSpot, SendGrid, or Klaviyo — to apply different verification thresholds to different segments.

Does Email List Validation work with Mailchimp and Klaviyo?

Yes. You can integrate Email List Validation with Mailchimp, Klaviyo, SendGrid, and HubSpot to clean lists and set thresholds automatically.

Do purchased credits expire?

No. Credit purchases never expire, so you can scale your verification operations at any time.