Email Verifier — Email Validation, MX and SMTP Checks (No API Key)

Email Verifier checks a list of addresses and returns one structured result for each input. It checks address syntax, looks up the domain's mail-exchange (MX) records, identifies common free and disposable providers, and reports the result of a bounded SMTP recipient check when the destination mail server allows one. The Actor does not send an email, does not need an API key, and does not ask you to log in.

Get your first results in under 2 minutes. Start with the prefilled reserved-domain examples, then replace them with addresses you are authorized to process.

The output keeps uncertain cases visible. valid, invalid, catch-all, and unknown are separate outcomes. A mail server can accept every address, block verification probes, greylist, or change its policy. An SMTP check is one signal, not a promise that a message will reach an inbox.

Table of contents

• What this Actor checks
• Who uses it
• Output fields
• How to run it
• Input example
• Output example
• Accuracy and limits
• Pricing
• Tips
• Want other data?
• MCP and AI agents
• Integrations and API
• FAQ
• Related searches
• Disclaimer
• Resources
• 中文说明

What this Actor checks

• Parses each submitted address and reports whether its syntax matches the Actor's practical email format checks.
• Looks up DNS MX records for syntactically valid domains.
• Reports the selected MX host when DNS returns one.
• Flags common free-mail providers and a maintained set of disposable-mail domains.
• Checks SMTP availability and, when possible, whether the server accepts the recipient command.
• Detects a catch-all response when a server accepts a random, nonexistent recipient. Catch-all domains are marked uncertain rather than treated as confirmed deliverable.
• Returns an explicit unknown result when the destination cannot be confirmed, including when a server blocks or times out a check.
• Writes one dataset item for each processed input. Invalid syntax is still a result, not a dropped row.

Who uses it

• Sales operations teams cleaning a permission-based prospect list before importing it to a CRM.
• Marketing operations checking a list collected with appropriate consent before a campaign.
• Developers adding a verification stage to an enrichment or data-quality workflow.
• Researchers separating malformed addresses, domains without MX records, catch-all domains, and inconclusive checks.
• Small businesses checking a handful of addresses without signing up for a separate verification API.

This Actor is not a way to discover addresses. It verifies only addresses you provide. Use it only when you have a lawful basis to process the data and follow the rules that apply to your list and location.

Output fields

Field	Type	Description
email	string	The exact submitted address for this result. Always populated.
syntaxValid	boolean	Whether the local syntax check accepted the address. Always populated.
status	string	valid, invalid, catch-all, or unknown. Always populated.
confidence	string	high, medium, or low, based on the checks that completed. Always populated.
domain	string or null	Domain parsed from a syntactically valid address. Populated when parsing succeeds.
hasMx	boolean	Whether DNS returned an MX record for the domain. Always populated.
mxHost	string or null	The preferred MX host returned by DNS. Populated when an MX record exists.
smtpDeliverable	boolean or null	Recipient acceptance signal. null means SMTP did not provide a conclusive answer.
catchAll	boolean	Whether the mail server accepted a random address during the catch-all check.
isFreeProvider	boolean	Whether the domain appears in the Actor's common free-mail provider set.
isDisposable	boolean	Whether the domain appears in the Actor's disposable-mail domain set.

status is a summary of the observed checks, not a guarantee of future delivery. A valid response means the checks accepted the address at that time. A later message can still bounce because the mailbox is full, disabled, filtered, or changed after the run.

Status meanings

Status	Meaning
valid	Syntax and MX checks passed, and the SMTP recipient check returned an acceptance response.
invalid	Syntax failed, or the domain could not receive mail according to the available DNS/SMTP result.
catch-all	The server accepted a random recipient, so individual mailbox existence could not be established.
unknown	The domain has mail routing, but the server did not provide a reliable recipient answer.

How to run it

1. Open the Actor and keep the prefilled sample if you only want to inspect the output shape.
2. Replace emails with addresses you have permission to process. Use one address per line in the input form.
3. Set maxItems to the number of rows you want, up to 100.
4. Start the run. The Actor returns a row for each address it processed.
5. Open the Verification results view for a compact table. Use DNS and domain details to inspect MX results, or download the full dataset as JSON, CSV, or Excel.
6. Treat unknown and catch-all as inconclusive. Do not turn them into a hard pass or hard fail without another authorized verification method.

