Email address validation
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.
Create your account to run an Email Lookup. Review the result before deciding to send.
Email Lookup
Example results
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 delivery confidence alongside the result. The separate valid boolean checks format and domain setup, so it cannot establish that a mailbox exists.
Scale your email validation
Use the API, SDKs or CLI to check addresses in your workflow. Reuse an idempotency key when retrying a POST lookup so the answer is replayed.
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.
- 01
Valid.
The mailbox is reported as accepting mail. Continue to honor consent, preferences and suppression records.
- 02
Undeliverable.
The address does not accept mail. Inspect the reason for a syntax, domain or recipient problem before sending.
- 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.
- 04
Typo.
The address looks misspelled. Offer the suggested correction for the person to confirm; do not silently replace the address they submitted.
- 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 incorporate individual lookups into your list-import process. Let people confirm typo suggestions. Revisit address quality when an older audience returns, and keep your contact, suppression and preference records consistent.
Put it into practice.
Continue with the documentation, guides and examples for this topic. Resources are in English.
Questions about recipient validation
How do I validate an email address with Bird?
Which verdicts should my integration handle?
What should I do with a typo or neutral result?
Does validation guarantee delivery or permission to email?
Can I upload a list here?
Put address quality into practice
Use validation alongside your contact data, sending preferences and delivery controls.
Build validation into your sending workflow.
Check your first address through Lookup, then connect the result to your contact or sending workflow. Discuss larger volumes and integration requirements with our team.
Create your account to run an Email Lookup. Review the result before deciding to send.