Article
Email Verification Cost vs the Cost of a Burned Domain: A Break-Even Guide
By Unlimited Verifier Team ·

Summary
Email verification is usually far cheaper than a burned sending domain, which can cost lost inbox placement, disrupted transactional mail and weeks of recovery. Verify when the chance of a burn multiplied by its cost exceeds your verification bill. This guide shows the break-even math and the bounce and complaint thresholds to protect.Verification is far cheaper than a burned domain. On Unlimited Verifier's Pro plan, a deep check works out to about $0.00116 per address at full allowance, while a single burn can cost thousands of dollars in lost revenue and recovery time. Verification pays off whenever the chance of a burn multiplied by its cost is larger than your verification bill. In the worked example below, that break-even point is a 0.44% chance of a burn in a given period.
This guide works through the numbers, the thresholds to protect, and a step-by-step method for deciding how much verification your list needs. For the broader cost picture, start with our pillar guide on email verification cost.
Quick answer
- A burned domain costs far more than the domain. The domain name is a small line item. Lost inbox placement, delayed transactional mail and weeks of recovery make up most of the bill.
- Break-even is simple arithmetic. Verify when (probability of a burn) × (cost of a burn) is larger than your verification bill. In the example, that break-even is about 0.44% in a given period.
- Spend deep checks where they matter. Standard verification is unlimited on every plan, including Free. Reserve Pro's 25,000 monthly deep verifications for legacy imports and Risky results.
- Protect two thresholds. Keep bounces under 2% and complaints under 0.10%. Public sources differ on complaint limits, so 0.10% is the stricter figure to plan around.
- Prune before you pay. Remove contacts you will never mail before verifying, so your deep-check allowance covers addresses that matter.
What counts as a burned domain, and how long does recovery take?
A burned domain is a sending domain or IP whose reputation has fallen far enough that mailbox providers filter its mail to spam, a blocklist lists it, or your ESP pauses sending. Recovery usually takes weeks, because reputation is built over time from engagement and complaint signals rather than reset by a support ticket.
Two details change the cost. First, if you send through an ESP's shared infrastructure, a problem caused by another customer can still reach you. Second, switching to a new domain is not a clean escape. A new sending domain has no history, so it needs warm-up and full SPF, DKIM and DMARC setup before it can send at volume.
The cost is spread across several line items, and most of them never appear on an invoice:
| Cost component | How it shows up | Why it is easy to miss |
|---|---|---|
| Lost inbox placement | Fewer opens, clicks and orders from campaigns | Hidden inside normal revenue swings |
| Transactional disruption | Password resets, receipts and invoices delayed or lost | Shows up as support tickets, not email reports |
| Replacement infrastructure | New sending domain or subdomain, plus authentication setup | The direct cost is small; the setup hours are not |
| Warm-up | Low send volumes while providers learn the new sender | Reduces reach for weeks |
| ESP suspension and appeal | Paused sends and staff time spent on review | Often absorbed by existing staff |
| Compliance exposure | Complaints, regulator scrutiny and penalties for mailing without consent | Depends on your jurisdiction and consent records |
Google's bulk sender guidance says to keep spam complaint rates below 0.10% and warns against rates of 0.30% or higher. Yahoo's sender requirements use 0.3% as their line. Those figures matter because a list full of people who never asked for your mail is one of the most common routes to a burn. Our guide to the cost of not verifying your email list walks through how those complaints build up.
Bottom line: Count lost revenue, setup hours and disrupted transactional mail. The domain itself is the smallest line item.
How much does email verification cost per address?
Compare verification pricing as cost per 1,000 addresses, including re-checks and expiry rules. The sticker price of a single pass rarely shows what you will pay over a year.
| Pricing model | Cost per 1,000 addresses | What re-checks cost | Watch-out |
|---|---|---|---|
| Pay-per-credit packs | Varies by vendor and pack size; compare the effective price after bonus credits | Each re-check uses another credit | Some sellers expire unused credits. Read the terms (what happens to unused credits) |
| Subscription with a deep-check cap (Unlimited Verifier Pro) | $29/month, or about $1.16 per 1,000 deep checks at the full 25,000 allowance | Standard re-checks are unlimited; deep re-checks draw on the monthly allowance | The 25,000 deep-check cap is the real constraint on large lists |
| Free tier (Unlimited Verifier Free) | $0 | 25 lists of up to 150 emails a month (3,750 emails), plus 750 deep verifications | Results are kept for 24 hours, so export them the same day |
| Self-hosted open-source engine | Server and engineering time, not a per-address fee | You run every check yourself | SMTP checks come from your own infrastructure, so you own any throttling by mailbox providers |
Unlimited Verifier's standard verification is included on every plan with no per-email fees. Its Pro plan is $29 a month, or $25 a month billed annually, and includes unlimited lists of up to 25,000 emails each, 25,000 deep verifications a month, API access for 100,000 emails a month, and results kept for 30 days. Every upload is sorted into Valid, Risky and Invalid, catch-all domains are detected, and disposable and role-based addresses are flagged. The company states 99.5% accuracy for deep verification. That is Unlimited Verifier's own figure, not an independent benchmark. For what "unlimited" does and does not cover, read what unlimited really means in email verification.
Teams that need checks at signup often rely on an email verification API and automation workflow. Compare that cost model with bulk uploads in API pricing vs bulk upload pricing. For a year-by-year view of what providers charge, see how much email verification costs in 2026. For the underlying models, our overview of email verification pricing is a useful reference.
Before you buy credits anywhere, check whether unknown or unverifiable results are billed. Do email verifiers charge for unknown results? covers the terms to read.
Bottom line: Compare cost per 1,000 addresses across re-checks, not the price of one pass. Deep-check allowance and expiry rules often matter more than the headline fee.
Where is the break-even point?
The break-even point is the chance of a burn at which verification pays for itself. The formula is:
Expected burn cost = probability of a burn in the period × cost of a burn
Verify when the verification bill is smaller than the expected burn cost it prevents.
Rearranged, the break-even probability is verification bill ÷ cost of a burn. Replace the inputs below with your own data. The numbers are illustrative.
Worked example 1: a program sending 400,000 emails a month
Assumptions:
- 400,000 sends a month at $40 of email-attributed revenue per 1,000 sends = $16,000 a month
- A burn that cuts inbox placement by 30% for three weeks (0.75 months)
- 40 staff hours at $75 an hour to set up a new domain, handle the appeal and monitor warm-up
Burn cost:
- Lost revenue: $16,000 × 30% × 0.75 = $3,600
- Staff time: 40 × $75 = $3,000
- Total: $6,600
Verification cost:
- Pro plan: $29
- Staff time for export, verification and re-import, assumed at 4 hours: 4 × $75 = $300
Break-even probability, plan fee only:
$29 ÷ $6,600 = 0.44%
Including staff time:
($29 + $300) ÷ $6,600 = about 5.0%
Even at the higher figure, the bar is low for a list that has never been cleaned. The estimate also leaves out ESP suspension risk and any compliance penalties, which would move the break-even point lower. The does verifying emails lower your ESP bill guide covers the related cost savings on the sending side.
Does verification still pay off on a small list?
Usually, yes, but for a different reason. A small list has a smaller burn cost because it earns less revenue. However, Free covers up to 3,750 emails a month across 25 lists, plus 750 deep checks, so the plan fee can be zero. Your remaining cost is staff time, and that is the figure to keep small.
Bottom line: Verification pays for itself at a fraction of a percent chance of a burn. Teams that skip it often haven't priced the burn.
How do you verify a 180,000-contact list on Pro, and what does it cost?
Here is the arithmetic on a realistic list, respecting Pro's limits.
Step 1: Split the file. Pro accepts lists of up to 25,000 emails each.
180,000 ÷ 25,000 = 7.2, so 8 files: seven of 25,000 and one of 5,000.
Step 2: Run standard verification on all 180,000. Standard checks are unlimited on Pro, so the cost is the plan fee only.
Step 3: Deep-check the risky segment. Suppose your history shows that 22,000 addresses come from legacy imports or were flagged Risky on the standard pass. Deep-check those 22,000.
25,000 − 22,000 = 3,000 deep verifications left for re-checks after fixes
Step 4: Allocate the cost. At the full-allowance rate, the deep portion equals:
22,000 × ($29 ÷ 25,000) = $25.52 of the plan fee
Step 5: Act on the results. Re-import Valid contacts, suppress Invalid ones and hold Risky addresses back.
Total outlay: $29 plus about four staff hours. Against the $6,600 burn in the first example, that is a small fraction of the exposure.
Bottom line: A full 180,000-contact cleanup, including its deep-check segment, fits in one Pro month. The constraint to watch is the monthly deep-check allowance, not the fee.
How do you verify 500,000 contacts without overspending?
For large lists, the binding constraint is usually the deep-check allowance, because 25,000 deep checks a month can run out before your list does.
Worked example 2: a 500,000-contact list
Starting point:
- 500,000 ÷ 25,000 = 20 files. Standard verification covers all of them.
- Suppose 40,000 addresses need deep checks (legacy imports and Risky results).
Without pruning:
- 40,000 is above the 25,000 monthly cap, so split the work across two months.
- Month 1: 25,000 deep checks. Month 2: 15,000 deep checks.
- Cost: 2 × $29 = $58, plus two re-import waves.
With pruning first:
- Suppose 180,000 contacts have not opened or clicked in 24 months, and you have decided you won't mail them again. Suppress them before verification. Remaining: 500,000 − 180,000 = 320,000 active contacts.
- Suppose 18,000 of the 40,000 deep-check addresses fall within that dormant group. Remaining deep-check segment: 40,000 − 18,000 = 22,000, which fits in one month's 25,000 allowance.
- Standard pass on 320,000: 320,000 ÷ 25,000 = 12.8, so 13 files (twelve of 25,000 and one of 20,000).
- Cost: $29 for one month.
Suppression is not deletion. If you need the history for consent or compliance purposes, keep the dormant contacts in a separate file marked "do not mail" rather than erasing them.
Two rules follow from this:
- Prune first, verify second. Don't spend deep checks on addresses you won't send to.
- Plan around the monthly cap. Schedule large deep-check jobs across months so you don't hit the limit mid-project.
For a broader cost comparison at this size, see how much it costs to verify 500,000 emails.
Bottom line: Pruning turned a two-month deep-check job into one month and cut the bill from $58 to $29 in this example.
Which verification plan fits your list size?
Choose by list size, sending volume and how often you re-check.
- Lists of up to 150 addresses, occasional use: The Free plan covers it, with 25 lists a month and 750 deep verifications. Free results are kept for only 24 hours.
- Lists of up to 25,000 addresses, regular cleans: Pro at $29 a month covers unlimited lists of that size, with 25,000 deep verifications and 30-day result retention. If budget is the main constraint, our guide to the best value email verifier under $30 a month compares the options at this price point.
- Agencies or multi-client databases: Plan deep-check allowance per client and per month. Our guide to email verification pricing for agencies with many clients covers the allocation.
- Ecommerce and SaaS databases: These change fastest, especially B2B addresses that churn with job changes. See email verification for ecommerce and SaaS.
- Real-time checks at signup or checkout: Use the email verification API, which accepts single-email checks and batches of up to 10,000 emails per request.
If you're comparing vendors more broadly, read the best email verification tools and how to choose an email verifier. Differentiators to check include how results are categorised, whether catch-all domains are flagged separately, and how deep and standard checks are metered.
Bottom line: Match the plan to your list size and re-check frequency, not to the lowest headline price.
How do you decide whether verification is worth it? (a 6-step framework)
Use this sequence to turn the break-even logic into action.
- Estimate monthly sends and revenue per 1,000 sends. Use your own analytics. Replace the $40 figure in this article if it doesn't match.
- Estimate the burn probability. Start from your bounce and complaint history. If you lack data, be conservative and assume a meaningful chance.
- Calculate the expected burn cost. Multiply probability by the cost of a burn, including lost revenue and staff time.
- Compare with the verification bill. Include the plan fee, deep-check spend and staff hours.
- Prune, segment and verify. Remove contacts you won't mail, split the rest by risk, and deep-check the riskiest segment first.
- Re-verify on a schedule. Lists decay, so repeat the process monthly or quarterly. For the routine, see email list maintenance best practices, and check new sign-ups at the point of entry with real-time email validation.
Bottom line: The framework takes an afternoon to set up, then runs on a schedule.
What bounce and complaint thresholds should you protect?
Sources disagree on exact thresholds, so choose a conservative target and hold it.
- Bounces: AWS's Amazon SES documentation describes a 5% bounce rate as the point where accounts go under review, with pausing possible at 10%. Other platforms may act at lower rates. Recommendation: keep total bounces under 2%, and aim for under 1% on any single send.
- Complaints: Google's guidance says to keep spam rates below 0.10% and avoid 0.30% or higher. Yahoo's requirements use 0.3% as their line. Recommendation: target 0.10%, the stricter figure, which leaves a margin.
- Hard bounces: RFC 3463 defines enhanced status codes. The first digit separates temporary failures (4.x.x) from permanent failures (5.x.x). Permanent failures should be suppressed, not retried.
Bottom line: Target 2% bounces and 0.10% complaints. The stricter numbers protect you wherever the sources disagree.
What mistakes make verification look more expensive than it is?
- Comparing only the first pass. A cheap first run can become expensive once you pay for re-checks. Compare the second and third verification too.
- Deep-checking addresses you will suppress anyway. Dormant contacts consume allowance for no benefit. Prune first.
- Re-deep-checking addresses you already verified. Pro keeps results for 30 days and Free for 24 hours. Export every result file so you don't pay allowance twice for the same address.
- Treating Risky as Valid to save money. Catch-all domains accept every address, so a result there cannot confirm a mailbox. Hold these back, or test with a small send. The catch-all email verification page explains how these results are handled.
- Sending marketing and transactional mail from one domain. A marketing reputation problem can then block password resets. Separate subdomains limit the damage.
- Ignoring staff time. Hours spent on exports, re-imports and appeals are real costs, and they belong on both sides of the calculation.
- Assuming verification proves consent. A valid mailbox is not an opted-in one. Verification reduces bounces; it does not replace consent records. The email verification compliance and hygiene guide covers the division of responsibility, and the US FTC's CAN-SPAM guide sets out what senders must keep.
Bottom line: Most "expensive verification" problems come from comparing the wrong numbers, not from the price of checking an address.
How do you run a verification job on Unlimited Verifier?
- Export your contacts as a CSV. Include the email column and engagement fields such as last open date or signup date.
- Prune first. Remove contacts you will never mail again and save them to a separate file.
- Create an account. Sign up for free. Run a 150-row sample first to check your columns and results. The Free plan accepts lists of up to 150 emails.
- Upload your file. Go to upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. On Pro, split files at 25,000 rows.
- Run standard verification on everything. Each address is checked for syntax, domain, MX records and the SMTP mailbox. Catch-all, disposable and role-based addresses are flagged.
- Deep-check the risky segment. Upload legacy imports and Risky results as their own file, and run deep verification on that file only. Check your remaining monthly allowance before you start.
- Read the three buckets. Valid addresses are ready to send. Invalid addresses should be suppressed. Risky addresses are held back until your main sends are stable.
- Export and save the counts. Download the results as CSV, Excel or JSON, and keep the summary numbers for your records.
- Re-import Valid contacts and suppress Invalid ones. Unlimited Verifier has no native ESP, CRM or Zapier integration, so this is a manual export and re-import, or a call to the API from your own scripts.
To spot-check a single high-value address before a campaign, use the free email checker.
Bottom line: Prune, verify, deep-check the risky segment, export, and re-import only Valid contacts.
How we compared (and limitations)
This article draws on public documentation: AWS's Amazon SES documentation, Google and Yahoo's sender guidance, RFC 3463 and the FTC's CAN-SPAM guide. We have not tested verification tools against mailbox providers or ESP review teams, and we have not run experiments on domain recovery times.
The worked examples use illustrative inputs that you should replace with your own: $40 of revenue per 1,000 sends, a 30% placement loss, a three-week recovery window, a $75 staff rate and four hours of verification work. Real recovery times vary widely with sender reputation, list quality and provider.
Unlimited Verifier figures come from its published plan facts. The 99.5% deep-verification accuracy is the company's own stated figure, not an independent benchmark. Other vendors change pricing often, so compare cost per 1,000 addresses on current pricing pages before you decide.
Bottom line: Use the framework with your own numbers, and check the inputs against your sending data before you commit budget.
Break-even steps
- Estimate your verification bill for the period (list size x per-address cost).
- Estimate the cost of a burn: lost revenue, recovery hours, replacement infrastructure, warm-up reach loss.
- Estimate the probability of a burn in that period using your historical complaint and bounce trends.
- Multiply step 2 by step 3.
- If the result exceeds the step 1 bill, verify the list before sending.
- Re-run the calculation each quarter as list quality and volume change.
Frequently asked questions
How much does email verification cost per address?
Per-address cost depends on your plan and check depth. Standard verification is unlimited on every plan, while deep checks have monthly allowances. Compare the bill for your list size against your expected cost of a burn to see whether the spend is justified.
What is a burned domain?
A burned domain is a sending domain or IP whose reputation has dropped so far that mailbox providers filter its mail to spam, a blocklist lists it, or your provider pauses sending. Recovery typically takes weeks because reputation builds over time from engagement and complaint signals.
Is it cheaper to buy a new domain than to verify emails?
Usually not. A new sending domain has no history, so it needs warm-up and full SPF, DKIM and DMARC setup before it can send at volume. The domain fee is small compared with the lost reach and setup hours that follow a burn.
What bounce rate is safe for email campaigns?
Most senders aim to keep hard bounces under 2 percent. Higher bounce rates signal poor list quality to mailbox providers and can hurt sender reputation. Verifying before sending is one of the most direct ways to keep bounces low.
What spam complaint rate should I stay under?
Google's bulk sender guidance says to keep spam complaint rates below 0.10 percent and warns against rates of 0.30 percent or higher. Public sources differ on exact limits, so planning to 0.10 percent gives a safer margin.
When is email verification not worth it?
Verification may be hard to justify for very small lists with low send frequency and strong consent records, where the expected cost of a burn is low. Even then, verifying before a large import or a re-engagement campaign is often worthwhile.
Should I deep check my whole list?
Not always. Standard verification can cover most addresses, while deep checks are best reserved for legacy imports, risky results and high-value segments. Pruning contacts you will never mail first keeps deep-check allowances focused on addresses that matter.
How do I calculate break-even for verification?
Multiply the estimated probability of a burn in a period by the estimated cost of that burn. If the result is larger than your verification bill for the same period, verification pays for itself. Use conservative estimates for both inputs.
Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification
Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.
Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.
| Free | Pro | |
|---|---|---|
| Price | $0 | $29/month ($25/month billed annually) |
| Lists | 25 a month, up to 150 emails each | Unlimited, up to 25,000 emails each |
| Deep verifications | 750 a month | 25,000 a month |
| API access | No | Yes (100,000 emails a month) |
| Result retention | 24 hours | 30 days |
Why teams choose Unlimited Verifier
- Unlimited standard verification on all plans, including Free, with no per-email fees.
- Catch-all detection so you know which domains accept every address.
- Clear Valid / Risky / Invalid results, exportable as CSV, Excel or JSON.
- An open-source verification engine you can inspect on GitHub.
Unlimited Verifier states 99.5% accuracy for deep verification.
Create a free account and verify your next list before you hit send.
Want to test a single address first? Try the free email checker.