Article
Is Verifying Emails Without Permission Legal? US, UK and EU Rules
By Unlimited Verifier Team ·

Summary
Verifying an email address is usually lawful in the US, UK and EU and generally doesn't require prior consent, because the check is processing that can rest on legitimate interests. The bigger legal risks come from where the list came from and how you use the addresses afterwards.Generally yes: verifying an email address is usually lawful in the US, UK and EU, and in the UK and EU it typically rests on the legitimate interests basis in GDPR Article 6(1)(f), so prior consent isn't needed for the check.
The check itself is rarely the problem. The legal exposure sits in where the list came from, what you send afterwards, and how long you keep the results. This page covers the rules in the US, UK and EU, the reasoning behind each answer, and a verification process you can document. It is practitioner guidance, not legal advice, and for high-risk lists you should confirm the position with counsel. It sits inside our email verification and data privacy guide and covers the wider email verification compliance and hygiene picture.
Quick answer
- Verification usually doesn't need prior consent. Consent rules mainly govern sending marketing email. Checking an address is processing that needs a lawful basis, and legitimate interests is the basis most teams rely on.
- The list's origin matters more than the check. Verifying your own customers is low risk. Verifying scraped or undocumented purchased lists is high risk, and deleting them is often the right call.
- Write down your reasoning. A one-page legitimate interests assessment and a retention rule protect you better than any vendor's marketing claims.
- Get the verifier's terms in writing. Ask for a data processing agreement and stated retention periods. Unlimited Verifier publishes 24-hour retention on Free and 30 days on Pro.
- Keep the working copy short. Export results, store them securely, and purge them once they have served their purpose.
Is verifying an email address without permission legal?
Verifying an address is generally lawful, but "without permission" is the wrong frame. The check is a processing step that needs a legal basis, and the marketing that follows has its own rules. An address like jane.smith@firm.com identifies a person, so it counts as personal data even at a business.
| Jurisdiction | Law that matters | What it says about verification | What it says about sending |
|---|---|---|---|
| United States | CAN-SPAM Act, enforced by the FTC | Not addressed as a separate activity | Opt-out model: clear identification, a working unsubscribe honoured within 10 business days, and a valid postal address. Harvesting addresses and dictionary attacks are aggravated violations under 15 U.S.C. § 7704(b). |
| United Kingdom | UK GDPR and PECR, enforced by the ICO | Personal-data processing that needs a lawful basis | Corporate subscribers can generally receive marketing email with an opt-out. Individual subscribers, including sole traders, generally need prior consent. |
| European Union | GDPR and national ePrivacy rules | Needs an Article 6 lawful basis | Set nationally, and B2B rules differ by member state |
The stakes are real. The top tier of GDPR fines reaches €20 million or 4% of global annual turnover, whichever is higher (Article 83(5)). CAN-SPAM penalties apply per violation, so a large send to bad data multiplies quickly.
The US difference is worth noting. Its default is opt-out, so the main legal question is what you send and how you identify yourself, not whether you checked the address first.
Bottom line: Verification is generally lawful in the US, UK and EU, but the rules that govern sending still apply after the check.
Do you need consent to verify an email address?
No. Consent is one of six lawful bases under GDPR Article 6(1), and for verification it is usually the least workable. You can't ask a cold prospect for consent before checking whether their address exists, because the check is what tells you whether the address is worth contacting. For the detailed reasoning, see do I need consent to verify an email address, and for whether the check counts as personal-data processing, see is email verification processing personal data under GDPR.
| Lawful basis | Fits verification? | When it fits | Watch-out |
|---|---|---|---|
| Consent (Art 6(1)(a)) | Rarely | Only where the person has already agreed to be checked | Circular for cold lists |
| Legitimate interests (Art 6(1)(f)) | Usually the best fit | Your customers, sign-ups and event contacts who would reasonably expect the contact | Needs a documented balancing test |
| Contract (Art 6(1)(b)) | Sometimes | Checking details a customer supplied to receive a service | Covers the service, not marketing |
| Legal obligation (Art 6(1)(c)) | Rarely | Only where a specific law requires accuracy checks | Don't invoke it without a specific rule |
For legitimate interests, the ICO's guidance uses a three-part test. Write it down in one page:
- Purpose: Keeping contact data accurate, so you don't mail people who don't exist and damage your sending reputation.
- Necessity: A syntax check cannot tell whether a mailbox exists. Verification is the least intrusive way to answer that question.
- Balance: People reasonably expect a business to check the details they gave it. Process only the fields you need, and send no marketing content during the check.
People keep the right to object to processing based on legitimate interests (Article 21). Give them a simple way to object and log each objection.
Bottom line: Use legitimate interests, write the assessment down, and reserve consent for the marketing that follows.
Does the source of your list change the answer?
Yes, far more than the verification step does. Verifying a list doesn't cure how it was collected, and a fast check can make a bad list look usable. Under GDPR Article 14, if you obtained personal data from a third party, you must inform the individuals within a reasonable period and no later than one month.
| List source | Verification risk | Why | What to do first |
|---|---|---|---|
| Your own customers | Low | Expected processing within an existing relationship | Verify, then segment by recency |
| Opt-in sign-ups | Low | Your consent wording covers contact, and verification is hygiene | Check the consent wording, then verify |
| Trade-show or event scans | Medium | Depends on what attendees were told when they handed over their details | Review the collection terms and document a balancing test before verifying |
| Purchased or rented lists | High | Article 14 notice is often impossible to give, and provenance is frequently unprovable | Request written provenance. If it doesn't exist, delete the list rather than verify it. |
| Scraped addresses | Very high | Usually breaches site terms and privacy law, and harvesting is an aggravated CAN-SPAM violation | Delete. Don't verify data you shouldn't hold. |
A common error is reading a high Valid rate as proof the list is fine. Take a hypothetical team that checks 40,000 addresses and gets 30,000 Valid results. Those mailboxes probably exist, but that says nothing about whether those people agreed to hear from the company. Valid means deliverable, not permitted.
If you're considering cold outreach, read whether it's ethical to verify emails before cold outreach. For the workflow, see email verification for sales prospecting.
Bottom line: Decide whether you may hold a list before you decide whether to verify it.
Which verification methods carry the least legal exposure?
Syntax and domain checks carry the least exposure because they touch only the address string or domain records. The SMTP mailbox check is the one most people ask about, because it contacts the recipient's mail server, so it needs the most deliberate justification.
An SMTP check opens a connection to the recipient domain's mail server and issues standard commands defined in RFC 5321, including RCPT TO with the address. The server replies, and the verifier disconnects before any message body is sent. Nothing is delivered to the person's inbox.
Data protection regulators generally focus on purpose, lawful basis and transparency rather than on the technique. Dictionary attacks and harvesting are different: they generate or collect addresses to send to, which is what CAN-SPAM's aggravated-violation provisions target. Checking addresses you already hold for a documented purpose is a different activity. Checking a harvested list is not.
| Method | What it reveals | Personal data touched | Relative legal exposure | Best use |
|---|---|---|---|---|
| Syntax check | Formatting errors | The address string only | Lowest | First pass to catch typos |
| Domain and MX lookup | Whether the domain can receive mail | Domain records only | Very low | Remove dead domains early |
| SMTP mailbox check | Whether the receiving server accepted the recipient at check time | Recipient's mail server is contacted | Moderate: personal-data processing plus server etiquette | Full check on segments you have a documented basis to hold |
| Catch-all detection | Whether the domain accepts any address | Domain level | Low | Hold back rather than treat as confirmed |
| Disposable and role flags | Throwaway inboxes or shared addresses such as info@ | Address string | Low | Exclude from personal outreach |
| Double opt-in email | Whether the person clicked a confirmation | Sends a message to the person | Highest for cold lists, because the confirmation is itself an email | Only for people already expecting contact |
| Engagement history (your data) | Recent opens, clicks or purchases | Data you already hold | Low | Prioritise sends |
Catch-all domains deserve special mention. They accept every address, so a "yes" tells you nothing about the individual mailbox. Unlimited Verifier detects catch-all domains and flags them so you can hold those addresses back rather than count them as confirmed. The catch-all email verification page explains how they're handled.
On pacing, M3AAWG, the messaging industry body, publishes best-practice material on responsible mail handling. Heavy probing can get a verifier throttled or blocked, so good tools rate-limit their checks.
Bottom line: Use the lightest method that answers your question, and treat the SMTP check as a deliberate step for segments with a documented basis.
What should you check about a verifier's data handling?
Before you upload anything, ask for a written data processing agreement, stated retention periods and a documented deletion process. Under GDPR Article 28, a verifier that processes data on your behalf is generally a processor, and the contract must cover instructions, confidentiality, security, sub-processors and deletion.
| Question | What a good answer looks like |
|---|---|
| Will you act as my processor, and is a DPA available? | A written DPA you can review, not a clause buried in general terms |
| How long are uploads and results kept? | Specific periods. Unlimited Verifier publishes 24 hours on Free and 30 days on Pro. See how long email verifiers keep uploaded lists. |
| How do I request deletion? | A stated written process. See can I delete my data from an email verifier. |
| Where is processing done, and who are the sub-processors? | Named locations and providers. See where email verification servers are located. |
| Is my data used for training or marketing? | A clear written no |
| Can I inspect the verification logic? | Unlimited Verifier's verification engine is open source on GitHub, so you can read how the checks are implemented |
Leak risk depends mostly on storage and access inside your own organisation, so read can email verification leak my customer list for the practical controls.
Hashing is a common shortcut that doesn't work. Under GDPR Recital 26, pseudonymised data remains personal data, and verification needs the real address to function. Hashing may reduce exposure in some cases, but it isn't a legal fix. See does email verification work with hashed emails.
Retention is where most teams are vague. Platform retention governs the vendor's copy, not yours. Once you download a file, you are the controller, and the storage limitation principle in Article 5(1)(e) applies to you.
Compare options in our guide to the best email verification tools, and check each vendor's own privacy terms. For a broader review, see how to check if an email verifier is GDPR compliant and is it safe to upload my email list to a verifier.
Bottom line: Get the processor terms in writing, know the platform's retention window, and keep your own copy only as long as you need it.
How do you verify an email list legally, step by step?
Work through seven steps: map each row to its source, delete what you can't defend, write an assessment, minimise the upload, verify in stages, act on each bucket with a purpose, and set retention. Each step produces a record you can show a regulator.
- Map each row to its source and original purpose. Tag every address as customer, opt-in, event, purchased or scraped, and note what the person was told when they gave it to you.
- Delete what you can't defend. Scraped lists and purchased lists without provenance come out first. Log the date and count of the deletion, not the addresses themselves.
- Write a legitimate interests assessment for each remaining source. One page per source is enough. Cover purpose, necessity and balance.
- Minimise the upload. Send only the email column plus an internal ID, so results can be joined back to your record. Remove names, notes and CRM fields you don't need, in line with the data minimisation principle in Article 5(1)(c).
- Verify in stages. Run the full check on the list, then use deep verifications on the segments where a more confident result would change what you do.
- Act on each bucket with a purpose. Valid addresses go to marketing only where the source allows it. Risky addresses are held back. Invalid addresses are suppressed, and you keep a minimal suppression record so you don't mail them again, which is itself a legitimate purpose.
- Set retention and repeat on a schedule. Export results, store them securely, purge the working copy once it has served its purpose, and re-verify on a regular cycle. The email list maintenance best practices guide covers the schedule. For new signups, real-time email validation stops bad addresses at the form. As a rule of thumb, keep working copies no longer than 30 days. That's a practical convention, not a legal figure.
Bottom line: Source and purpose come before the check, and retention comes after it.
How do you verify a list in Unlimited Verifier?
Upload a minimal file, verify it, sort results into Valid, Risky and Invalid, then export and re-import only what your source supports.
- Create an account. Sign up to start. The Free plan includes 25 lists a month of up to 150 emails each, plus 750 deep verifications, which is enough for a pilot. Free has no API access.
- Prepare a minimal file. Keep the email column and an internal ID column, and delete everything else. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically, but confirm the detection before you run.
- Split large lists. Pro lists hold up to 25,000 emails each. Divide bigger files, and note how you split them.
- Upload the file. Use Upload and verify a list.
- Run verification. Standard verification is unlimited on every plan, with no per-email fees. Each address is checked for syntax, domain, MX records and the SMTP mailbox.
- Read the three buckets. Review the Valid, Risky and Invalid results, along with the catch-all, disposable and role-based flags. Those flags determine how each record may be used. A role address such as info@ is usually not a personal contact.
- Export and record. Download as CSV, Excel or JSON. Store the file in an access-controlled location, and log the date and counts in your assessment file.
- Re-import selectively. Upload only the Valid segment your source supports to your email platform, and add Invalid addresses to your suppression list. There are no native ESP, CRM or Zapier integrations, so this is a manual CSV step or an API job.
- Set a purge date. Results are kept 24 hours on Free and 30 days on Pro, so export before the window closes, then delete your own copy on your schedule.
- Spot-check or automate. Check a single address with the free email checker. For recurring workflows, the API route uses API keys, which come with Pro's 100,000 emails a month, and accepts bulk batches of up to 10,000 emails per request. Create keys on the Email verification API page.
Bottom line: Upload the minimum, export what you need, and keep the platform's retention window in mind.
What does a compliant verification look like with real numbers?
This scenario is hypothetical. The plan limits and arithmetic are real. It shows how the legal decision and the verification run fit together for an email verification for ecommerce and SaaS database.
A B2B SaaS company holds 40,000 rows:
- 22,000 own customers
- 12,000 trade-show scans
- 6,000 purchased leads with no written provenance
Decision: The 6,000 purchased leads come out before any verification. Without provenance, the company can't meet the Article 14 notice requirement, so it deletes them and logs the date and count.
Remaining: 40,000 − 6,000 = 34,000 addresses to verify.
Plan fit:
- Pro lists hold up to 25,000 emails each, so 34,000 splits into 25,000 + 9,000.
- Standard verification of all 34,000 is included, with no per-email fee.
- The 12,000 trade-show addresses are the segment where the company wants the most confident result, so it runs them as deep verifications. That uses 12,000 of the 25,000 monthly allowance and leaves 13,000 for re-checks.
Cost: Pro is $29 a month, or $25 a month billed annually ($300 a year). If you use the full 25,000 deep-verification allowance in one month, the effective cost is $29 ÷ 25,000 × 1,000 = $1.16 per 1,000 deep verifications. Compare email verification pricing against your expected list size and how many deep checks you need, not just the headline plan price.
Hypothetical results on the 34,000:
| Bucket | Count | Share | Action |
|---|---|---|---|
| Valid | 27,200 | 80% | Mail where the source allows it |
| Risky | 4,080 | 12% | Hold back; review trade-show records |
| Invalid | 2,720 | 8% | Suppress; keep a minimal suppression record |
Check: 27,200 + 4,080 + 2,720 = 34,000.
Retention: The company exports results on day one and sets a purge date within 30 days, so its working copy follows the platform's window.
Free-plan reality check: The Free plan allows 25 lists of up to 150 emails each per month, which is 25 × 150 = 3,750 emails a month. That suits a pilot, not a 40,000-row database.
Bottom line: The legal decision, deleting the undocumented purchased list, did more work than the verification did.
What are the most common legal mistakes?
Most legal problems come from the list's origin and its retention, not from the verification click.
- Treating "we verified it" as a lawful basis. Verification doesn't cure unlawful collection.
- Verifying scraped or purchased lists before asking where they came from.
- Planning to rely on consent for the check, then finding you can't obtain it before checking. Legitimate interests is the workable basis.
- Sending double opt-in emails to cold addresses. The confirmation is itself an outbound marketing email to someone who never asked for it.
- Uploading full CRM exports when an email column and an ID would do.
- Assuming hashing makes data anonymous, when pseudonymised data stays personal.
- Purging the platform on schedule but keeping exported files indefinitely.
- Reading Valid as opt-in. Verification can confirm a mailbox exists, not that someone agreed to receive your email.
- Counting catch-all addresses as confirmed to inflate list size.
- Skipping the written assessment because "everyone does it." A regulator will ask for your reasoning, not the industry norm.
Bottom line: Fix the list's origin and retention first, and the verification step becomes a routine, defensible part of your process.
How we compared (and limitations)
This page is based on public sources: the text of GDPR, ICO and FTC guidance, RFC 5321, and Unlimited Verifier's published plan facts. We haven't tested any vendor's data handling or compared competitors' compliance, and this page makes no claims about them.
- Jurisdictions: Coverage is limited to the US, UK and EU. Rules in Canada, Australia, Brazil and elsewhere differ and need separate review.
- Vendor figures: Unlimited Verifier states 99.5% accuracy for deep verification. That is the company's own figure, not an independent benchmark.
- Worked example: The 40,000-contact scenario and its percentages are hypothetical. The plan limits and arithmetic are real.
- Legal currency: Laws, regulator guidance and enforcement change. Check the current text before relying on any point here.
- Not legal advice: For scraped data or large purchased databases, get advice from qualified counsel in your jurisdiction.
Bottom line: Use this as a framework for your own documented decisions, and confirm the current law before you act.
Documented verification process
- Identify the source of each list and record how the addresses were collected.
- Confirm the subscriber type (corporate or individual) for UK sends.
- Write a one-page legitimate interests assessment covering purpose, necessity and balancing.
- Get a DPA and stated retention periods from the verification vendor.
- Verify only lists with a clear, documented origin; delete undocumented lists.
- Export results, store them securely, and purge on a fixed schedule.
- Suppress bounces and complaints immediately and record the suppression.
Frequently asked questions
Is it illegal to verify an email address without permission?
No, verifying an email address is generally not illegal in the US, UK or EU. The check is a processing step that needs a lawful basis, and in the UK and EU legitimate interests is the basis most teams rely on. The legal risk usually comes from how the list was obtained and how you email the addresses afterwards.
Do I need consent to verify email addresses under GDPR?
Usually not. GDPR requires a lawful basis for processing personal data, and consent is only one of six options in Article 6(1). Many organisations verify addresses under legitimate interests, which requires a documented balancing test showing the processing is necessary and does not override the individual's rights.
Does CAN-SPAM prohibit email verification?
CAN-SPAM does not address email verification as a separate activity. It regulates commercial email, requiring accurate headers, clear identification, a valid postal address and a working unsubscribe honoured within 10 business days. Harvesting addresses and dictionary attacks are treated as aggravated violations.
Can I verify a purchased email list?
You can, but the purchase itself is the bigger risk. Verifying a purchased or scraped list may reveal that the data was collected unlawfully, and continuing to use it can expose you to enforcement. Many compliance teams delete undocumented lists rather than verify and mail them.
What is a legitimate interests assessment for email verification?
A legitimate interests assessment is a short written record showing the purpose of the processing, that it is necessary for that purpose, and that your interest is not overridden by the individual's rights. For verification, it typically covers keeping lists accurate and reducing bounces, plus the safeguards you apply.
Is it legal to email addresses that verification marks as valid in the UK?
Verification confirms an address is deliverable but does not grant permission to market to it. In the UK, PECR generally requires prior consent for marketing to individual subscribers, including sole traders, while corporate subscribers can usually receive marketing with an opt-out. Check the subscriber type before sending.
How long can I keep email verification results?
Keep results only as long as needed for their purpose, and set a documented retention period in your policy. Under GDPR, storage limitation requires that personal data is not kept longer than necessary. Export what you need, store it securely, and delete the rest on a fixed schedule.
Does email verification notify the person whose address is checked?
A verification check normally does not deliver a message to the recipient's inbox. It tests whether the address is deliverable, which is why it is generally treated as a data-processing step rather than a marketing action. Confirm the method your vendor uses in its documentation.
Do I need a data processing agreement with an email verification provider?
If the provider processes personal data on your behalf, GDPR Article 28 requires a written data processing agreement. Ask the vendor for its DPA, subprocessor list, data location and stated retention periods before you upload any list.
What should I do if a verified address later bounces or complains?
Suppress the address immediately and stop sending to it. Repeated bounces or spam complaints signal poor list quality and can harm deliverability and compliance. Record the suppression so the address is not re-imported from another source.
Is email verification compliant in the EU if the list contains B2B contacts?
Verification of B2B contacts generally relies on legitimate interests, but marketing rules vary by member state. Some countries apply stricter consent requirements to business email than others. Confirm the national ePrivacy rules for each market you send to.
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.