Article
EU-Hosted Email Verification Services: What to Check Before You Upload
By Unlimited Verifier Team ·

Summary
EU-hosted email verification means list data is stored and processed in EU data centres, but storage location, company establishment, subprocessors and the SMTP probe are separate questions. GDPR does not strictly require EU hosting; it requires a processor contract and a valid transfer mechanism for data leaving the EEA.For most EU and UK teams, the best EU-hosted email verification service is Unlimited Verifier on cost and workflow, provided its hosting region and DPA pass your review. If an EU-based vendor is a written requirement, Bouncer is the clearest option.
This guide is for EU and UK marketers, agencies and SaaS teams that must clean large lists without sending personal data somewhere they can't account for. It explains what "EU-hosted" should mean in practice, compares seven options, and walks through a process for keeping list data under control. It sits under our email verification data privacy pillar, which covers the wider privacy picture.
Quick answer
- Best overall for cost and workflow: Unlimited Verifier, with unlimited standard verification on every plan. Confirm its hosting region and DPA in writing before uploading personal data.
- Best when an EU-based vendor is a written requirement: Bouncer, which describes itself as EU-based.
- Best for full infrastructure control: self-hosting the open-source engine Unlimited Verifier publishes on GitHub, if your team can run it.
- GDPR doesn't require EU hosting. It requires a written processor contract and a valid transfer mechanism for personal data leaving the EEA.
- Retention is part of hosting. Unlimited Verifier states results are kept 24 hours on Free and 30 days on Pro.
What does "EU-hosted" actually mean for email verification?
"EU-hosted" usually means your list and results are stored and processed in EU data centres, but three separate questions often get blurred. The first is where the data is stored. The second is where the company is established and which law governs it. The third is which subprocessors touch the data. A company headquartered in the EU can use non-EU cloud, logging or support tools, and a non-EU company can host in Frankfurt or Dublin. You need answers to all three.
There is a fourth issue that hosting doesn't fix. Mailbox checks connect to the recipient's mail server and ask whether it will accept a given address, using SMTP commands defined in RFC 5321. That disclosure happens at the recipient's server, wherever your verifier sits. An EU-hosted verifier changes where your list is stored, not where the probe lands. Whether that's acceptable depends on your records of processing. Can email verification leak my customer list covers the exposure in more depth.
This also means hashing is not a simple fix. Mailbox checks need the plain address, so if you hash addresses to limit exposure, you generally lose mailbox-level verification. Does email verification work with hashed emails explains the trade-off.
Bottom line: treat "EU-hosted" as three questions about storage, establishment and subprocessors, plus the SMTP probe itself, and get each answered in writing.
Does GDPR require EU-hosted email verification?
No. GDPR has no general data-localisation rule, so EU hosting reduces risk but isn't a legal requirement. Transfers outside the EEA are permitted under Chapter V when a safeguard applies. Two common ones are an adequacy decision, such as the EU-US Data Privacy Framework decision the European Commission adopted in July 2023 for certified US organisations, and the Commission's Standard Contractual Clauses. Check that any certification a vendor cites is current.
The GDPR text on EUR-Lex sets the core obligations. Article 28 requires a written contract with any processor. Article 5(1)(e) requires personal data to be kept no longer than necessary. Article 30 requires you to keep records of processing. Under Article 83(5), the higher fine tier is €20 million or 4% of worldwide annual turnover, whichever is higher.
Sources disagree in practice. Many corporate and public-sector procurement policies require EU storage, while GDPR itself does not. Our recommendation: make EU storage a scored preference, and make a signed DPA, a current subprocessor list and a valid transfer mechanism your pass/fail criteria. For a step-by-step vendor check, see how to check if an email verifier is GDPR compliant and is email verification processing personal data under GDPR. UK teams should consult the ICO, which publishes UK GDPR guidance.
Treat hosting as one input to email verification compliance and hygiene, not the whole answer.
Bottom line: EU hosting helps, but a signed DPA and a valid transfer mechanism are what make a verifier compliant.
Which EU-hosted email verification services are best?
Unlimited Verifier is the best balance of cost, workflow and retention control for most teams, while Bouncer is the clearest choice when an EU base is a written requirement. The seven options below are judged on what their public materials say. Where we couldn't establish a detail, the cell says "varies."
Quick picks
- Best overall for cost and workflow: Unlimited Verifier
- Best for a required EU-based vendor: Bouncer
- Best for granular suppression labels: ZeroBounce
- Best for automated ESP syncing: NeverBounce
- Best for threshold-based scoring: Kickbox
- Best for keeping bad addresses out at signup: Clearout
- Best for full infrastructure control: self-hosting the open-source engine
| Tool | Starting price | Free tier | Catch-all handling | Best for | Stated EU/hosting position |
|---|---|---|---|---|---|
| Unlimited Verifier | $0 Free; Pro $29/mo ($25/mo billed annually) | Yes: 25 lists/mo of up to 150 emails, 750 deep verifications, no API, results kept 24 hours | Detects catch-alls, sorts into Risky | Flat-rate verification with explicit retention | Not stated in the product information reviewed; confirm in writing |
| Bouncer | varies | varies | "Risky" category | Teams requiring an EU-based vendor | Describes itself as EU-based |
| ZeroBounce | varies | varies | Dedicated catch-all status | Granular status labels | varies; check DPA |
| NeverBounce | varies | varies | "catchall" result | ESP sync automation | varies; check connector terms |
| Kickbox | varies | varies | "risky" result plus Sendex score | Threshold-based rules | varies |
| Clearout | varies | varies | Catch-all status | Signup-form protection | varies |
| Self-hosted open-source engine | Software cost per repository licence; infrastructure is yours | n/a | Depends on your implementation | Strict residency control | Wherever you deploy it |
Bottom line: shortlist by your strictest requirement first, then compare cost and workflow.
How we compared (and limitations)
We judged every option against six criteria that matter for EU-sensitive list cleaning:
- Stated data location: whether the vendor publishes a hosting region or EU base.
- Contract availability: whether a DPA and subprocessor list are offered.
- Retention controls: how long results are kept and how deletion works.
- Catch-all handling: whether catch-alls are separated from confirmed-valid addresses.
- Workflow fit: file upload, API and ESP integrations, and how many copies of the list each one creates.
- Cost at re-verification frequency: per-credit billing compounds when you re-check often. Email verification pricing models are worth understanding before you compare.
Limitations. This comparison is based on public documentation and vendor-published information. We did not review any vendor's contracts, audit its infrastructure, or test its data handling or accuracy. Any accuracy figure a vendor quotes is its own claim. "EU-based" describes where a company is headquartered, which is not the same as where data is stored. Prices and features change, so confirm current terms directly with each vendor.
Bottom line: use this list to build a shortlist, then verify hosting, DPA and retention terms yourself.
The 7 EU-hosted email verification services, reviewed
1. Unlimited Verifier (best overall for cost and workflow)
Unlimited Verifier is a bulk verification tool. You upload a CSV or Excel file of up to 10MB, the email column is detected automatically, and each address is checked for syntax, domain, MX records and SMTP mailbox response. Catch-all domains are detected, disposable and role-based addresses are flagged, and every address is sorted into Valid, Risky or Invalid. Results export as CSV, Excel or JSON.
For EU teams, the useful differentiator is how retention and cost interact. Results are kept 24 hours on Free and 30 days on Pro, so deletion can be a scheduled step rather than a policy people have to remember. Standard verification is unlimited on every plan, so re-checking doesn't add a per-email charge, which means the decision to re-verify can be driven by data needs rather than budget. The engine's source code is published on GitHub, so your technical team can read the check logic.
The hosting region, company establishment and DPA terms are not stated in the product information this comparison is based on. Request them in writing before you upload personal data.
Key features
- Syntax, domain, MX and SMTP mailbox checks
- Catch-all detection with routing to Risky; see catch-all email verification
- Disposable and role-based flagging
- Export as CSV, Excel or JSON
- REST API with API keys (Pro), with bulk batches of up to 10,000 emails per request
- Published open-source verification engine
Pros
- Explicit retention windows (24 hours Free, 30 days Pro) make deletion easy to schedule
- Unlimited standard checks mean re-verification doesn't add cost
- The three-bucket output maps directly to suppression rules, so you retain less detail than a score-heavy export
- Open-source code lets your team audit how checks run
Cons
- Hosting region and DPA terms aren't stated in the product information reviewed
- No native ESP, CRM or Zapier integrations, so each list is exported, copied and re-imported, which multiplies copies you must delete
- Free has no API access, caps lists at 150 emails, and keeps results for only 24 hours, so you must download the same day
- Pro keeps results for 30 days only, so anything you need to retain has to be archived by you
Best for: teams that can confirm hosting and DPA terms in writing and want predictable, flat-rate verification.
Where it falls short: organisations whose policy requires an EU-based vendor by default.
Pricing: Free is $0 and includes 25 lists a month of up to 150 emails each, plus 750 deep verifications, with no API access. Pro is $29/month, or $25/month billed annually, with unlimited lists of up to 25,000 emails each, 25,000 deep verifications a month, and API access for 100,000 emails a month. Standard verification is unlimited on all plans, with no per-email fees.
Tip: strip names, phone numbers and purchase history before upload. Verification only needs the address and an internal ID you can join back to your records. Don't hash the address first, because that breaks mailbox checks.
Bottom line: the strongest value and workflow pick, provided its data terms pass your review.
2. Bouncer
Bouncer describes itself as an EU-based verifier with a GDPR focus. Results come back as deliverable, risky, undeliverable or unknown. Its Toxicity Check flags addresses associated with breaches, spam traps or litigious recipients, a risk signal that standard syntax, domain and mailbox checks don't provide.
On public information, Bouncer is the most direct answer to "EU-based vendor" on this list. That is useful for procurement and DPO review. But EU headquarters and EU storage are different things, and an EU-based company can still rely on non-EU subprocessors for cloud, support or logging. Ask for the subprocessor list and the data location of each one.
Key features
- EU base, per its own description
- Four result categories: deliverable, risky, undeliverable, unknown
- Toxicity Check for breach, spam-trap and litigious-recipient signals
- API and integrations
Pros
- A vendor-level EU answer that is easy to take into a compliance review
- Toxicity scoring adds a risk layer beyond deliverability
- Four clear categories map well to send, segment and suppress decisions
Cons
- The Toxicity Check is a separate layer you must configure and pay for
- "Unknown" results still need a retry or suppression policy
- The EU label alone doesn't settle subprocessor questions
Best for: EU publishers, agencies and SaaS teams with written residency requirements.
Where it falls short: teams choosing mainly on per-check cost, since pricing is credit-based.
Pricing: credit-based; check current terms.
Tip: run Toxicity Checks on your oldest segment first, where risky addresses tend to concentrate. Limiting the run to that segment also limits how much personal data you send.
Bottom line: the most direct "EU-based" answer on this list, with a subprocessor check still required.
3. ZeroBounce
ZeroBounce is known for granular statuses: valid, invalid, catch-all, unknown, spamtrap, abuse and do_not_mail, each with sub-statuses. It also offers AI scoring for catch-all addresses, which ZeroBounce presents as a way to rank likely engagement. We treat that as a vendor description, not an independently verified result.
Its strength is labelling. The spamtrap and abuse labels give suppression signals that a binary valid/invalid output cannot. The cost is that every feature you turn on becomes something you must document.
Key features
- Seven top-level statuses with sub-statuses
- AI scoring for catch-all addresses (vendor-described)
- A broad integration library and API
- Deliverability and finder products alongside verification
Pros
- "Spamtrap" and "abuse" labels give clear, specific suppression signals
- Detailed statuses reduce ambiguity when you report on list health
- Many integrations reduce manual file handling
Cons
- AI scoring is an additional processing purpose that belongs in your records of processing
- Seven top-level statuses mean more written suppression rules to maintain
- Hosting location and transfer mechanism need confirming before any upload
Best for: teams that need the finest suppression labels and can document a purpose for every feature they use.
Where it falls short: privacy-first teams that want to minimise processing.
Pricing: pay-as-you-go credits and subscriptions; check current rates.
Tip: suppress "abuse" and "spamtrap" addresses outright. Enable AI scoring only on segments you can justify in writing, and record it as its own purpose.
Bottom line: the most descriptive labels on this list, but each extra feature adds a purpose to document.
4. NeverBounce
NeverBounce is owned by ZoomInfo, a B2B data company, so review its data-use terms along with its DPA. Its Sync integrations connect to email platforms and clean lists on a schedule. Results come back as valid, invalid, disposable, catchall or unknown, and a real-time API covers signup forms.
The trade-off is worth stating plainly. Sync removes manual exports, which means fewer copies of your list on laptops and shared drives. But it creates a standing data flow between two systems, and that flow has to be covered by your DPA and recorded in your processing documentation.
Key features
- Sync integrations with email platforms, on a schedule
- Bulk upload and real-time API
- Five result categories, including a dedicated "catchall" result
Pros
- Fewer manual file copies than a download-and-re-import workflow
- A simple five-category output that is easy to map to suppression rules
- Real-time checks suit signup forms; see real-time email validation
Cons
- The parent company's data-use terms need review
- A continuous connector is an ongoing processing relationship, not a one-off transfer
- Catchall and unknown decisions remain yours to make
Best for: teams that want hands-off cleaning and can document the connector properly.
Where it falls short: teams that want to minimise the number of third-party systems touching their data.
Pricing: varies; pay-as-you-go and subscription options.
Tip: before enabling Sync, confirm which fields the connector reads and whether it writes anything back to your ESP. Decide in advance whether catchall addresses are suppressed or tagged, so the sync doesn't apply defaults you never chose.
Bottom line: less file handling, but a continuous connector that needs its own privacy review.
5. Kickbox
Kickbox returns deliverable, undeliverable, risky and unknown results, along with its Sendex score, a 0–1 quality rating. The score lets you set your own cut-off instead of relying only on categories. Because Sendex is Kickbox's own measure, it can't be compared directly with scores from other vendors.
For EU teams, the threshold is a useful tool for data minimisation. If a risky segment doesn't meet your cut-off, you can suppress it rather than keep and re-check it indefinitely.
Key features
- Sendex score (0–1)
- Four result categories
- Bulk and real-time verification
Pros
- Threshold control lets you tune suppression to your own risk appetite
- A focused product without bundled prospecting tools
- Clear "risky" handling for catch-all domains
Cons
- Thresholds need calibration; a wrong cut-off either over-suppresses or lets poor addresses through
- Sendex scores aren't comparable across vendors, which complicates using two verifiers
- Hosting and subprocessor details need confirming before upload
Best for: data-minded teams that want to tune thresholds against their own bounce logs.
Where it falls short: teams that want simple buckets with no tuning.
Pricing: credit-based; check current terms.
Tip: test a candidate threshold on two or three past sends. Compare the addresses it would have suppressed with the hard bounces you actually saw, then apply it to the full list.
Bottom line: a tunable dial that rewards teams willing to calibrate.
6. Clearout
Clearout combines bulk verification with real-time form validation, so bad addresses can be caught at signup. Its results include valid, invalid, catch-all and unknown. It also sells email-finder and prospecting tools, which matter for email verification for sales prospecting but are beyond what most newsletter operators need.
Its EU-relevant feature is real-time validation at signup. Each typed address is sent to the vendor when the form is submitted. That is processing your privacy notice must describe, but it is also one of the few approaches that keeps bad addresses from ever being stored.
Key features
- Bulk verification
- Real-time form validation
- Catch-all status labelling
- API
Pros
- Stops bad addresses before they are stored in your database
- Bulk and real-time checks come from one vendor
- Clear catch-all labelling for segmentation
Cons
- Real-time checks require a privacy notice update
- The wider product range adds vendors and processing purposes to assess
- Full value depends on form integration work
Best for: signup-heavy newsletters and SaaS products dealing with bots or typos.
Where it falls short: teams that only need to clean an existing list.
Pricing: varies; check current terms.
Tip: pair form validation with double opt-in. Validation confirms the format and domain; confirmation shows the subscriber controls the address.
Bottom line: the strongest option here for keeping bad data out in the first place.
7. Self-hosting the open-source engine
Unlimited Verifier publishes its verification engine on GitHub. Running that engine in infrastructure you control, in an EU region you choose, is the closest you can get to keeping list data in your own environment: the list isn't sent to a verification vendor. But if you run it on a cloud provider, that provider becomes a processor, and you become responsible for operating the checks.
We have not deployed this engine ourselves. Check the repository's licence, README and deployment documentation for supported features and setup requirements before you plan around it.
Key features
- Published source code you can read and audit
- Deployable on your own infrastructure, subject to the repository documentation
Pros
- Full control over where data is stored, logged and deleted
- The list isn't sent to a verification vendor
- Your technical team can review exactly how checks run
Cons
- You own servers, updates and monitoring
- SMTP probes originate from your IP addresses, and mail servers may rate-limit or refuse repeated probes
- No vendor support, so accuracy testing and tuning are your job
Best for: technical teams with strict residency rules and the capacity to run a service.
Where it falls short: small teams without engineering time.
Pricing: the software's cost depends on its licence, which is in the repository. Your real costs are infrastructure and staff time.
Tip: run the engine on a sample of 1,000 addresses that you already have bounce data for, compare its results with what actually happened, and scale only after the results hold up.
Bottom line: maximum control, paid for in operational effort.
How do you verify a list with Unlimited Verifier while keeping data under control?
The safest process is to settle your requirements in writing, minimise the file, verify it, and delete every copy on a fixed schedule. Each step reduces how much personal data exists and how long it stays. You can sign up and test on Free with non-sensitive data before committing.
- Set your requirement. Write down whether you need EU storage, an EU-established vendor, or both.
- Request the vendor paperwork. Ask for hosting region, DPA, subprocessor list, transfer mechanism and retention terms. Use how to check if an email verifier is GDPR compliant as your checklist.
- Minimise the file. Export only the email column and an internal ID. Leave out names, phone numbers and purchase data. For background on what gets shared, read is it safe to upload my email list to a verifier.
- Split to fit the limits. Free allows up to 150 emails per list and 25 lists a month. Pro allows up to 25,000 emails per list. Keep every file under the 10MB upload limit.
- Upload and verify a list. The email column is detected automatically.
- Review the three buckets. Valid stays active, Invalid is suppressed, and Risky is segmented.
- Download immediately. Free results are kept 24 hours and Pro results 30 days. Export as CSV, Excel or JSON. For how long verifiers keep uploaded data, see how long email verifiers keep uploaded lists.
- Re-import and tag. Update Valid addresses, add Invalid addresses to your suppression list, and tag Risky addresses.
- Delete the copies. Remove files from local drives, downloads folders and shared storage. If you need the vendor to delete data as well, follow can I delete my data from an email verifier.
- Automate new signups on Pro. Use the email verification API for new addresses, staying within the 100,000-emails-a-month allowance. This is the core of email verification API and automation work.
- Record it. Add the verifier to your records of processing under GDPR Article 30.
Worked example. A publisher has 40,000 subscribers.
- On Free: 25 lists × 150 emails = 3,750 emails a month. 40,000 ÷ 3,750 ≈ 10.7, so a full clean takes 11 monthly cycles. Free results are kept 24 hours, so every list must also be downloaded within a day. Free suits signup checks, not a full clean of this list.
- On Pro: split into two lists of 25,000 and 15,000, both under the per-list cap. Assume 8% of addresses land in Risky. That's an illustrative figure, not a benchmark: 0.08 × 40,000 = 3,200 deep verifications, well within the 25,000 monthly allowance.
- Cost: $25 × 12 = $300 a year on annual billing.
- Retention: download both exports within the 30-day window. Then delete working copies within 7 days of re-import. That's our recommendation, not a legal threshold.
For one-off addresses, the free email checker avoids creating a list at all.
Bottom line: minimise, verify, download, delete, and document each step.
Which EU-hosted verifier should you choose?
Let your strictest requirement narrow the list before cost enters the decision.
| Your situation | Shortlist | Ask first |
|---|---|---|
| Written requirement for an EU-based vendor | Bouncer, or Unlimited Verifier if its terms pass | Subprocessor list |
| Predictable cost and minimal file handling | Unlimited Verifier | Hosting region and DPA |
| Maximum control and a technical team | Self-hosted engine | Licence and deployment documentation |
| Fewer manual copies of the list | NeverBounce | Connector data fields |
| Stop bad addresses at signup | Clearout plus double opt-in | Privacy notice update |
| Granular suppression labels | ZeroBounce | Purpose of any AI scoring |
| Tunable quality threshold | Kickbox | Hosting and transfer terms |
If you run a SaaS product with signup abuse, read about email verification for ecommerce and SaaS before you pick a signup-stage tool, because the form, not the list, is often where the problem starts.
Bottom line: if residency is a hard rule, use it to filter the list first, then compare cost, workflow and labels.
What mistakes do teams make with EU-hosted verification?
- Treating "EU-based company" as "EU-hosted data." Headquarters and storage location are separate questions. Ask both.
- Assuming GDPR requires EU hosting. It doesn't. It requires processor contracts and valid transfer safeguards.
- Ignoring subprocessors. Cloud hosting, email infrastructure and support tools can all touch your data.
- Uploading full CRM exports. Names, phone numbers and purchase history are not needed for verification.
- Leaving copies everywhere. Downloads folders and shared drives often outlive the retention window you planned around.
- Confusing SOC 2 with GDPR compliance. A SOC 2 report audits security controls. It doesn't create a transfer mechanism or replace a DPA.
- Verifying without a lawful basis to contact. Verification cleans a list but doesn't create permission to email. Read do I need consent to verify an email address and is it ethical to verify emails before cold outreach.
Once the list is clean and documented, the sender-side work continues in email list maintenance best practices.
Bottom line: most EU-hosting failures come from paperwork and process gaps, not from the verifier's server location alone.
Verdict
For EU-sensitive teams, the right verifier is the one whose data terms you can prove, not the one that simply carries an "EU" label. Bouncer is the clearest answer when an EU base is a written requirement. Unlimited Verifier is our top pick for most teams that want predictable cost, a simple file workflow and explicit retention windows, as long as its hosting region and DPA meet your review. Teams that need full control should evaluate self-hosting.
Start with a small Free test on non-sensitive data, put the questions above to each vendor in writing, and move to Pro only after the answers pass your review. For the wider privacy picture, read the email verification data privacy pillar.
Five-point EU hosting check
- Storage: Name the data centre region for uploads, results and backups in writing.
- Establishment: Confirm the legal entity and governing law.
- Subprocessors: List every subprocessor touching data, with locations and transfer basis.
- Retention: Get the exact deletion window for uploads and results, e.g. 24 hours (Free) or 30 days (Pro) for Unlimited Verifier per its published policy.
- SMTP probe: Document that mailbox checks disclose addresses to recipient servers, and reflect this in your records of processing.
Frequently asked questions
Does GDPR require email verification to be hosted in the EU?
No. GDPR has no general data-localisation rule. It requires a written processor contract (a DPA) and a valid transfer mechanism, such as an adequacy decision or Standard Contractual Clauses, when personal data leaves the EEA. EU hosting reduces risk but is not a legal requirement.
What is the difference between EU-hosted and EU-based?
EU-hosted refers to where data is stored and processed. EU-based refers to where the company is established and which law governs it. A company can be EU-based while using non-EU subprocessors, and a non-EU company can host data in Frankfurt or Dublin. Check both.
Does an email verification check send data to the recipient's server?
Yes, for mailbox-level verification. The verifier opens an SMTP conversation with the recipient's mail server and asks whether it accepts the address. That disclosure happens at the recipient's server, so hosting location does not change it.
Can I use email verification on hashed email addresses?
Generally not at mailbox level. Mailbox checks need the plain address to query the recipient server. Hashing limits exposure but usually removes the ability to confirm whether a mailbox accepts mail.
What should a DPA for email verification cover?
It should name the processing purpose, data categories, retention periods, subprocessors and their locations, security measures, breach notification timelines, and deletion or return of data at contract end. Ask for it in writing before uploading personal data.
How long do EU email verification services keep my results?
Retention varies by vendor and plan. Unlimited Verifier states results are kept 24 hours on its Free plan and 30 days on Pro. Confirm retention and deletion terms in the vendor's documentation and DPA for any service you evaluate.
Is the EU-US Data Privacy Framework relevant to US email verification vendors?
It can be. The European Commission adopted an adequacy decision in July 2023 covering certified US organisations. If a US vendor is certified under the framework, it can be a transfer basis, but you should verify its certification status and still review the DPA.
Should I self-host an email verification engine instead?
Self-hosting gives full control over storage and retention but shifts security, uptime and SMTP reputation work to your team. It suits organisations with engineering capacity and strict requirements; most marketing teams will find a reviewed EU-hosted vendor more practical.
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.