Back to Details

sales-zerobounce

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

ZeroBounce Platform Help

ZeroBounce平台帮助

Help the user with ZeroBounce platform questions — from email validation and list cleaning through AI scoring, activity data, inbox placement testing, blacklist monitoring, DMARC monitoring, email warmup, API integration, and email finder.
ZeroBounce is an email validation and deliverability platform with 99.6% accuracy across 30+ email status types. SOC 2 Type 2 and ISO-27001 certified, GDPR/HIPAA/CCPA compliant. Core strengths: bulk and real-time email validation, AI-powered catch-all scoring, activity data for engagement tracking, inbox placement testing, blacklist monitoring, DMARC monitoring, and email warmup.
为用户解答ZeroBounce平台相关问题——涵盖邮件验证与列表清理、AI评分、活动数据、收件箱投递测试、黑名单监控、DMARC监控、邮箱预热、API集成以及邮箱查找等内容。
ZeroBounce是一款邮件验证与送达性平台，在30+种邮件状态类型上的准确率达99.6%。该平台拥有SOC 2 Type 2和ISO-27001认证，符合GDPR/HIPAA/CCPA合规要求。核心优势包括：批量与实时邮件验证、AI驱动的catch-all评分、用于参与度追踪的活动数据、收件箱投递测试、黑名单监控、DMARC监控以及邮箱预热。

Step 1 — Gather context

步骤1 — 收集上下文

If 
references/learnings.md
exists, read it first for accumulated knowledge.
Ask the user:
  1. What area of ZeroBounce do you need help with?
    • A) Email Validation — bulk list cleaning or real-time API verification
    • B) Email Finder — B2B email discovery by name + domain
    • C) Email Scoring (AI) — catch-all validation and engagement scoring
    • D) Activity Data — subscriber engagement tracking
    • E) Inbox Placement Testing — test email configs and inbox vs. spam placement
    • F) Blacklist Monitoring — IP/domain blacklist checks across 200+ providers
    • G) DMARC Monitor — domain authentication monitoring and policy setup
    • H) Email Warmup — domain/IP reputation building
    • I) API & SDKs — programmatic access, automation
    • J) Integrations — HubSpot, Salesforce, Mailchimp, Zapier, etc.
    • K) Account & Billing — credits, pricing, plans
    • L) Something else — describe it
  2. What's your role?
    • A) Sales rep / AE / BDR
    • B) Sales manager / team lead
    • C) RevOps / Sales Ops
    • D) Marketer / Email marketer
    • E) Admin / IT
    • F) Founder / solo seller
    • G) Other
  3. What are you trying to accomplish? (describe your specific goal — e.g., "clean 100K contacts before a HubSpot campaign", "set up blacklist monitoring for 5 sending IPs", "validate catch-all addresses with AI scoring")
If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.
如果
references/learnings.md
文件存在，请先阅读以获取累积知识。
询问用户：
  1. 你需要ZeroBounce哪方面的帮助？
    • A) 邮件验证——批量列表清理或实时API验证
    • B) 邮箱查找——通过姓名+域名发现B2B邮箱
    • C) 邮件评分（AI）——catch-all验证与参与度评分
    • D) 活动数据——订阅者参与度追踪
    • E) 收件箱投递测试——测试邮件配置及收件箱/垃圾邮件投放情况
    • F) 黑名单监控——在200+个服务商处检查IP/域名是否被列入黑名单
    • G) DMARC监控——域名认证监控与策略设置
    • H) 邮箱预热——域名/IP信誉构建
    • I) API与SDK——程序化访问、自动化
    • J) 集成——HubSpot、Salesforce、Mailchimp、Zapier等
    • K) 账户与计费——积分、定价、套餐
    • L) 其他——请描述
  2. 你的角色是什么？
    • A) 销售代表/AE/BDR
    • B) 销售经理/团队主管
    • C) RevOps/Sales Ops
    • D) 营销人员/邮件营销人员
    • E) 管理员/IT人员
    • F) 创始人/个体销售者
    • G) 其他
  3. 你想要达成什么目标？（描述你的具体目标——例如："在HubSpot活动前清理10万条联系人数据"、"为5个发送IP设置黑名单监控"、"用AI评分验证catch-all地址"）
**如果用户的请求已提供大部分此类上下文，请直接跳至相关步骤。**先基于合理假设（明确说明）给出最佳答案，最后仅询问最关键的1-2个澄清问题——不要要求收集完整上下文后才提供响应。

