Check at the point of entry.
Offer a possible typo correction for the person to accept. Keep the original input until they decide, and repeat the lookup when the input changes.
Integrate Email Lookup ↗Email收件人验证
Email validation.
Catch the small mistake.
Check an address before an important message depends on it. Read the verdict, offer a useful correction, and handle uncertain results deliberately.
A small correction. A better beginning.
Inspect a synthetic address, then decide how your application should handle its evidence.
fieldnotes.
Join the studio.
Try alex@gmial.com, alex@gmail.com, neutral@example.com, role@example.com, missing@example.com, or unknown@example.com. Other addresses have no example result.
LOOKUP / SYNTHETIC EVIDENCERead Lookup result meanings ↗
Keep the verdict in context.
Not inspected. Inspect the current address before making a validity decision.
This example has no result for this address. No result can be inferred and no Lookup request was made.
Offer the suggested correction. The customer chooses whether to accept it; after acceptance, inspect the changed address again.
The address-quality evidence is favorable. Check possession, consent and suppressions separately.
This result needs review. Ask the customer to confirm the address; a risk flag or inconclusive mailbox is not proof of delivery.
Continue only with separate possession verification under your reviewed application policy. The uncertainty remains in the record.
Do not send to this example mailbox. Invite the customer to correct the address.
Unknown future verdict. Preserve the result and seek confirmation or another supported signal without automatically accepting or rejecting it.
Companies that trust Bird across their communications.
Read Bird customer storiesUseful evidence before you send.
Keep uncertainty visible.
A risky or unknown verdict needs a deliberate application policy. Validation does not confer marketing permission or override suppression and preference records.
Understand sending restrictions ↗Know more about the address before you send.
在决定发送前了解地址质量。
智能验证流程
使用单地址查询获取判定结果、置信度评分和风险标记。由您的应用决定如何处理这些信息。
全面的检查
检查语法和域名问题、邮箱判定结果和拼写建议。区分无法投递的地址和无法确认的地址。
实时保护
防止表单中提交无效邮件。针对常见拼写错误提供智能建议，帮助用户在注册时填写正确的邮件地址。
应用您的注册策略
在注册策略中使用角色地址和一次性地址标记。免费邮箱提供商标记用于识别个人邮箱，并不意味着该地址无效。
带上下文的置信度
将投递置信度与结果一起查看。独立的 valid 布尔值检查格式和域名配置，因此无法确认邮箱是否存在。
扩展你的邮件验证
Use the API, SDKs or CLI to check addresses in your workflow. Reuse a POST idempotency key within its documented replay window when retrying the same lookup.
一次查询，更清晰的发送决策。
Submit one bare email address, without a display name, and preserve the local part before the @. Read the result, confidence, reason and flags before applying your signup policy. Acceptance here means accepting the address into your workflow; sending still requires consent, preferences and suppression checks.
An answer your application can use.
Offer corrections for the person to confirm. Keep risky, inconclusive and future verdicts subject to a deliberate policy.
validate-address.ts
const answer = await bird.lookup.email({ email: "info@example.com" });
const decision =
answer.result === "undeliverable"
? { action: "reject", reason: answer.reason }
: answer.result === "typo"
? { action: "offer_correction", address: answer.did_you_mean }
: answer.result === "valid"
? { action: "continue_signup" }
: {
action: "review",
result: answer.result,
confidence: answer.delivery_confidence,
flags: answer.flags,
};
console.log(decision);
Run an email lookup with CLI or MCP and inspect the verdict and risk signals. Use those signals in your application policy; they do not verify the person behind an address.
Each answered lookup is billed, including undeliverable results. There is no list-upload or batch endpoint: integrate individual lookups and follow rate limits. Failed requests without an answer are distinct from billed verdicts.
你的验证结果会告诉你什么。
使用文档中记录的判定结果、置信度和风险标记。处理未来可能出现的新结果值，不要将其视为错误。
有效。
该邮箱报告为可接收邮件。继续遵守许可、偏好设置和屏蔽记录。
无法投递。
该地址不接收邮件。发送前检查原因，确认是语法、域名还是收件人问题。
高风险。
该地址可能接收邮件，但存在风险信号，例如角色地址或一次性地址。根据您的发送策略审查其标记。
拼写错误。
该地址疑似拼写错误。向用户展示建议的更正供其确认，不要静默替换其提交的地址。
中性。
无法确认该邮箱是否存在，通常是因为该域名对不同收件人返回相同响应。请结合置信度和您的发送策略判断。
验证在你工作流中的位置。
在注册时检查地址，或将单地址查询整合到列表导入流程中。让用户确认拼写纠正建议。当旧受众回访时重新评估地址质量，并保持联系人、屏蔽和偏好记录的一致性。
付诸实践。
继续查阅此主题的文档、指南和示例。资源为英文。
收件人验证常见问题
如何使用 Bird 验证邮箱地址？
使用 Email Lookup，配合具有 lookup 权限的 API 密钥。提交一个地址并读取其结果、投递置信度、风险标记以及拼写建议。仪表板、SDK 和 CLI 提供了尝试相同查询的方式。
我的集成应处理哪些判定结果？
文档记录的结果有 valid、neutral、risky、undeliverable 和 typo。将 result 视为开放词汇表，使用投递置信度处理未来的新值。单独的 valid 布尔值检查的是地址格式和域设置，而非邮箱是否存在。
收到 typo 或 neutral 结果时该怎么做？
向用户展示拼写建议让其确认；不要默默替换其地址。neutral 表示无法确认也无法否认该邮箱的存在。将结果和置信度与你的同意和发送策略结合使用。
验证能否保证投递成功或发送许可？
不能。查询有助于评估当时的地址质量，但不能建立同意、移除退出偏好或保证进入收件箱。请继续遵守抑制和偏好记录。
我可以在这里上传列表吗？
本页面介绍单地址 Lookup 工作流。对于较大的列表，请将单个查询集成到你的导入流程中并审查结果。如需讨论批量需求请联系销售团队；本页面不提供不受支持的批量上传产品。
How should I format an address?
Submit a bare address, such as person@example.com, without a display name. Keep the local part before the @ unchanged rather than lowercasing the whole address.
How do result, confidence and valid differ?
Result describes the mailbox verdict. Delivery confidence adds evidence for your application policy, including when a result is inconclusive or unfamiliar. The valid boolean only checks address form and domain setup; it does not prove the mailbox exists.
What do reasons and flags tell me?
An undeliverable result includes a reason to investigate, such as an address, domain or recipient problem. Flags describe properties such as role, disposable or free-provider addresses. Treat flags as an open vocabulary; a free-provider flag alone does not make an address invalid.
Which lookups are billed?
Answered lookups are billed, including an undeliverable verdict. A failed request without a lookup answer is different from a negative result. Consult current Lookup pricing and reuse a POST idempotency key within its documented replay window when retrying the same request.
将地址质量付诸实践
将验证与您的联系人数据、发送偏好和投递控制结合使用。
Separate validation from verification
Work through address quality, possession and permission in a signup flow.
联系人和受众
将已验证的地址与用于营销活动的档案和细分一起管理。
屏蔽
在地址检查之外，同时应用退订和屏蔽规则。
投递能力
将地址质量审查纳入更广泛的发送配置中。
Inbox Insights
在检查收件人质量后，查看预估的收件箱到达率。
发送 API
将验证结果接入应用的发送工作流。
邮件概览
探索 Bird Email 的发送、营销活动及更多功能。
Lookup pricing
Review published rates for the lookups your application needs.
Phone number lookup
Check number information before choosing a messaging route.
联系我们的邮件团队
在下次发送前验证收件地址。
讨论验证量、集成方式以及检查应放在邮件工作流的哪个环节。您也可以直接使用 API 开始测试。
创建账户以运行 Email Lookup。在决定发送前查看结果。