Runs are bounded to 100 addresses. A run with no usable email input finishes SUCCEEDED with zero rows and zero result charges; inspect OUTPUT for the INPUT_ERROR reason.

Input example

{
  "emails": [
    "test@example.com",
    "invalid@@example.com",
    "ops@example.com"
  ],
  "maxItems": 3
}

The reserved example domains are safe placeholders for trying the form. They are not evidence that a real mailbox exists. Replace them with your own authorized test addresses when checking a live mail setup.

Input	Type	Default	Limit
emails	array of strings	Prefilled examples	Up to 100 addresses. Malformed addresses are skipped without a result charge and explained in OUTPUT; valid addresses continue to verification.
maxItems	integer	100	1–100; limits how many addresses from the list are processed.

Output example

The following row is from an actual Actor run using the reserved address test@example.com. It is a verification finding, not proof of a deliverable mailbox. Malformed input is explained in OUTPUT rather than stored as a verification row.

[
  {
    "email": "test@example.com",
    "hasMx": false,
    "domain": "example.com",
    "mxHost": null,
    "status": "invalid",
    "catchAll": false,
    "confidence": "high",
    "syntaxValid": true,
    "isDisposable": false,
    "isFreeProvider": false,
    "smtpDeliverable": null
  }
]

The example uses the values from the live core run. For the reserved test domain, mxHost and smtpDeliverable were null because no MX record was returned. Null means no value was available; it is not an SMTP rejection.

Accuracy and limits

Email verification is probabilistic because mail servers control what anonymous SMTP clients can learn. This Actor reports observed responses; it cannot see a mailbox, deliver a message, or guarantee that a message will be accepted later.

• A domain can have MX records while the server refuses anonymous checks. That result is unknown, not a claim that the address is valid.
• A catch-all server can accept any recipient. The Actor returns catch-all and low confidence rather than claiming every mailbox exists.
• Greylisting, connection limits, temporary outages, network policy, and provider filtering can prevent a conclusion.
• Disposable-domain detection uses a maintained list. New or unlisted temporary-mail domains may not be recognized.
• Free-provider detection covers common domains. A domain's classification can change, and a business may use a custom domain hosted by a free provider.
• Syntax validation is intentionally pragmatic. It does not prove that the mailbox exists.
• MX records can change after a run. Keep the run timestamp with the result when freshness matters.
• Some servers accept a recipient during SMTP and still reject a later message. Delivery depends on sender reputation, message content, authentication, and the recipient's policy.
• The Actor does not send DATA, does not send a message body, and does not confirm inbox placement.
• The Actor processes up to 100 addresses per run. Larger lists should be split into batches you are permitted to process, and each row is billed as a result.

Pricing

The Actor uses pay-per-event pricing. Each stored result row is one apify-default-dataset-item event at $0.0005 per row ($0.50 per 1,000 rows). A run that fails before writing rows has no result-row event, and there is no actor-start event. Apify platform usage, if applicable to your account, is shown separately by Apify.

A batch of 100 processed addresses can create up to 100 result events. Set your own run spending limit if you need a stricter ceiling.

Tips

• Start with a small batch and inspect status, confidence, and smtpDeliverable before changing your import rules.
• Keep unknown and catch-all records in a review queue instead of deleting them.
• Use isDisposable as a risk flag, not as a substitute for your organization's acceptance policy.
• Deduplicate your input before a run if duplicate addresses should not create duplicate result rows.
• Retain the result timestamp and your source for each address if you need an audit trail.
• Don't upload an entire contact database just to test the Actor. The prefilled sample shows the output shape.
• Use the dataset's JSON API in automated jobs; use CSV or Excel for a quick review by a person.
• Avoid repeated checks against the same mail host in a short period. Mail providers may throttle or block probes.
• A low-confidence result deserves a second, authorized check. Do not silently relabel it as valid.

Want other data?

Use another Actor when the task is discovery or enrichment rather than verification:

• Google Maps Scraper for public business listing information.
• Google Search Results Scraper for web search result pages.
• LinkedIn People Scraper for public professional profile data where available.
• Browse all Actors by myagizm for other data sources.

Cross-platform data: Apify Store also has Actors for public Instagram, TikTok, LinkedIn, Reddit, YouTube, and Google data. Check each Actor's scope and terms before combining its output with an email list.