Step 2 — Route or answer directly

步骤2 — 转接或直接解答

If the request maps to a specialized skill, route:
  • General deliverability strategy (SPF/DKIM/DMARC, warmup planning, inbox placement strategy) → 
    /sales-deliverability
  • Enrichment strategy across tools (waterfall enrichment, CRM hygiene) → 
    /sales-enrich
  • Building prospect lists / ICP definition → 
    /sales-prospect-list
  • Connecting tools via Zapier/webhooks generically → 
    /sales-integration
Otherwise, answer directly from platform knowledge using the reference below.
如果请求对应某个专业技能，请转接：
  • 通用送达策略（SPF/DKIM/DMARC、预热规划、收件箱投递策略）→ 
    /sales-deliverability
  • 跨工具enrichment策略（瀑布式enrichment、CRM数据清洁）→ 
    /sales-enrich
  • 构建潜在客户列表/ICP定义 → 
    /sales-prospect-list
  • 通过Zapier/webhooks通用连接工具 → 
    /sales-integration
否则，直接基于平台知识及下方参考内容解答。

Step 3 — ZeroBounce platform reference

步骤3 — ZeroBounce平台参考资料

Read 
references/platform-guide.md
 for detailed module documentation, pricing, integrations, and data model.
You no longer need the platform guide details — focus on the user's specific situation.
**阅读
references/platform-guide.md
**获取详细的模块文档、定价、集成及数据模型信息。
你无需关注平台指南的细节——专注于用户的具体情况即可。

Step 4 — Actionable guidance

步骤4 — 可执行指导

Based on the user's specific question, provide step-by-step instructions:
根据用户的具体问题，提供分步说明：

Bulk list validation workflow

批量列表验证工作流

  1. Prepare your list: Export contacts as CSV with one email per row. Remove duplicates to save credits.
  2. Upload: Log in to ZeroBounce → Bulk Email Validator → upload your CSV file. Or use 
    POST /v2/sendfile
    via the API.
  3. Wait for processing: ZeroBounce processes the list asynchronously. Check status via the dashboard or 
    GET /v2/filestatus
    .
  4. Review results: Download results via the dashboard or 
    GET /v2/getfile
    . Review the breakdown by status (Valid, Invalid, Catch-All, Spam Trap, Abuse, Disposable, Unknown, Do Not Mail).
  5. Handle catch-all addresses: Run AI Scoring on catch-all results. Set a score threshold (7+ recommended) for inclusion.
  6. Download clean list: Export Valid emails (and high-scoring catch-all) for campaigns.
  7. Import to your campaign tool: Upload the clean list to your ESP, CRM, or campaign platform.
  8. Re-verify regularly: Re-validate every 3 months or before any major campaign.
  1. 准备列表：将联系人导出为CSV格式，每行一个邮箱。移除重复项以节省积分。
  2. 上传：登录ZeroBounce → 批量邮件验证器 → 上传你的CSV文件。或通过API调用
    POST /v2/sendfile
    。
  3. 等待处理：ZeroBounce异步处理列表。通过仪表盘或
    GET /v2/filestatus
    检查状态。
  4. 查看结果：通过仪表盘或
    GET /v2/getfile
    下载结果。查看按状态分类的明细（有效、无效、Catch-All、垃圾邮件陷阱、滥用、一次性邮箱、未知、请勿邮件）。
  5. 处理Catch-All地址：对Catch-All结果运行AI评分。设置评分阈值（建议7分及以上）以筛选纳入的地址。
  6. 下载清洁列表：导出有效邮箱（及高评分Catch-All地址）用于营销活动。
  7. 导入至营销工具：将清洁列表上传至你的ESP、CRM或活动平台。
  8. 定期重新验证：每3个月或任何大型活动前重新验证一次。

Real-time API validation setup

