When to use this
Use this when valid users are lost because of mistyped email domains.
How Verifence evaluates it
Email checks combine address parsing, domain intelligence, reachability checks, and your own account rules. The response keeps each signal separate so you can choose a policy that fits a lead form, signup flow, or marketing list instead of treating every flag as the same kind of failure.
Syntax and normalization
The submitted value is trimmed, normalized, and checked as an email address before deeper analysis begins.
Disposable and free providers
The domain is compared with Verifence data for temporary inbox services, known public providers, and free-email domains.
Role accounts
Local parts such as info@, admin@, support@, sales@, and billing@ are identified so B2B teams can review them separately.
Domain reachability
Verifence checks whether the domain has usable mail or address records. A failed or timed-out DNS lookup is returned as unknown rather than automatically counted against the address.
Typo correction
Common mistakes in Gmail, Hotmail, Yahoo, and other domains can return a suggested corrected address instead of forcing you to discard the lead.
Account policy
API checks can also apply custom email, domain, TLD, IP, wildcard-IP, and country rules configured for the account.
How to do it
- 01 Send the address to the real-time email endpoint before saving the signup or lead.
- 02 Check did_you_mean instead of guessing corrections in browser code or silently rewriting the submitted value.
- 03 Show the suggested address next to the original and ask the visitor to confirm which one they intended.
- 04 Rescan the confirmed correction when the address is part of a high-value signup or lead workflow.
- 05 Store the confirmed address and preserve the original only where it helps support or audit the correction.
How to act on the result
Keep addresses with valid syntax, no blocking rule, no disposable flag, and a reachable or trusted domain.
When did_you_mean is present, show the suggestion to the visitor or fix the row only after confirming the intended address.
Role accounts, public domains, and unknown DNS results often need business context rather than an automatic rejection.
Reject malformed addresses, known disposable providers, unreachable domains, or anything matched by an explicit account rule.
Implementation notes
- A single email check costs 1 credit. The bulk API accepts up to 500 addresses per request and charges unique addresses that receive a result.
- The web app accepts pasted addresses or CSV, TXT, XLS, and XLSX uploads, with a configured limit of up to 100,000 valid rows and 100 MB per submission.
- Bulk jobs run in the background and expose progress, clean and flagged totals, category counts, and a downloadable results CSV.