MCP and AI agents

The Actor can be called by an AI agent through Apify's MCP integration. Give the agent only the addresses it is allowed to process. Ask it to preserve the unknown and catch-all distinctions and to report counts by status, not to claim that every valid result will reach an inbox.

A useful instruction is: "Verify this authorized test list. Keep the original address in each row, summarize counts by status, and do not treat unknown or catch-all as confirmed deliverable."

Integrations and API

Use the Apify API token from your account's API settings. Do not paste a token into a public document, a task input, or a shared chat.

Run synchronously and wait up to five minutes:

curl -X POST "https://api.apify.com/v2/acts/myagizm~email-verifier/run-sync?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"emails":["test@example.com"],"maxItems":1}'

Start a run asynchronously:

curl -X POST "https://api.apify.com/v2/acts/myagizm~email-verifier/runs?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"emails":["test@example.com"],"maxItems":1}'

Fetch the default dataset after substituting the dataset ID from the run response:

$curl "https://api.apify.com/v2/datasets/$DATASET_ID/items?clean=true&format=json&token=$APIFY_TOKEN"

Apify also supports JavaScript and Python clients, scheduled runs, webhooks, and direct dataset exports. See the Apify API documentation for authentication and run options. For help with this Actor, use its Issues tab.

FAQ

Does the Actor send an email?

No. It performs syntax and DNS checks, then may open an SMTP connection and issue recipient-check commands. It does not send a message body or run an inbox-placement test.

Does valid guarantee delivery?

No. It means the checks accepted the address at run time. The mailbox can change, and the receiving provider can reject a later message.

What does unknown mean?

The domain has a mail route, but the server did not provide enough information to confirm the recipient. Common causes include blocked probes, timeouts, greylisting, or temporary policy responses.

What does catch-all mean?

The server accepted a random recipient that should not exist. Individual mailbox existence cannot be confirmed from that response.

Why can an address be invalid when its syntax is correct?

A syntactically correct address can use a domain without a usable MX record, or the server can explicitly reject the recipient. The status describes the available checks, not the syntax alone.

Why is smtpDeliverable null?

The SMTP exchange did not return a clear recipient-level accept or reject response. Null does not mean false.

Does the Actor verify disposable email?

It flags domains in its disposable-domain set. The list is not exhaustive, so a new or unlisted provider may not be flagged.

Can it identify Gmail, Outlook, or other free providers?

It flags common consumer mail domains in isFreeProvider. A custom domain hosted by a free provider may not be recognized.

Can I submit one address?

Yes. Put it in the emails list as a single string.

Can I submit a CSV file?

The input form accepts a list of strings. For CSV data, extract the address column first or use an integration that supplies an array of strings.

What is the maximum batch size?

Up to 100 addresses per run. maxItems can lower the number processed.

Are duplicate addresses removed?

No. Each submitted occurrence is treated as an input and can produce its own result row. Deduplicate first if you want one row per unique address.

What happens to malformed addresses?

Malformed addresses are skipped before verification, with no dataset row or result charge. Inspect OUTPUT for INPUT_ERROR or the skipped-input details. A syntactically valid address can still produce an invalid/nonexistent-domain verification row.

Why did a real mailbox return unknown?

The provider may block anonymous SMTP recipient checks. This is an inconclusive response, not proof that the mailbox is absent.

Does the Actor use a third-party verification API?

The Actor uses public DNS and SMTP protocol responses. It does not ask for a vendor API key.

Can I use it for a cold-email campaign?

Only process addresses when you have a lawful basis and comply with the rules that apply to your campaign. This Actor does not grant consent or make a list legally permissible.

Does it store my input in the output?

Each result includes the submitted address so you can match it to your list. Do not submit addresses you are not allowed to process. The Actor's operational logs omit the email value and the MX hostname.

Why does the DNS view show a null MX host?

The domain had no MX record available to this run, or the address did not pass syntax parsing. Check hasMx and domain alongside mxHost.

Can I export results?

Yes. Use the dataset export menu for JSON, CSV, Excel, XML, or RSS where supported. The API endpoint can return JSON or other supported formats.

Can I schedule the Actor?

Yes. Apify schedules can run the Actor on a recurring basis. Review the source list and legal basis before each scheduled run.