实时API验证设置

  1. Get your API key: Log in to ZeroBounce → API settings → copy your API key.
  2. Choose your region: Default (
    api.zerobounce.net
    ), US (
    api-us.zerobounce.net
    ), or EU (
    api-eu.zerobounce.net
    ).
  3. Integrate: Call 
    GET /v2/validate?api_key=YOUR_KEY&email=user@example.com
    for single validation, or 
    POST /v2/validatebatch
    for up to 200 at once.
  4. Handle responses: Check the 
    status
    field — route Valid emails to your system, reject Invalid/Spam Trap/Abuse/Disposable, and flag Catch-All for AI Scoring.
  5. Use an SDK: ZeroBounce offers 13 official SDKs — use the one for your language instead of raw HTTP calls.
  6. Monitor usage: Check credits with 
    GET /v2/getcredits
    and usage with 
    GET /v2/getusage
    .
  1. 获取API密钥：登录ZeroBounce → API设置 → 复制你的API密钥。
  2. 选择区域：默认（
    api.zerobounce.net
    ）、美国（
    api-us.zerobounce.net
    ）或欧盟（
    api-eu.zerobounce.net
    ）。
  3. 集成：调用
    GET /v2/validate?api_key=YOUR_KEY&email=user@example.com
    进行单个验证，或调用
    POST /v2/validatebatch
    批量验证最多200个邮箱。
  4. 处理响应：检查
    status
    字段——将有效邮箱导入你的系统，拒绝无效/垃圾邮件陷阱/滥用/一次性邮箱，标记Catch-All地址以进行AI评分。
  5. 使用SDK：ZeroBounce提供13个官方SDK——使用对应语言的SDK而非直接HTTP调用。
  6. 监控使用情况：通过
    GET /v2/getcredits
    检查积分，通过
    GET /v2/getusage
    查看使用情况。

Blacklist monitoring setup

黑名单监控设置

  1. Add your IPs and domains: In ZeroBounce → Blacklist Monitor → add all sending IPs (IPv4 and IPv6) and domains.
  2. Configure alerts: Set up email or webhook notifications for blacklist events.
  3. Review initial scan: ZeroBounce runs an initial check — review any existing blacklist entries.
  4. Act on alerts: When you receive a blacklist alert, identify the blacklist provider, check their delisting process, and submit a delisting request. Cross-reference with recent sending activity to find the cause.
  5. Monitor continuously: Check the dashboard regularly — some blacklists auto-expire, others require manual delisting.
  1. 添加IP和域名：在ZeroBounce → 黑名单监控 → 添加所有发送IP（IPv4和IPv6）及域名。
  2. 配置警报：设置黑名单事件的邮件或webhook通知。
  3. 查看初始扫描结果：ZeroBounce会进行初始检查——查看任何已存在的黑名单条目。
  4. 响应警报：收到黑名单警报时，识别黑名单服务商，查看其移除流程并提交移除请求。结合近期发送活动交叉查找原因。
  5. 持续监控：定期查看仪表盘——部分黑名单会自动过期，其他则需要手动移除。

DMARC monitoring setup

DMARC监控设置

  1. Add your domains: In ZeroBounce → DMARC Monitor → add all domains you send email from.
  2. Publish DMARC record: If you don't have a DMARC record yet, start with 
    v=DMARC1; p=none; rua=mailto:your-dmarc-reports@yourdomain.com
    . ZeroBounce provides the correct record to publish.
  3. Monitor reports: Review DMARC aggregate reports in the dashboard — identify all authorized senders.
  4. Tighten policy gradually: Once you've identified all legitimate senders, move from p=none → p=quarantine → p=reject over weeks/months.
  5. Watch for suspicious activity: Act on alerts about unauthorized senders spoofing your domain.
  1. 添加域名：在ZeroBounce → DMARC监控 → 添加所有你用于发送邮件的域名。
  2. 发布DMARC记录：如果你还没有DMARC记录，从
    v=DMARC1; p=none; rua=mailto:your-dmarc-reports@yourdomain.com
    开始。ZeroBounce会提供正确的记录供你发布。
  3. 监控报告：在仪表盘中查看DMARC汇总报告——识别所有授权发送方。
  4. 逐步收紧策略：识别所有合法发送方后，在数周/数月内将策略从p=none → p=quarantine → p=reject逐步调整。
  5. 警惕可疑活动：针对伪造你域名的未授权发送方警报采取行动。

Email warmup workflow

邮箱预热工作流

  1. Connect your email account: In ZeroBounce → Email Warmup → connect the Gmail or Outlook account you want to warm up.
  2. Configure settings: Set daily send volume targets and ramp-up schedule.
  3. Start warmup: ZeroBounce begins automated engagement — sending, opening, replying, and rescuing from spam.
  4. Monitor progress: Check warmup metrics in the dashboard — delivery rates, inbox placement rates.
  5. Run inbox placement tests: After 2-3 weeks, run placement tests to verify reputation improvement.
  6. Transition to campaigns: Once warmup metrics stabilize, begin sending real campaigns at low volume and gradually increase.
  1. 连接邮箱账户：在ZeroBounce → 邮箱预热 → 连接你想要预热的Gmail或Outlook账户。
  2. 配置设置：设置每日发送量目标和递增计划。
  3. 开始预热：ZeroBounce开始自动互动——发送、打开、回复邮件，并将邮件从垃圾邮件中救出。
  4. 监控进度：在仪表盘中查看预热指标——送达率、收件箱投递率。
  5. 运行收件箱投递测试：2-3周后，运行投递测试以验证信誉提升情况。
  6. 过渡至营销活动：预热指标稳定后，开始以低发送量发送真实活动邮件，并逐步增加发送量。

