Bulk Email Verifier — Verify Gmail, Outlook & Business Emails at Scale

Clean any email list before you send. This Actor gives you honest, mailbox-level answers for Gmail, Google Workspace, Microsoft 365, Outlook and custom business domains — without sending a single email.

Most bulk verifiers return "unknown" for Gmail and Outlook because those providers hide mailbox existence. This Actor goes further: it can ask Google's sign-in page directly and Microsoft's HTTPS endpoint directly, so you get real valid / invalid verdicts instead of guesses.

Why use this Actor

• Cut bounce rate — remove invalid, disposable and role-based addresses before your campaign.
• Protect sender reputation — no test emails are sent, so your domain is never flagged for probing.
• Verify Gmail & Outlook — get concrete verdicts on the providers most tools can only guess about.
• Cheap at scale — addresses are grouped by domain and checked in shared sessions, so large lists cost only Apify compute.
• Honest results — addresses that genuinely cannot be verified are labelled unknown, never faked as valid.

What makes it different

Provider / situation	Typical verifier	This Actor
Gmail / Google Workspace	"Unknown" or guessed	valid / invalid via browser probe when you add residential proxies
Microsoft 365 / Outlook	"Unknown" or guessed	valid / invalid via HTTPS check
Catch-all / accept-all domains	Often guessed as valid	Clearly labelled catch_all so you decide the risk
Secure gateways (Proofpoint, Mimecast, Barracuda)	Often guessed as invalid	Labelled unknown + reason, protecting your reputation
Disposable / throwaway domains	Mixed handling	Marked invalid (or risky if you prefer)

Quick start

1. From the Apify Console

1. Paste your email list into the Emails to verify field.
2. Choose Balanced speed (recommended).
3. If you want to verify Gmail / Google Workspace addresses, turn on Verify Google mailboxes via the sign-in page and paste your residential proxies into Residential proxies.
4. Click Run.
5. Download results from the Dataset tab.

2. Minimal JSON input

{
  "emails": [
    "lead@gmail.com",
    "contact@company.com",
    "support@apify.com"
  ],
  "speed": "balanced"
}

3. Verify Gmail / Google Workspace (recommended setup)

Google blocks datacenter IPs, so Gmail verification needs real residential or ISP proxies.

{
  "emails": ["lead@gmail.com", "name@company.com"],
  "speed": "balanced",
  "googleBrowserProbe": true,
  "residentialProxies": [
    "http://user:pass@host:port",
    "socks5://user:pass@host:1080"
  ],
  "googleProbeConcurrency": 4,
  "googleProbeMaxPerProxyPerHour": 60
}

• googleBrowserProbe — turns on the Gmail / Google Workspace check.
• residentialProxies — list of HTTP(S) or SOCKS5 proxies. Rotated round-robin.
• googleProbeConcurrency — how many browsers run at once. Keep it low (2–4) to stay under Google's radar.
• googleProbeMaxPerProxyPerHour — hourly quota per proxy. Exceeded proxies are rested automatically.

4. Run it from your code

Use the Apify API or any SDK. The Actor returns a Dataset with one item per email and a summary in the key-value store.

curl -X POST https://api.apify.com/v2/acts/andrew_babo~email-verifier-bulk-validator/runs \
  -H 'Content-Type: application/json' \
  -d '{
    "emails": ["lead@gmail.com", "contact@company.com"],
    "speed": "balanced",
    "googleBrowserProbe": true,
    "residentialProxies": ["http://user:pass@host:port"]
  }'

Output explained

One row per email:

{
  "email": "lead@gmail.com",
  "domain": "gmail.com",
  "verdict": "valid",
  "reason": "google_mailbox_exists",
  "provider": "google",
  "isDisposable": false,
  "isRoleAccount": false,
  "isFreeProvider": true,
  "checkedAt": "2026-09-07T10:04:58.207Z"
}

Verdicts

Verdict	Meaning	Safe to send?
valid	Mailbox confirmed to exist	Yes
invalid	Mailbox does not exist, domain has no mail server, or disposable domain	No
catch_all	Domain accepts every address; mailbox-level state is unknowable	Only with care
risky	Deliverable but problematic (e.g. mailbox full or Gravatar-only signal)	Low volume only
unknown	Provider does not disclose mailbox state, or the probe was blocked	Your call

Speed and cost

• Microsoft 365 / Outlook and business SMTP: 10,000–15,000 emails/hour per run.
• Gmail / Google Workspace: roughly 60–120 emails/hour per residential proxy (limited by Google, not the Actor).
• Large lists are grouped by domain and cached, so cost stays low even for hundreds of thousands of addresses.

FAQ

Does it send real emails? No. It only opens a mail-server handshake and never sends a DATA command.

Do I need proxies?

• Required for Gmail / Google Workspace verification (googleBrowserProbe).
• Recommended for real SMTP RCPT TO checks if your host blocks outbound port 25.
• Not required for Microsoft 365 / Outlook HTTPS checks.

Why are some Gmail addresses still "unknown"? Either googleBrowserProbe is off, no residential proxies were supplied, or the proxies were blocked by Google. Try fresh proxies or lower the hourly quota per proxy.

Can it verify Yahoo, iCloud, Proton or QQ? Those providers do not disclose mailbox existence. The Actor returns unknown with a clear reason instead of guessing.

Can I resume a large run? Yes. Progress is checkpointed and a restarted run continues where it stopped.

How many emails can I verify in one run? There is no hard limit. Paste hundreds of thousands of addresses or point the Actor at a public URL with one email per line.

Keywords

bulk email verifier, verify Gmail in bulk, Gmail email verification, Google Workspace email verifier, Outlook email verification, Microsoft 365 email checker, SMTP email verification, email list cleaning, reduce bounce rate, email validator API, catch-all email detection, disposable email checker, role account detection, lead list hygiene.