Does the Actor need a proxy or browser?

No browser or login is needed for DNS and SMTP checks. Mail providers can still restrict server-to-server verification.

How do I avoid charges on an invalid run?

Provide at least one email string. A run with an empty email list finishes SUCCEEDED with zero rows and an INPUT_ERROR reason in OUTPUT. Only result rows create result events.

Where do I report a problem?

Open an issue on the Actor's Apify page and include the run ID, the status, and a sanitized example. Do not post a full contact list or credentials.

Related searches

email verifier · email validator · email verification actor · bulk email verification · email list cleaner · email syntax checker · MX record checker · SMTP email checker · email deliverability check · catch-all email detection · disposable email detector · temporary email domain check · B2B email list validation · validate CRM contacts · verify sales leads · email hygiene tool · check email domain MX · mailbox verification signals · email verification API alternative · Apify email verifier · email address quality check · pre-campaign email validation · email list deduplication workflow · disposable domain lookup · verify email addresses online · SMTP recipient check · email confidence score · DNS email validation · lead list quality check

Disclaimer

This independent Actor is not affiliated with or endorsed by any mail provider or email-service company. It checks only the addresses supplied by the user. You are responsible for having permission to process the data and for complying with privacy, anti-spam, and data-protection laws, including GDPR or CCPA where applicable. Results are time-sensitive and do not guarantee message delivery. Do not use the Actor to send mail, evade provider protections, or build a list of people who have not agreed to be contacted.

Resources

• Apify API documentation
• Apify MCP server
• Exporting dataset data
• Apify schedules
• Apify integrations
• All myagizm Actors

中文说明

Email Verifier 用于检查你提交的邮箱地址，并为每个输入返回一条结构化记录。它检查地址语法、查询域名的 MX 邮件交换记录、标记常见免费邮箱和一次性邮箱域名；如果目标邮件服务器允许，也会进行有限的 SMTP 收件人检查。Actor 不会发送邮件，不需要 API 密钥，也不要求登录。

两分钟内查看第一批结果。先运行预填的保留示例域名，确认输出字段后，再替换成你有权处理的地址。

结果会保留不确定状态。valid、invalid、catch-all 和 unknown 各自代表不同情况。邮件服务器可能接受所有地址、阻止验证探测、启用灰名单，或随时改变策略。SMTP 检查只是一个信号，不保证邮件最终进入收件箱。

目录

• Actor 检查什么
• 适用人群
• 输出字段
• 运行步骤
• 输入示例
• 输出示例
• 准确性和限制
• 价格
• 使用建议
• 其他数据 Actor
• MCP 与 AI Agent
• 集成与 API
• 常见问题
• 相关搜索
• 免责声明
• 资源

Actor 检查什么

• 检查邮箱地址的格式，并通过 syntaxValid 返回结果。
• 查询语法正确的域名是否有 DNS MX 邮件交换记录。
• 返回 DNS 选择的 MX 主机（如果存在）。
• 标记常见免费邮箱服务和已收录的一次性邮箱域名。
• 在服务器允许时检查 SMTP 服务和收件人命令响应。
• 如果服务器接受随机的不存在地址，则标记为 catch-all，不把它误判为某个具体邮箱有效。
• 如果服务器阻止探测或超时，返回 unknown，不伪造确定结论。
• 每个已处理地址写入一行结果；语法错误也会保留为结果。

适用人群

• 在导入 CRM 前清理已获许可的销售线索名单。
• 在发送营销活动前检查依法收集的地址列表。
• 为数据增强或数据质量流程添加邮箱检查步骤的开发者。
• 需要区分语法错误、没有 MX、全收件域和无法确认情况的研究人员。
• 想快速检查少量地址、又不想另行申请验证 API 的小团队。

这个 Actor 不负责发现邮箱，只检查你提供的地址。请仅在有合法依据时处理数据，并遵守适用于你所在地区和名单来源的规则。

输出字段

