Catch address problems
before the next send.

Use Bird Email Lookup to check an address at signup or before a send. Read the verdict, delivery confidence and risk flags, then offer a typo correction or investigate a risky address before it enters your audience.

Email Lookup

Example results

alex@example.com
Verdict
Deliverable
SyntaxValid
MailboxConfirmed
Next stepCheck consent

These are illustrative results, not live lookups. Validation does not establish consent or guarantee delivery.

Validate your email list with confidence.

Understand address quality before you choose to send.

Smart validation process

Use a single-address lookup to receive a verdict, a confidence score and any risk flags. Your application decides what to do with that evidence.

Comprehensive checks

Inspect syntax and domain problems, mailbox verdicts and typo suggestions. Distinguish an undeliverable address from one that could not be confirmed.

Real-time protection

Prevent invalid email submissions on forms. Get smart suggestions for common typos, helping users provide correct email addresses during signup.

Apply your signup policy

Use role and disposable-address flags in your signup policy. A free-provider flag identifies a consumer mailbox; it does not make that address invalid.

Confidence with context

Read result, delivery confidence and risk flags together. The valid boolean carries the provider’s validity assessment and does not guarantee delivery.

Scale your email validation

Check one address or use the batch API for up to 1,000 inputs per request. Keep requests within the documented size limits and match each assessment to its submitted position.

One lookup. A clearer sending decision.

Connect the Email Lookup API to your form or import process. Check the submitted address, read its result and confidence, then decide whether to accept it, request a correction or investigate. Keep consent and suppression checks in the sending workflow as well.

What your validation results tell you.

Use the documented verdict with confidence and risk flags. Handle future result values without treating them as errors.

  1. 01

    Valid.

    The mailbox is reported as accepting mail. Continue to honor consent, preferences and suppression records.

  2. 02

    Undeliverable.

    The address does not accept mail. Inspect the reason for a syntax, domain or recipient problem before sending.

  3. 03

    Risky.

    The address may accept mail but carries risk signals, such as a role or disposable address. Review its flags against your sending policy.

  4. 04

    Typo.

    The address looks misspelled. Offer the suggested correction for the person to confirm; do not silently replace the address they submitted.

  5. 05

    Neutral.

    The mailbox could not be confirmed either way, often because the domain responds the same way for different recipients. Use confidence and your sending policy.

Where validation fits in your workflow.

Check addresses during signup or use batch lookups in your list-import process. Split larger lists to the documented limits and reconcile results in submission order. Let people confirm typo suggestions, and keep consent, suppression and preference records consistent.

Questions about recipient validation

How do I validate an email address with Bird?
Use Email Lookup with an API key scoped for lookup. Submit one address and read its result, delivery confidence, risk flags and any typo suggestion. The dashboard, SDKs and CLI provide ways to try the same lookup.
Which verdicts should my integration handle?
The documented results are valid, neutral, risky, undeliverable and typo. Treat result as an open vocabulary and handle future values using delivery confidence. The valid boolean is the provider’s validity assessment; read it alongside the result and confidence, since it does not guarantee delivery.
What should I do with a typo or neutral result?
Offer a typo suggestion for the person to confirm; never silently replace their address. Neutral means the mailbox could not be confirmed either way. Combine the result and confidence with your consent and sending policy.
Does validation guarantee delivery or permission to email?
No. A lookup helps assess address quality at that moment. It does not establish consent, remove opt-out preferences or guarantee inbox placement. Continue to honor suppression and preference records.
How do I validate a larger list?
Use the batch API to assess up to 1,000 addresses in one request, within the 128 KiB request limit. Results follow submission order, including duplicates. Each answered entry is billed. Check the documented replay limits before retrying a batch; this page does not provide a list-upload control.

Scale without
losing control.

Organize teams in workspaces, control API access, and trace changes through audit logs.

BirdHarborOrganization
WorkspacesProductionSandbox

Delivery agent

API key · Customer operations team
Active
PermissionsAccess
EmailRead & write
SMSRead & write
ALAlex Lee AdminPermissions updated

Audit log

Production
Workspace
Production
Resource
Delivery agent
WhatsApp
Read accessRead & write
Succeeded

Start with Email Lookup.
Build across channels with Bird.

Your next idea.
Ready to connect.