Gotchas

注意事项

Best-effort from research — review these, especially items about pricing, credit costs, and API behavior that may have changed.
  • Don't treat Catch-All as Valid or Invalid. Catch-all domains accept all emails at the SMTP level, so ZeroBounce cannot confirm individual mailbox existence through standard validation alone. Don't blindly include them (risking bounces) or blindly exclude them (losing valid prospects). Use AI Scoring to evaluate catch-all addresses individually — it's what the feature was designed for.
  • Don't underestimate Email Finder credit cost. At 20 credits per successful find, a batch of 500 lookups can cost up to 10,000 credits — equivalent to validating 10,000 emails. Budget Email Finder usage separately from validation credits. If you need high-volume email discovery, compare the per-find cost against dedicated email finder tools.
  • Don't forget about regional API endpoints. ZeroBounce offers US and EU regional endpoints in addition to the default. If you have data residency requirements (GDPR), use the EU endpoint (
    api-eu.zerobounce.net
    ). If latency matters, use the regional endpoint closest to your infrastructure. The default endpoint works globally but may not satisfy compliance requirements.
  • Don't ignore the 80K/hour rate limit on credit endpoints. At 80,000 requests per hour, you can process ~22 emails per second via real-time validation. For large lists, use bulk upload (
    POST /v2/sendfile
    ) instead of hammering the real-time endpoint — bulk is async and handles scale better. Use batch validation (
    POST /v2/validatebatch
    for up to 200 at a time) as a middle ground.
  • Don't warm up and campaign simultaneously from the same account. Email warmup builds reputation through controlled engagement patterns. Sending live campaigns during warmup disrupts these patterns and can hurt rather than help. Finish warmup first (2-4 weeks), then transition to live sending gradually.
  • Self-improving: If you discover something not covered here, append it to 
    references/learnings.md
    with today's date.
基于研究的最佳实践——请重点关注定价、积分成本及API行为等可能发生变化的内容。
  • 不要将Catch-All视为有效或无效。Catch-All域在SMTP层面接受所有邮件，因此ZeroBounce无法仅通过标准验证确认单个邮箱是否存在。不要盲目纳入这些地址（存在退信风险）或盲目排除（错失有效潜在客户）。使用AI评分逐个评估Catch-All地址——这正是该功能的设计初衷。
  • 不要低估邮箱查找的积分成本。每成功找到一个邮箱需消耗20积分，500次批量查找最多可能消耗10,000积分——相当于验证10,000个邮箱。将邮箱查找的使用预算与验证积分分开。如果需要大量邮箱发现服务，比较单条查找成本与专用邮箱查找工具的差异。
  • 不要忘记区域API端点。除默认端点外，ZeroBounce还提供美国和欧盟区域端点。如果你有数据驻留要求（如GDPR），请使用欧盟端点（
    api-eu.zerobounce.net
    ）。如果延迟很重要，请使用离你的基础设施最近的区域端点。默认端点适用于全球范围，但可能无法满足合规要求。
  • 不要忽视积分端点的80K/小时速率限制。每小时最多80,000次请求，实时验证每秒可处理约22个邮箱。对于大型列表，请使用批量上传（
    POST /v2/sendfile
    ）而非频繁调用实时端点——批量处理是异步的，更适合大规模操作。使用批量验证（
    POST /v2/validatebatch
    ，最多200个邮箱）作为折中方案。
  • 不要在同一账户同时进行预热和营销活动。邮箱预热通过可控的互动模式构建信誉。预热期间发送实时活动邮件会打乱这些模式，反而可能损害信誉。先完成预热（2-4周），再逐步过渡到实时发送。
  • 自我改进：如果发现此处未涵盖的内容，请将其添加到
    references/learnings.md
    中，并标注日期。

Step 5 — Related skills

