Email Verification
Confirm an email address is correctly formed, actively hosted and able to receive mail before it becomes a bounced onboarding step or a fraud vector.
Overview
What the Email Validation API does
FinHub's Email Validation API checks syntax, MX/domain health and inbox-level deliverability in a single call, so onboarding forms and KYC workflows reject dead or malformed addresses before they cost you a failed OTP or a lost lead. Every check runs against a consent artifact and writes to a tamper-evident audit log, in line with DPDP data-handling requirements.
Inputs
- Email address
- Consent artifact ID
- Check depth (syntax / domain / inbox)
Returns
- Syntax validity
- Domain & MX health
- Inbox existence (deliverability)
- Disposable/role-account flag
- Risk score
POST /v1/email/validate
How it works
Three steps to a verified result
Submit the address
Send the email address with a consent artifact over a single authenticated call.
We check three layers
FinHub validates syntax, resolves MX/domain health and probes inbox-level deliverability without sending mail to the user.
Get a decision-ready result
Receive validity, deliverability and a risk score in real time — sealed to your audit trail.
Use cases
Where teams use Email Validation
- Onboarding form validation for banks, NBFCs and fintechs
- Reducing OTP and welcome-email bounce rates
- Cleaning lead and customer data before KYC
- Screening disposable or role-based addresses at signup
FAQ
Email Validation API — FAQs
Common questions about FinHub's Email Validation API.
It validates syntax, resolves domain and MX health, and confirms whether the inbox actually exists and can receive mail — without sending an email to the user.
More verification APIs
Explore related APIs
Ready to add Email Validation to your flow?
Book a demo and see the API return a verified result on your own test data in minutes.