字段	类型	说明
email	字符串	本条记录对应的原始输入地址。始终返回。
syntaxValid	布尔值	本地语法检查是否通过。始终返回。
status	字符串	valid、invalid、catch-all 或 unknown。始终返回。
confidence	字符串	high、medium 或 low，取决于完成了哪些检查。始终返回。
domain	字符串或 null	从语法正确的地址解析出的域名。解析成功时返回。
hasMx	布尔值	DNS 是否返回 MX 记录。始终返回。
mxHost	字符串或 null	DNS 返回的首选 MX 主机。存在 MX 时返回。
smtpDeliverable	布尔值或 null	SMTP 收件人接受信号；null 表示没有明确回答。
catchAll	布尔值	服务器是否接受随机生成的收件人。
isFreeProvider	布尔值	域名是否属于常见免费邮箱服务。
isDisposable	布尔值	域名是否属于已收录的一次性邮箱服务。

status 总结本次运行观察到的结果，不是未来投递保证。valid 表示本次检查得到接受信号。邮箱之后仍可能停用、满额、被过滤，或因发件信誉和邮件策略而退信。

状态说明

状态	含义
valid	语法和 MX 检查通过，SMTP 收件人检查也得到接受响应。
invalid	语法错误，或可用 DNS/SMTP 结果显示域名或收件人无法接收。
catch-all	服务器接受随机收件人，因此无法确认某个具体邮箱是否存在。
unknown	域名有邮件路由，但服务器没有给出可靠的收件人答案。

运行步骤

1. 打开 Actor。只想看输出结构时，可以保留预填示例。
2. 将 emails 换成你获准处理的地址，表单中每行一个地址。
3. 将 maxItems 设为本次需要处理的数量，最高 100。
4. 启动任务，每个已处理地址返回一行。
5. 查看 Verification results 表格，或切换到 DNS and domain details。也可以从数据集导出 JSON、CSV 或 Excel。
6. 把 unknown 和 catch-all 留在人工复核队列中，不要直接当作确定有效或无效。

每次运行最多处理 100 个地址。没有可用邮箱输入时，Actor 以 SUCCEEDED 状态结束，结果行和结果费用均为零；请在 OUTPUT 中查看 INPUT_ERROR 原因。

输入示例

{
  "emails": [
    "test@example.com",
    "invalid@@example.com",
    "ops@example.com"
  ],
  "maxItems": 3
}

保留的示例域名仅用于查看表单和输出结构，并不代表存在真实邮箱。测试真实邮件系统时，请使用你自己有权使用的测试地址。

输入	类型	默认值	限制
emails	字符串数组	预填示例	每次最多 100 个；格式错误的地址会被跳过，不产生结果行或费用，原因在 OUTPUT 中。
maxItems	整数	100	1–100，限制本次从列表中处理的数量。

输出示例

以下结果来自一次真实 Actor 运行，输入为保留测试地址 test@example.com。这是验证发现，并非确认可投递的邮箱；格式错误的输入在 OUTPUT 中说明，不保存为验证结果行。

[
  {
    "email": "test@example.com",
    "hasMx": false,
    "domain": "example.com",
    "mxHost": null,
    "status": "invalid",
    "catchAll": false,
    "confidence": "high",
    "syntaxValid": true,
    "isDisposable": false,
    "isFreeProvider": false,
    "smtpDeliverable": null
  }
]

示例与保存的真实 Actor 运行结果一致。保留测试域名没有 MX 记录，因此 mxHost 和 smtpDeliverable 都是 null。null 表示没有可用值，不代表 SMTP 拒绝了收件人。

准确性和限制

邮件服务器决定匿名 SMTP 客户端可以获得多少信息。因此，Actor 返回观察到的响应，不能查看邮箱、发送邮件或保证未来投递。

• 域名有 MX 记录，但服务器可能拒绝匿名检查；此时返回 unknown，不代表邮箱已确认有效。
• 全收件域可能接受任意收件人；Actor 返回 catch-all 和较低置信度。
• 灰名单、连接限制、临时故障、网络策略和服务商过滤会阻止结论。
• 一次性域名检测依赖维护列表；新域名可能尚未收录。
• 免费邮箱检测只覆盖常见域名。自定义域名可能由免费服务托管而无法识别。
• 语法检查采用实用规则，不会证明邮箱存在。
• MX 记录可能在运行后发生变化。需要判断时效时，请保存运行时间。
• SMTP 接受收件人命令后，后续邮件仍可能被拒收。发件信誉、邮件内容、身份认证和收件策略都会影响投递。
• Actor 不发送 DATA、不发送邮件正文，也不测试收件箱是否收到邮件。
• 每次运行最多处理 100 个地址。更大的名单应拆分，并确保你有权处理；每条结果都按事件计费。