步骤5 — 相关技能

  • /sales-deliverability
    — Email deliverability strategy across tools (SPF/DKIM/DMARC, warmup planning, inbox placement, bounce management)
  • /sales-enrich
    — Enrichment strategy across tools (waterfall enrichment, CRM hygiene, credit optimization)
  • /sales-prospect-list
    — Build targeted prospect lists with ICP definition and segmentation
  • /sales-integration
    — Connect ZeroBounce to CRM and other tools via Zapier or direct integrations
  • /sales-do
    — Not sure which skill to use? The router matches any sales objective to the right skill. Install: 
    npx skills add sales-skills/sales --skill sales-do
  • /sales-deliverability
    ——跨工具的邮件送达性策略（SPF/DKIM/DMARC、预热规划、收件箱投递、退信管理）
  • /sales-enrich
    ——跨工具的enrichment策略（瀑布式enrichment、CRM数据清洁、积分优化）
  • /sales-prospect-list
    ——通过ICP定义和细分构建目标潜在客户列表
  • /sales-integration
    ——通过Zapier或直接集成将ZeroBounce连接到CRM及其他工具
  • /sales-do
    ——不确定使用哪个技能？路由工具会将任何销售目标匹配到合适的技能。安装方式：
    npx skills add sales-skills/sales --skill sales-do

Examples

示例

Example 1: Cleaning an email list before a HubSpot campaign

示例1：HubSpot活动前清理邮件列表

User says: "I have 50,000 contacts in HubSpot and want to verify them before sending a product launch email." Skill does:
  1. Recommends exporting the HubSpot contact list as CSV
  2. Walks through uploading to ZeroBounce for bulk validation (50,000 credits needed)
  3. Explains how to interpret results — remove Invalid, Spam Trap, Abuse, Disposable, and Do Not Mail
  4. Recommends running AI Scoring on Catch-All results (set threshold at 7+ for inclusion)
  5. Points to the native HubSpot integration as an alternative to manual export/import Result: Clean, verified list re-imported to HubSpot with invalid and risky addresses removed, catch-all addresses scored and filtered
用户提问："我在HubSpot中有50,000条联系人数据，想在发送产品发布邮件前验证它们。" 技能操作：
  1. 建议将HubSpot联系人列表导出为CSV格式
  2. 引导完成上传至ZeroBounce进行批量验证（需50,000积分）
  3. 解释如何解读结果——移除无效、垃圾邮件陷阱、滥用、一次性邮箱及请勿邮件地址
  4. 建议对Catch-All结果运行AI评分（设置7分及以上的阈值以纳入）
  5. 指出原生HubSpot集成作为手动导出/导入的替代方案 结果：清洁、已验证的列表重新导入HubSpot，移除了无效和高风险地址，Catch-All地址经过评分和筛选

Example 2: Setting up blacklist monitoring for sending infrastructure

示例2：为发送基础设施设置黑名单监控

User says: "We send from 3 IPs and 2 domains — I want to know immediately if we get blacklisted." Skill does:
  1. Walks through adding all 3 IPs (IPv4 and/or IPv6) and 2 domains to Blacklist Monitor
  2. Configures email and webhook alerts for immediate notification
  3. Explains the 200+ blacklist providers covered and the difference between auto-expiring and manual-delist lists
  4. Recommends pairing with DMARC Monitor for complete domain authentication monitoring
  5. Advises cross-referencing any blacklist hits with recent sending activity to identify the cause Result: 24/7 blacklist monitoring across 200+ providers for all sending IPs and domains, with immediate alerts
用户提问："我们从3个IP和2个域名发送邮件——我想在被列入黑名单时立即收到通知。" 技能操作：
  1. 引导将所有3个IP（IPv4和/或IPv6）和2个域名添加到黑名单监控中
  2. 配置邮件和webhook警报以实现即时通知
  3. 解释覆盖的200+黑名单服务商，以及自动过期和手动移除列表的区别
  4. 建议搭配DMARC监控以实现完整的域名认证监控
  5. 建议将任何黑名单命中情况与近期发送活动交叉对比以找出原因 结果：对所有发送IP和域名进行24/7黑名单监控（覆盖200+服务商），并提供即时警报

Example 3: Using the API to validate emails in real-time at signup

示例3：使用API在注册时实时验证邮箱

