InboxIQo Email Verification

Verify email addresses from Apify and receive clean, structured results in your dataset. InboxIQo helps you check whether an email address is usable before you add it to outreach, CRM, enrichment, onboarding, or data-quality workflows.

The actor is designed for list validation, automation pipelines, and lead-data cleanup. Paste email addresses, add an optional tag, choose concurrency, and run the actor. Results are written to the default Apify dataset as they complete.

What It Checks

InboxIQo returns practical verification signals for each email address:

• Valid: the mailbox appears to exist.
• Invalid: the address or mailbox appears unusable.
• CatchAll: the domain may accept mail for many or all addresses.
• Disposable: the email belongs to a temporary or disposable provider.
• Spamtrap: the address or domain appears risky.
• Unknown: the result could not be confirmed reliably.

Unknown results are not charged.

Pricing

This actor uses Apify Pay per Event pricing.

One chargeable email verification result equals one paid event. Unknown results are returned in the output but are not billed.

The dataset includes charged and chargeStatus fields so you can see whether each row was charged.

Input

Email addresses

Paste email addresses separated by lines, spaces, commas, or semicolons.

Example:

name@example.com
sales@company.com
support@domain.com

Tag

Optional. Use a tag to group a run by campaign, upload source, client, workflow, or any label that helps you filter results later.

Examples:

july-leads
crm-cleanup
apollo-import

Concurrency

Controls how many email checks run at the same time. The default is 3; the maximum is 25.

For small lists, the default is usually enough. For larger lists, a higher concurrency can finish faster.

Output Fields

Each verified email is saved to the Apify dataset with these fields:

• email: submitted email address.
• status: verification status.
• mailboxResult: mailbox-level result where available.
• freeEmail: whether the domain is a common free email provider.
• account: part before @.
• domain: email domain.
• mxFound: whether mail exchange records were found.
• mxRecord: detected mail domain or provider signal.
• tag: optional tag from the input.
• charged: whether this result was billed by Apify.
• chargeStatus: billing explanation for the row.

Possible chargeStatus values:

• Charged
• Not charged - Unknown result

Example Output

{
  "email": "name@example.com",
  "status": "Valid",
  "mailboxResult": "mailbox_exists",
  "freeEmail": "No",
  "account": "name",
  "domain": "example.com",
  "mxFound": "Yes",
  "mxRecord": "example.com",
  "tag": "july-leads",
  "charged": true,
  "chargeStatus": "Charged"
}

Good Use Cases

• Clean lead lists before importing them into your CRM.
• Check email quality before enrichment or outreach workflows.
• Remove invalid, disposable, risky, or uncertain addresses from datasets.
• Add email verification to Apify tasks, automations, and scheduled jobs.
• Segment results by tag for campaign reporting.

Notes

Email verification depends on signals returned by recipient domains and mail systems. Some domains intentionally hide mailbox-level information, rate-limit checks, or apply security policies. In those cases, InboxIQo may return Unknown, and those rows are not charged.

InboxIQo verifies email addresses only. It does not send marketing campaigns, harvest addresses, or send email on your behalf.

For support, contact support@inboxiqo.com.