01 / 04
Start with an address you can use.
Signup, confirmation, recovery, notifications, support, and sales can all depend on one field being usable.
emailverifier.dev helps you spot invalid addresses, disposable inboxes, and likely typos before creating an account or importing a contact.
See how checks workCHECK
THE
WHOLE
ADDRESS.
One request checks the address and returns a recommended action with the reasons behind it.
01 / 04
Signup, confirmation, recovery, notifications, support, and sales can all depend on one field being usable.
02 / 04
Look at structure, mail routing, provider type, risk signals, and, when available, mailbox acceptance and catch-all behavior.
03 / 04
A confirmed failure, a risk signal, and an unknown mailbox result each need different handling. The response keeps them separate.
04 / 04
Ask for a correction when an address is invalid, suggest a fix for a likely typo, and send a confirmation email when inbox ownership matters.
Your signup rules
An invalid address needs a correction. A disposable inbox may conflict with your trial policy. An uncertain mailbox result may need email confirmation. The response gives you the detail to handle each case.
The API recommends allow, review, or block. Your application decides what happens next. Verification does not prove inbox ownership or guarantee that a message will arrive.
01
Check the address format, likely typos, whether the domain can receive mail, and known provider risks. Mailbox acceptance and catch-all checks are included when available.
02
Correct a likely typo, block a confirmed failure, apply your own disposable-address policy, or require confirmation when inbox access matters.
03
Start with 1,000 non-expiring credits on your first project. Add 20,000 more for $10 whenever you need them.
Create your first project with 1,000 non-expiring starter credits. No card required.