User says: "I want to add email validation to our signup form so fake emails don't enter our database." Skill does:
  1. Recommends the real-time validation endpoint 
    GET /v2/validate
    or batch endpoint for form submissions
  2. Shows authentication setup with the 
    api_key
    parameter
  3. Advises blocking Invalid, Disposable, Spam Trap, and Abuse statuses at the form level
  4. Recommends using the regional API endpoint closest to the user's infrastructure for lowest latency
  5. Suggests an SDK (13 available) for the user's backend language rather than raw HTTP calls
  6. Calculates credit usage based on expected signup volume Result: Real-time form validation preventing invalid, disposable, and risky emails from entering the database
用户提问："我想在注册表单中添加邮箱验证功能，防止虚假邮箱进入我们的数据库。" 技能操作：
  1. 建议使用实时验证端点
    GET /v2/validate
    或批量端点处理表单提交
  2. 展示使用
    api_key
    参数的认证设置
  3. 建议在表单层面拦截无效、一次性、垃圾邮件陷阱及滥用状态的邮箱
  4. 建议使用离用户基础设施最近的区域API端点以实现最低延迟
  5. 推荐使用对应后端语言的SDK（提供13种）而非直接HTTP调用
  6. 根据预期注册量计算积分使用情况 结果：实时表单验证可防止无效、一次性及高风险邮箱进入数据库

Troubleshooting

故障排除

High percentage of Catch-All results

Catch-All结果占比过高

Symptom: A large portion of your list comes back as Catch-All, making it hard to judge list quality. Cause: Many corporate domains configure catch-all mail servers that accept all addresses — standard validation cannot confirm individual mailbox existence on these domains. Solution: Run AI Scoring on all Catch-All results. Set a threshold score (7+ recommended) for inclusion in campaigns. Monitor bounce rates for scored addresses and adjust your threshold over time. If most of your list is catch-all, it likely skews toward large enterprises — this is normal.
症状：列表中大部分地址返回Catch-All状态，难以判断列表质量。 原因：许多企业域名配置了catch-all邮件服务器，接受所有地址——标准验证无法确认这些域名上的单个邮箱是否存在。 解决方案：对所有Catch-All结果运行AI评分。设置评分阈值（建议7分及以上）以筛选纳入营销活动的地址。监控已评分地址的退信率，并随时间调整阈值。如果你的列表大部分是catch-all地址，它可能偏向大型企业——这属于正常情况。

Bulk validation job stuck or slow

批量验证任务停滞或缓慢

Symptom: Uploaded a CSV for bulk validation but the job status shows "processing" for an extended period. Cause: Large lists take longer to process. Network issues during upload can cause incomplete file transfers. Malformed CSV formatting can slow processing. Solution: Check job status via the dashboard or 
GET /v2/filestatus
. For large lists (100K+), processing can take hours — this is normal. If stuck for more than 24 hours, delete the file with 
GET /v2/deletefile
and re-upload. Ensure your CSV is properly formatted with one email per row and no special characters in the email column.
症状：上传CSV进行批量验证，但任务状态长时间显示"处理中"。 原因：大型列表处理时间更长。上传期间的网络问题可能导致文件传输不完整。格式错误的CSV会减慢处理速度。 解决方案：通过仪表盘或
GET /v2/filestatus
检查任务状态。对于大型列表（10万+），处理可能需要数小时——这属于正常情况。如果停滞超过24小时，使用
GET /v2/deletefile
删除文件并重新上传。确保你的CSV格式正确，每行一个邮箱，邮箱列无特殊字符。

API returning "Unknown" status for many emails

API对大量邮箱返回"Unknown"状态

Symptom: Real-time validation returns "Unknown" status for a significant percentage of emails. Cause: The receiving mail server timed out or returned an ambiguous response. Greylisting by the recipient server can cause temporary Unknown results. Network issues between ZeroBounce and the recipient server. Solution: Retry Unknown emails after a few hours — greylisting typically resolves on subsequent attempts. If Unknown rates remain high for a specific domain, that domain's mail server may be aggressively blocking verification attempts. Do not treat Unknown as Valid — exclude from campaigns or retry before sending.
症状：实时验证对大量邮箱返回"Unknown"状态。 原因：接收邮件服务器超时或返回模糊响应。收件人服务器的灰名单机制可能导致临时Unknown结果。ZeroBounce与收件人服务器之间的网络问题。 解决方案：数小时后重试Unknown邮箱——灰名单问题通常在后续尝试中解决。如果某个域名的Unknown率持续较高，该域名的邮件服务器可能在积极阻止验证请求。不要将Unknown视为有效——从营销活动中排除或在发送前重试。