Bulk Email Deliverability & SMTP Verification avatar

Bulk Email Deliverability & SMTP Verification

Pricing

from $0.49 / 1,000 results

Go to Apify Store
Bulk Email Deliverability & SMTP Verification

Bulk Email Deliverability & SMTP Verification

Check email addresses for syntax, MX records, disposable and role-based domains, and optionally SMTP mailbox existence and catch-all behavior, with a verdict and confidence score per address.

Pricing

from $0.49 / 1,000 results

Rating

0.0

(0)

Developer

Nimbryxo-studio

Nimbryxo-studio

Maintained by Community

Actor stats

0

Bookmarked

3

Total users

2

Monthly active users

17 days ago

Last modified

Features

Limited permissions

Share

Paste an email list and get one clean record per address: syntax, MX and A/AAAA routing, disposable and role-based detection, typo suggestions, SPF/DMARC/DKIM findings, a best-effort SMTP mailbox probe, catch-all detection, a risk level and a recommended next action.

Use it to clean a CRM export, screen sign-up addresses, scrub a lead list before outreach or periodically re-check stored contacts. No API keys, cookies or third-party verification service are required.

What it checks

  • Syntax and normalization - catches malformed addresses and returns the normalized form plus the local part and domain.
  • Domain routing - MX records sorted by priority, the primary mail host, the mail provider, and an A/AAAA fallback when a domain publishes no MX record. A null MX record (0 .) is treated as "does not accept email", not as a deliverability win.
  • Typo suggestions - flags likely mistakes such as gmial.com, hotmail.con or outlok.com with a corrected address in didYouMean.
  • Disposable, role and free providers - separate flags for throwaway domains, shared addresses such as admin@ or support@, and consumer providers such as Gmail or Outlook.
  • Alias signals - plusTag for +tag subaddressing and isAlias for plus tags and Gmail dot aliases.
  • Domain health - whether SPF and DMARC records exist, the DMARC policy, and which common DKIM selectors publish a usable key.
  • SMTP mailbox probe - a best-effort RCPT TO check against the domain's mail server with the raw code and message.
  • Catch-all detection - tests a random address at the domain and reports how confident the result is.
  • Risk and action - a riskLevel (low, medium, high) and a recommendedAction (send, send_with_caution, verify_manually, remove).
  • Batch summary - a key-value store record named SUMMARY with totals, truncation and per-domain cap counts. It is separate from the dataset, so one dataset row still means one unique email address.

Output per email

FieldTypeDescription
emailstringThe normalized address, or the trimmed input when syntax fails.
normalizedEmailstringNormalized address (domain lowercased, IDN converted) when syntax passes.
localPartstringThe part before @.
domainstringThe domain that was checked.
verdictstringvalid, invalid, risky, disposable or unknown.
confidencenumber0-100 confidence score for the verdict.
checksobjectOnly checks that actually ran: syntax, mxRecord, aRecord, smtp, disposable, roleBased, freeProvider, catchAll.
mxHoststringHighest-priority mail host.
mxRecordsarrayMX records as {host, priority} objects, sorted by priority.
mxProviderstringRecognized provider such as Google, Microsoft, Proton, Zoho or Fastmail.
aRecordFallbackbooleantrue when there is no MX record and mail routing falls back to A/AAAA.
domainExistsbooleanWhether DNS shows the domain exists.
didYouMeanstringSuggested correction for a likely typo in the domain.
isAliasbooleantrue for plus-tag subaddressing or a Gmail dot alias.
plusTagbooleantrue when the local part contains +.
domainHealthobjectspf and dmarc booleans, dmarcPolicy when published, and dkimSelectors for common selectors with a usable key.
smtpAttemptedbooleantrue when an SMTP probe was attempted.
smtpVerifiablebooleantrue when the server returned a mailbox-level RCPT response.
smtpCodenumberRaw SMTP response code from the mailbox probe.
smtpMessagestringRaw SMTP response text (trimmed).
checks.catchAllbooleanWhether the domain accepted a random address.
catchAllConfidencenumber0-100 confidence in the catch-all result. A random-address acceptance scores 60 because some servers accept first and bounce later.
catchAllMethodstringMethod used for catch-all detection (smtp-random-recipient).
riskLevelstringlow, medium or high.
recommendedActionstringsend, send_with_caution, verify_manually or remove.
reasonstringPlain-language explanation when the verdict is not a clean valid.
verifiedAtstringISO 8601 UTC timestamp.

Fields that were not measured are omitted, not set to null. A false boolean is kept because it is a real answer.

Input

At least one of emails, emailsText, or datasetId is required. Apify's input-schema validator does not support anyOf, so this is enforced by the actor with a clear failure message.

FieldTypeDefaultDescription
emailsarray of strings-Email addresses, one per item.
emailsTextstring-The same list as text, separated by new lines, commas, semicolons or spaces.
datasetIdstring-Optional existing dataset ID to read emails from. The dataset must be readable by the run.
datasetEmailFieldstringemailColumn name that holds the address when datasetId is used.
includeSourceFieldsbooleanfalseCarry the original dataset row in sourceData.
verificationDepthselectstandardbasic, standard or deep.
concurrencyinteger10Parallel checks (1-50).
maxEmailsinteger10000Upper bound on unique addresses per run (1-100000).
maxEmailsPerDomaininteger100Cap per domain; extra addresses get an explanatory unknown record.
smtpTimeoutnumber10Per-probe SMTP timeout in seconds (1-60).
maxRetriesinteger2Extra attempts for temporary DNS, connection and SMTP 4xx failures (0-5).
checkSmtpbooleanfalseRun SMTP probing at basic or standard depth.
checkCatchAllbooleanfalseDetect catch-all domains; implies SMTP probing.
includeDomainHealthbooleantrueAdd SPF, DMARC and common DKIM selector findings at standard or deep depth.

