Stop typos and hard bounces before they hurt your sender reputation.

Validate email addresses on your signup forms and clean imported audience lists before launching a broadcast. Bird Email Lookup checks domain MX records and mailbox reachability in real time or in batches of up to 1,000 addresses, catching misspelled domains with inline correction suggestions and flagging disposable or role accounts before they damage your inbox placement.

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.

Keep bad addresses out of your forms and campaigns.

Catch signup mistakes inline, filter throwaway accounts, and clean imported lists before a high bounce rate hurts your domain reputation.

Inline typo suggestions at signup

Spot misspelled domains like gmial.com as users fill out your signup or checkout form and return a suggested correction they can confirm with one click.

Syntax, MX, and mailbox checks

Verify that an address is properly formatted, its domain publishes valid mail servers, and the recipient mailbox actually accepts incoming mail.

Disposable and role-address detection

Flag throwaway inbox services that expire after signup alongside shared team aliases like support@ or info@ that carry higher complaint risk.

Work and personal email filtering

Distinguish consumer mailboxes such as Gmail or Yahoo from company domains so B2B signup and trial flows can prompt for a work address when needed.

0 to 100 delivery confidence scores

Pair the verdict with a numeric confidence score from 0 to 100 so your app can set clear thresholds for transactional alerts versus promotional broadcasts.

1,000-address batch cleaning

Validate one address inline during registration or scrub up to 1,000 addresses per request when importing a CRM list or preparing a campaign audience.

Fix signup typos inline before you send a welcome email.

A single mistyped character on a registration or checkout form means a missed verification code, a lost order receipt, and an immediate hard bounce against your domain. Calling Email Lookup when a user submits their address lets your form catch dead domains right away, offer a suggested fix for common misspellings, and block disposable inboxes from abusing free trials.

Five clear verdicts to drive your signup and sending rules.

Each lookup returns a verdict, a 0 to 100 delivery confidence score, and specific risk flags so your app knows whether to send, prompt the user, or skip the address.

  1. 01

    Valid.

    The domain and mailbox accept incoming mail. Proceed with your welcome flow or campaign send while continuing to respect the contact’s opt-in preferences and suppression status.

  2. 02

    Undeliverable.

    The address cannot receive mail because of broken syntax, a non-existent domain, or a missing mailbox. Block the address before sending so it does not trigger a hard bounce.

  3. 03

    Risky.

    The mailbox likely accepts mail, though risk flags indicate a disposable inbox, a shared role alias like info@, or a low-reputation address that is likelier to bounce or report spam.

  4. 04

    Typo.

    The domain looks misspelled and the response includes a suggested correction. Show the suggestion inline so the user can confirm what they meant before you save the contact.

  5. 05

    Neutral.

    The receiving server accepts mail for the domain without confirming individual mailboxes. Combine the delivery confidence score with your own sending threshold.

Clean imported audience lists before launching a broadcast.

List decay and unverified CSV imports can spike your bounce rate and push your sending domain into spam folders at Gmail, Outlook, and Yahoo. Before you launch a campaign to a migrated list or an event signup sheet, run the addresses through the batch endpoint in chunks of up to 1,000. You get results back in submission order, making it straightforward to filter out undeliverable contacts and review risky ones before a broadcast leaves your workspace.

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.

Start with Email Lookup.
Build across channels with Bird.

Start building with Bird in minutes.