价格

本 Actor 按事件计费。每一条写入数据集的结果对应一个 apify-default-dataset-item 事件，价格为 每条 $0.0005（每 1,000 条 $0.50）。运行在写入结果前失败时不会产生结果行事件；不收取 Actor 启动事件。Apify 可能单独显示平台使用费用，具体以账户中的计费说明为准。

每次最多 100 条输入，因此最多产生 100 个结果事件。需要更严格上限时，可为运行设置自己的消费限额。

使用建议

• 先运行少量地址，确认 status、confidence 和 smtpDeliverable 的含义，再决定 CRM 导入规则。
• 将 unknown 和 catch-all 放入复核队列，不要直接删除。
• 把 isDisposable 当作风险提示，而不是公司的最终接受规则。
• 如果不想为重复地址生成重复结果，请在运行前自行去重。
• 需要审计时，同时保存运行时间和地址来源。
• 不要为了测试上传整份客户名单；预填示例已展示输出结构。
• 自动化时使用数据集 JSON API；人工检查时可导出 CSV 或 Excel。
• 不要在短时间内反复检查同一邮件主机；服务商可能限流或封锁探测。
• 低置信度结果需要另行复核，不能静默标记为有效。

其他数据 Actor

如果你要找邮箱或补充业务信息，请选择适合的数据来源：

• Google Maps Scraper：公开商家列表信息。
• Google Search Results Scraper：网页搜索结果。
• LinkedIn People Scraper：可访问的公开职业档案数据。
• 查看 myagizm 的全部 Actor。

跨平台数据： Apify Store 也有公开 Instagram、TikTok、LinkedIn、Reddit、YouTube 和 Google 数据 Actor。组合数据前，请检查每个 Actor 的范围和适用条款。

MCP 与 AI Agent

你可以通过 Apify MCP 集成让 AI Agent 调用此 Actor。只传入它获准处理的地址，并要求它保留 unknown 和 catch-all 状态。Agent 应按状态统计数量，不能承诺每个 valid 地址都会投递成功。

示例指令："验证这份获准处理的测试名单。保留每条原始地址，按状态汇总数量，不要把 unknown 或 catch-all 当成已确认可投递。"

集成与 API

从 Apify 账户的 API 设置中获取 API token。不要把 token 写入公开文档、task 输入或共享聊天。

同步运行并最多等待五分钟：

curl -X POST "https://api.apify.com/v2/acts/myagizm~email-verifier/run-sync?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"emails":["test@example.com"],"maxItems":1}'

异步启动运行：

curl -X POST "https://api.apify.com/v2/acts/myagizm~email-verifier/runs?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"emails":["test@example.com"],"maxItems":1}'

将运行响应中的数据集 ID 填入下面的请求：

$curl "https://api.apify.com/v2/datasets/$DATASET_ID/items?clean=true&format=json&token=$APIFY_TOKEN"

Apify 还支持 JavaScript 和 Python 客户端、定时运行、webhook 和数据集导出。认证和运行参数请查看 Apify API 文档。Actor 使用问题请在 Issues 页面提交。

常见问题

Actor 会发送邮件吗？

不会。它检查语法和 DNS，并可能连接 SMTP 服务发送收件人检查命令。它不发送邮件正文，也不测试邮件是否进入收件箱。

valid 是否保证投递？

不保证。它表示本次运行的检查得到接受信号。邮箱之后可能停用，或邮件服务商在实际投递时拒绝邮件。

unknown 是什么意思？

域名有邮件路由，但服务器没有足够信息确认收件人。常见原因包括阻止探测、超时、灰名单或临时策略响应。

catch-all 是什么意思？

服务器接受了一个随机生成的收件地址，因此无法确认某个具体邮箱是否存在。

为什么语法正确却返回 invalid？

地址格式正确，但域名可能没有可用 MX 记录，或服务器明确拒绝该收件人。状态反映检查结果，不只反映语法。

为什么 smtpDeliverable 是 null？

SMTP 对话没有返回明确的接受或拒绝结果。null 不等同于 false。

Actor 能检测一次性邮箱吗？

它会标记已收录的一次性邮箱域名。列表不可能覆盖所有服务，新域名可能尚未被识别。