emails and emailsText are combined, then duplicates are removed case-insensitively. If both are empty the run fails with a clear message.

Example: clean a pasted list

{
"emailsText": "alice@company.com, bob@gmial.com\ncarol@mailinator.com",
"verificationDepth": "standard"
}

Example: deep check for a short list

{
"emails": ["prospect@target-company.com"],
"verificationDepth": "deep",
"checkSmtp": true,
"checkCatchAll": true,
"smtpTimeout": 15
}

Example: large list with a per-domain cap

{
"emailsText": "...",
"verificationDepth": "basic",
"maxEmails": 50000,
"maxEmailsPerDomain": 50,
"concurrency": 30
}

How to read the verdict

  • valid - syntax and domain routing are sound. If SMTP was enabled and answered, the mailbox was accepted. Without SMTP, this means the domain can receive mail, not that the individual mailbox exists.
  • invalid - broken syntax, a non-existent domain, a null MX record, no MX/A routing, or a definitive mailbox rejection such as SMTP 550.
  • disposable - the domain is on a bundled disposable-domain list.
  • risky - the domain accepts random addresses (catch-all), so an accepted mailbox proves little.
  • unknown - the run could not decide. The reason field says why, and no guess is made in either direction.

SMTP is best-effort, by design

Port 25 is not guaranteed to be open from every network, and many large providers block probe traffic based on the sender IP's reputation, missing reverse DNS or greylisting. When the probe cannot reach the server or the server refuses the probe itself:

  • smtpAttempted stays true.
  • smtpVerifiable is false.
  • checks.smtp is omitted.
  • The verdict is unknown when SMTP was the deciding check.

An unreachable server is never turned into valid or invalid. This is deliberate: a blocked probe says nothing about the mailbox. If you need mailbox-level certainty for a list, run deep from a network with a reputable sending IP and expect some providers to remain unverifiable.

Catch-all detection has the same honest limit: a server that accepts every address at SMTP time may still bounce later. That is why catchAllConfidence is 60 for an accepted random address, and the verdict becomes risky rather than a confident catch-all claim.

Domain health coverage

SPF and DMARC are read from public DNS TXT records. DKIM is checked only on a small set of common selectors (google, selector1, selector2, default, k1, s1, dkim, mail). A missing dkimSelectors field means none of those selectors published a usable key; it does not prove the domain has no DKIM at all, because many domains use custom selectors. Domains with a wildcard TXT record are skipped for DKIM rather than reported as a false match.

Batch behavior and limits

  • Records are pushed in batches while the run is still working, so a long list does not sit entirely in memory.
  • A per-domain semaphore limits how many SMTP connections hit one mail server at once.
  • maxEmails truncates the input and the count is reported in the SUMMARY record and status message.
  • maxEmailsPerDomain does not silently drop addresses: each skipped address gets an unknown record with a reason.
  • No summary row is added to the dataset, so one row still means one unique email address.

FAQ

Is a valid verdict a guarantee that the mailbox exists? No. At standard depth it means the address is well-formed and the domain can receive mail. Only a completed SMTP probe can speak to the mailbox, and even then a provider may accept and bounce later.

Why did a Gmail address come back unknown in deep mode? Gmail and several other large providers reject probe traffic from many IP ranges. The actor reports that honestly instead of calling the address valid or invalid.

Why is checks.smtp missing instead of false? false means the server explicitly rejected the mailbox. A missing value means the probe did not produce a mailbox-level answer (blocked port, policy rejection, timeout or temporary response).

What does catchAllConfidence: 60 mean? The domain accepted a random address. That is evidence of catch-all or accept-then-bounce behavior, but it is not proof that every address is deliverable.

Can I use this for very large lists? Yes. Keep concurrency moderate, set maxEmailsPerDomain to protect individual mail servers, and use basic or standard depth unless mailbox-level probing is required.

Can I use a CSV or an existing dataset? Paste the email column into emailsText, or set datasetId to a dataset that the actor can read (attach it to the run or make it readable by ID) and choose datasetEmailField. Turn on includeSourceFields to carry the original row into sourceData.

What are the remaining limits? Outbound port 25 is unavailable from Apify cloud workers, so deep SMTP probes usually return unknown; 587/465 require authentication and are not a workaround. Provider reputation blocks, catch-all versus accept-then-bounce, catch-all mailbox resolution, arbitrary DKIM selectors, and A/AAAA parking domains cannot be resolved definitively without sending mail. Domain age is not shipped because RDAP has no service for several TLDs. These limits are reported honestly rather than converted into false verdicts.

Where is the batch summary? Open the run's key-value store and read the record named SUMMARY. It contains input counts, truncation, per-domain cap counts, verdict totals and SMTP counters. No extra row is added to the dataset.

Does it need credentials? No. MX, A/AAAA, SPF, DMARC, DKIM and SMTP checks all use public DNS and the recipient's own mail server. No account, API key or cookie is used.