Article
Where Are Email Verification Servers Located? A Guide to Processing Regions
By Unlimited Verifier Team ·

Summary
Email verification servers run wherever the vendor deploys its infrastructure, commonly in US or EU public cloud regions, so there is no single answer. The processing region named in a vendor's DPA and sub-processor list shows where your file is actually read, not just where the company is headquartered.Email verification servers run wherever the vendor deploys its infrastructure, commonly in public cloud regions in the United States or the European Union, so there is no single answer for the whole category. A vendor's headquarters does not settle the question. The processing region named in its data processing agreement (DPA) and sub-processor list shows where your file is actually read.
Quick answer
- Location means where your file is processed, which can differ from the vendor's headquarters or support staff. Check the processing region, not just the company's home country.
- Ask for three documents: the privacy policy, the DPA and the sub-processor list. Together they name the regions and companies that touch your data.
- Location can affect results, not only compliance. Verification checks run from the verifier's IP addresses, and the receiving mail server's reply can depend on how it treats those addresses.
- Retention matters as much as region. Unlimited Verifier states that results are kept 24 hours on the Free plan and 30 days on Pro. Ask separately how long uploaded files are kept.
- Self-hosting gives you control of location if you run the open-source engine in your own region, but you then own outbound port 25 access and your sending IP reputation.
Where are email verification servers located?
Each vendor chooses its own hosting, so the location depends on the company you pick. Hosted verifiers commonly run on a public cloud provider in one or more regions. Vendors that publish their regions most often name US or EU locations, and some also use Asia-Pacific regions. Location is a property of the vendor's architecture, and you confirm it by reading documents rather than assuming.
Buyers tend to blur three different things:
- Headquarters tells you which legal jurisdiction the contract falls under.
- Processing region tells you where verification servers read your upload.
- Backup and replica regions tell you where copies of your data may sit.
A vendor can be headquartered in the US and still process files in an EU region, or the reverse. Use this table as a checklist:
| Layer | What it tells you | Where to find it |
|---|---|---|
| Company headquarters | The legal jurisdiction the contracts fall under | Terms of service, about page |
| Primary processing region | Where verification servers run and read your upload | DPA, security or trust page |
| Backup and replica regions | Where resilience copies may be stored | DPA, sub-processor list |
| Sub-processors | Third parties (cloud, email, support, payments) that handle data | Sub-processor list in the DPA |
| Support and admin access | Where staff who can open customer files work | Privacy policy, DPA |
This article does not state Unlimited Verifier's processing region. Ask the vendor for it in writing before you upload regulated data.
Bottom line: Headquarters tells you the legal home, and the processing region tells you where your data is read. You need both answers.
Why does the server location of an email verifier matter?
Location determines which transfer rules apply to your contacts. A list of names and email addresses is personal data, and moving it across borders creates legal obligations. That makes location a compliance question first and a technical question second.
Three factors drive the stakes:
- Cross-border transfers under GDPR. Article 44 of the GDPR text on EUR-Lex requires that transfers outside the EEA meet the regulation's conditions. In practice that usually means an adequacy decision or Standard Contractual Clauses under Article 46. Breaches of the transfer rules sit in the higher fine tier of Article 83(5), up to €20 million or 4% of worldwide annual turnover, whichever is higher.
- Contract and sector requirements. Customer contracts, public-sector tenders and some regulated industries can restrict where personal data may be processed. Check these before you choose a verifier.
- Exposure window. A file processed in one region and deleted within a day carries a different risk from one copied to backups with no set deletion date. Location and retention together define your exposure.
A sound email verification compliance and hygiene program records the verifier's region alongside its accuracy. Verification also reveals each address to the recipient's mail server, which is a separate disclosure from how the verifier handles your file. Our article on whether email verification can leak your customer list covers that side. For the wider framework, see our email verification data privacy guide, and for whether verification itself counts as processing, read is email verification processing personal data under GDPR.
Bottom line: Location decides which transfer rules apply and how long your contacts sit outside your control.
Does server location change verification results?
It can. Standard verification checks a mailbox by opening an SMTP session with the recipient's mail server and asking whether it accepts the address, a process described in RFC 5321. The receiving server sees the verifier's IP address, and its response depends partly on how it treats that IP.
Most buyers never see this problem. Mail servers may rate-limit connections, return temporary rejections (4xx responses) or block IP ranges they do not trust. A verifier whose probes come from a poorly reputed range may record more "unknown" or "risky" results than one with a clean network, even on an identical list. Results can also shift if a verifier rotates IPs between runs.
Physical distance matters less than you might expect. Most of the wait in an SMTP check is the remote server's response time, not network travel between your file and the verifier.
You can test this yourself. Run a 500-row sample of a stable list on two different days. If the Risky share moves noticeably while the list has not changed, ask the vendor how it handles temporary 4xx responses and whether its probing IPs rotate. A good vendor can answer both questions.
Bottom line: The verifier's network is part of the measurement, so IP reputation can change results even when the location is fine.
How do you find out where a verifier stores your data?
Use a seven-step check. Each step produces a written answer you can file, which matters if a regulator or customer asks later.
- Read the privacy policy for the words "location," "transfer," "region" and "retention." If it names no regions, treat that as your first red flag.
- Request the DPA and look for an explicit transfer mechanism, such as SCCs or reliance on an adequacy decision.
- Open the sub-processor list. Record each entity, its function and its country. A verifier may use one cloud provider for compute and separate tools for support or payments.
- Confirm retention separately for uploaded files and for results. Unlimited Verifier states result retention of 24 hours on Free and 30 days on Pro. Ask how long the original upload is kept.
- Ask who can open customer files and from which country. Support access is the most overlooked gap.
- Ask for independent security evidence. A current attestation is more useful than a sentence about "industry-standard security." See SOC 2 compliant email verification services for what to request.
- Save the answers in writing and reference them in your data protection impact assessment, where one is required under Article 35 of the GDPR.
For a fuller vetting checklist, see how to check if an email verifier is GDPR compliant.
| Question to ask | Good answer looks like | Red flag |
|---|---|---|
| Where is my file processed? | A named region or regions, in writing | "Globally distributed" with no list |
| Which sub-processors touch my data? | A list with entity, function and country | "Trusted partners" with no names |
| How long are uploads and results kept? | Stated periods for each | One vague line covering everything |
| Who can open my files, and from where? | Defined roles and locations | No answer, or "authorised staff" |
| What transfer mechanism applies? | SCCs or an adequacy basis named | Silence on transfers outside your region |
Bottom line: Four written answers (region, sub-processors, retention, access) cover most of what a compliance reviewer will ask.
What if the verifier processes data outside the EU or UK?
A non-EU processing location is allowed, but it needs a transfer mechanism. The usual route is Standard Contractual Clauses, which the vendor signs as part of its DPA. Adequacy decisions are the other route, where the destination country has been formally recognised as providing equivalent protection.
Signing SCCs does not end the analysis. The European Data Protection Board's guidance on transfers expects exporters to assess whether the destination's laws allow government access that would undermine the clauses, and to add supplementary measures where needed. For a list of low-risk uploads, the practical question is simpler: does the data you send need to leave your region at all? If you can minimise the file to the email field and delete results quickly, the exposure is small. If you upload full CRM exports with purchase history, it is not.
Bottom line: Non-EU processing is workable with SCCs and a documented assessment, but minimising what you upload is the cheapest safeguard.
Should you use a hosted verifier or run your own?
Choose a hosted verifier when you need speed and a signed DPA. Run your own engine when your data must never leave infrastructure you control. The trade-off is operational effort, not capability.
| Option | Where data sits | Who controls location | Main trade-off | Best fit |
|---|---|---|---|---|
| Hosted verifier, vendor-chosen region | The vendor's chosen cloud region | Vendor, shown in its DPA | Depends on the DPA and transfer terms | Teams that need a fast, documented setup |
| Hosted verifier with a stated EU region | An EU region, if the vendor offers one | Vendor, confirmed in writing | Not every vendor offers this, so verify it | EU-only customer data |
| Open-source engine in your own cloud region | Your chosen region | You | You manage hosting, updates and IP reputation | Teams with DevOps capacity and strict residency rules |
| On-premise server inside your network | Your own data centre | You | Highest effort; needs mail-sending expertise | Regulated organisations with dedicated infrastructure teams |
The open-source engine is published at github.com/unlimitedverifier/free-email-verifier. Self-hosting is not an automatic escape from transfer questions, and it creates two practical hurdles:
- Outbound port 25. Many cloud providers restrict outbound SMTP on port 25 by default. At the time of writing, AWS's documentation describes restrictions on EC2 that must be lifted by request. Check your provider's current policy before you plan a deployment, at its documentation home or equivalent.
- IP reputation. Your results reflect the reputation of your own IP, not a shared pool that has been warming for years. A new cloud IP may receive more temporary rejections than an established one.
For hosted use, the email verification API lets your own systems send single addresses or batches, so you decide which fields leave your environment. The best email verification tools comparison covers hosted alternatives in more depth. Once you have chosen, the email verification API and automation approach determines how often data moves.
Bottom line: Pick a hosted option with a documented region for most teams, and self-host only when residency rules outweigh the operational work.
How do you check a verifier's data location before you upload a list?
Work through these steps before your first upload. You only need a 20-row test file to finish, and the document checks can be done in an hour.
- Identify the rules that apply. If any contact is in the EU or UK, plan for GDPR or UK GDPR. If you are unsure whether verification itself needs a legal basis, read do I need consent to verify an email address. Write the answer down.
- Send the questions from the table above to the vendor by email, and save the reply.
- Minimise your file. Remove any column the verification does not need, such as phone numbers, notes and purchase history. Keeping only the email field follows the data minimisation principle in GDPR Article 5(1)(c).
- Create a 20-row test file. Include your own test addresses, plus a few you know are invalid.
- Sign up for a free account at sign up. The Free plan handles lists of up to 150 emails, so the test file fits easily.
- Upload and verify with upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically.
- Review the three buckets. Valid, Risky and Invalid results sort every address. For catch-all handling, see the catch-all email verification page. For a spot check of a single address, use the free email checker.
- Export, then delete. Download results as CSV, Excel or JSON. Then remove your copy from the platform as its privacy policy describes. Our guide on deleting your data from an email verifier covers what to request.
- Re-import only the Valid contacts into your ESP or CRM. There are no native ESP, CRM or Zapier integrations, so this is a manual export and re-import step.
If you are still deciding whether uploading is safe at all, read is it safe to upload my email list to a verifier first.
Bottom line: Minimise the file, confirm the answers in writing, test with 20 rows, then upload.
Worked example: where does a 40,000-contact EU list go?
This scenario is illustrative. It shows how plan limits shape the workflow for an EU-focused SaaS company with 40,000 contacts, the kind of list covered by email verification for ecommerce and SaaS.
The constraints: The company needs a documented processing region, a retention policy it can record, and enough verification capacity to process the full list.
Step 1: Can the Free plan handle it? The Free plan allows 25 lists a month, each up to 150 emails.
- 25 × 150 = 3,750 emails per month
- 40,000 ÷ 3,750 ≈ 10.7 months
Free is not practical for this list.
Step 2: Split for Pro. Pro allows lists of up to 25,000 emails each.
- List A: 25,000 contacts
- List B: 40,000 − 25,000 = 15,000 contacts
- Total: 2 lists covering all 40,000 rows
Step 3: Budget the deep verifications. Pro includes 25,000 deep verifications a month, and standard verification is unlimited on every plan. This assumes you deep-check only the addresses that come back uncertain, such as catch-all, role-based or otherwise flagged.
- Run standard verification on all 40,000 rows.
- Deep-check the 12,000 flagged addresses.
- Deep verifications used: 12,000 of 25,000, leaving 13,000 for re-checks.
Step 4: Illustrative results. These figures are hypothetical:
- Valid: 33,200 (83%)
- Risky: 4,800 (12%)
- Invalid: 2,000 (5%)
- Check: 33,200 + 4,800 + 2,000 = 40,000 ✓
Step 5: Cost. One Pro month is $29 on monthly billing, or $25 a month on annual billing, which is $300 a year. If you used all 25,000 deep verifications in one month, the monthly price works out to about $1.16 per 1,000 deep checks ($29 ÷ 25). That is plan-price arithmetic, not a per-email fee. For how plan pricing compares across tools, see email verification pricing.
Step 6: Handle the data. Pro keeps results for 30 days. Export on the day you finish, then set a reminder to confirm deletion by day 30. Confirm upload retention in the privacy policy before you start.
Alternative: the API route. If the company calls the email verification API from its own systems, batches of up to 10,000 emails per request mean 40,000 ÷ 10,000 = 4 requests. Those requests use 40,000 of the Pro plan's 100,000 API emails a month, which is 40%.
For the signup-form side of this workflow, see real-time email validation. For keeping the list clean after the first pass, see email list maintenance best practices.
Bottom line: Two Pro lists, 12,000 deep checks and a 30-day deletion reminder cover this list for about $29 a month.
What mistakes do people make when checking server location?
Most of these errors come from treating marketing language as a compliance answer.
- Treating headquarters as the processing region. A US-headquartered company can process in an EU region, and the reverse is also true. Ask for the processing region separately.
- Accepting "industry-standard security" in place of named regions. Ask for places and companies, not adjectives.
- Ignoring sub-processors. You may have contacted only the verifier, while a cloud provider or support tool handles the actual file.
- Uploading full CRM exports. Phone numbers, notes and purchase history add personal data that verification does not need.
- Merging the two retention clocks. Upload retention and result retention can differ, so record each one.
- Assuming self-hosting removes transfer questions. If your server runs in a US cloud region, that region is your processing location.
- Comparing verifiers without accounting for IP differences. A gap in Risky results can come from the probing network rather than from accuracy.
- Keeping the answers in a phone call. An unrecorded conversation does not help you in an audit. Save the reply in writing.
Bottom line: Most location mistakes come from reading the marketing page instead of the DPA and sub-processor list.
How we compared (and limitations)
This article is based on public documentation: the GDPR text on EUR-Lex, RFC 5321 on SMTP, AWS's published documentation on outbound port 25, the open-source engine's repository and Unlimited Verifier's published plan facts. We have not tested server locations, network paths or IP reputation for any verification vendor, and we have not reviewed any vendor's DPA for this article.
Three limits matter for your decision:
- Unlimited Verifier's processing region is not stated here. Request it, along with the sub-processor list, before you upload regulated data.
- Cloud port policies change. Check your provider's current documentation before planning a self-hosted deployment.
- Vendor figures are claims. Unlimited Verifier states 99.5% accuracy for deep verification. That is the company's own figure, not an independent benchmark. The worked-example percentages are illustrative.
Location checklist by layer
| Layer | What it tells you | Where to find it |
|---|---|---|
| Company headquarters | Legal jurisdiction of the contract | Terms of service, about page |
| Primary processing region | Where verification servers read your upload | DPA, security or trust page |
| Backup and replica regions | Where resilience copies may sit | DPA, sub-processor list |
| Sub-processors | Third parties handling data | Sub-processor list in DPA |
| Support and admin access | Where staff who open files work | Privacy policy, DPA |
Frequently asked questions
Where are most email verification servers located?
Most hosted email verifiers run on public cloud infrastructure in the United States or the European Union, and some use Asia-Pacific regions. The exact location depends on the vendor, so there is no single answer for the whole category. Check the vendor's DPA and sub-processor list for the named processing region.
Does the company's headquarters determine where my data is processed?
No. Headquarters indicates the legal jurisdiction that governs the contract, while the processing region indicates where verification servers read your file. A company headquartered in the US can process files in an EU region, and the reverse is also possible.
What documents show an email verifier's server location?
Ask for the privacy policy, the data processing agreement (DPA) and the sub-processor list. Together these typically name the processing region, backup regions and third parties that handle data. Request the answer in writing before uploading regulated data.
Can server location change email verification results?
It can. Verification checks run from the verifier's IP addresses, and a receiving mail server may respond differently depending on how it treats those addresses. Location is therefore a possible factor in results, not only in compliance.
Do I need to worry about GDPR when choosing a verifier?
If your contact list includes EU personal data, transfers outside the EU fall under GDPR transfer rules, including Article 44. Confirm the processing region, the transfer mechanism in the DPA and the list of sub-processors before you upload.
How long do email verifiers keep my uploaded files?
Retention varies by vendor and is separate from location. Unlimited Verifier states results are kept 24 hours on the Free plan and 30 days on Pro. Ask each vendor separately how long uploaded files and results are stored.
Does self-hosting an email verifier control server location?
Yes. If you run an open-source verification engine in your own chosen region, you control where processing happens. You also take on responsibility for outbound port 25 access, server maintenance and your sending IP reputation.
What is a sub-processor in email verification?
A sub-processor is a third party that handles customer data on the vendor's behalf, such as a cloud host, email provider, support tool or payment processor. Their locations can add to where your data travels, so review the sub-processor list in the DPA.
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.