Actor 能识别 Gmail、Outlook 等免费邮箱吗？

isFreeProvider 会标记常见个人邮箱域名。免费服务托管的自定义域名可能无法识别。

可以只检查一个地址吗？

可以。将它作为一个字符串放在 emails 数组中。

可以上传 CSV 吗？

输入表单接受字符串数组。CSV 需要先提取邮箱列，或使用能将字段传为字符串数组的集成。

每次最多处理多少地址？

最多 100 个。maxItems 可设置更低的数量。

重复地址会自动删除吗？

不会。列表中的每个出现位置都视为一个输入，可能产生重复结果。需要唯一行时请先去重。

格式错误的地址会被丢弃吗？

格式错误的地址会在验证前跳过，不产生结果行或结果费用；OUTPUT 会说明 INPUT_ERROR 或跳过原因。格式正确但域名不存在的地址仍可产生 invalid 验证结果行。

为什么真实邮箱返回 unknown？

邮件服务商可能禁止匿名 SMTP 收件人检查。这个结果无法确认，不证明邮箱不存在。

Actor 使用第三方验证 API 吗？

它使用公共 DNS 和 SMTP 协议响应，不要求你提供第三方服务商 API 密钥。

可以用于冷邮件营销吗？

只有在你有合法依据并遵守适用规则时才可处理地址。Actor 不会提供同意，也不会让名单自动符合营销法规。

我的输入会出现在输出里吗？

会。每条结果包含原始地址，便于与名单匹配。请勿提交无权处理的地址。Actor 的运行日志会省略邮箱值和 MX 主机名。

为什么 DNS 视图中的 MX 主机是 null？

本次查询没有可用 MX 记录，或者地址未通过语法解析。请同时查看 hasMx 和 domain。

可以导出结果吗？

可以。使用数据集导出菜单下载 JSON、CSV、Excel、XML 或 RSS（具体格式取决于 Apify 支持）。API 也可以返回 JSON 等格式。

可以定时运行吗？

可以。Apify schedule 可按周期运行。每次运行前都应重新确认数据来源和处理依据。

Actor 需要代理或浏览器吗？

不需要浏览器或登录。DNS 和 SMTP 检查仍可能受到邮件服务商网络策略限制。

如何避免空运行产生结果费？

至少提交一个邮箱字符串。空列表以 SUCCEEDED 状态结束，不产生结果行或费用；原因在 OUTPUT 中。只有实际保存的验证结果行才产生结果事件。

如何反馈问题？

请在 Apify 页面提交 issue，并提供运行 ID、状态和已脱敏示例。不要贴完整联系人名单或任何凭据。

相关搜索

邮箱验证 · 邮箱校验 · Email Verifier · 批量邮箱验证 · 邮箱列表清理 · 邮箱语法检查 · MX 记录查询 · SMTP 邮箱检查 · 邮件可投递性 · catch-all 邮箱检测 · 一次性邮箱检测 · 临时邮箱域名 · B2B 邮箱名单验证 · CRM 联系人清理 · 销售线索邮箱验证 · 邮箱卫生检查 · 邮箱域名 MX 检查 · 邮箱存在性信号 · 邮箱验证 API 替代方案 · Apify 邮箱验证 Actor · 邮件地址质量检查 · 营销前邮箱校验 · 邮箱列表去重 · 一次性域名查询 · 在线检查邮箱地址 · SMTP 收件人检查 · 邮箱置信度 · DNS 邮箱验证 · 线索名单质量 · 邮箱投递风险

免责声明

此独立 Actor 与任何邮件服务商或邮箱公司无关联，也不代表其认可。它只检查用户提交的地址。你负责确认有权处理数据，并遵守隐私、反垃圾邮件和数据保护法规，包括适用时的 GDPR 或 CCPA。结果有时效性，也不保证实际投递。请勿用它发送邮件、规避服务商保护或建立未经同意的联系名单。

资源

• Apify API 文档
• Apify MCP Server
• 数据集导出
• Apify 定时任务
• Apify 集成
• myagizm 的全部 Actor

Errors & billing

Input errors finish with status SUCCEEDED, no results and no charge; see the OUTPUT record for the reason.

错误与计费

输入错误会以 SUCCEEDED 状态结束，不产生结果且不收费；原因请查看 OUTPUT 记录。