Official Email Verification for Salaried Loans: A Guide
Last reviewed: November 2026
Official email verification for salaried loans is the check that an applicant controls a mailbox on their declared employer's genuine email domain. Without it, lenders rely on offer letters and payslips that take minutes to fake, or on human resources (HR) calls that take days.
This guide is for heads of underwriting and heads of fraud control at non-banking financial companies (NBFCs), banks and fintech lenders. It explains which email checks prove employment, how to spot a fake employer domain, what to pass or refer, and how the Digiqt Lending Platform runs the flow.
Key Takeaways
- A one-time password (OTP) proves a mailbox, not a job. The domain must also belong to the declared employer.
- Domain age and mail records expose most fake employers. A domain registered last month rarely belongs to a company with three years of payroll.
- Forwarded HR emails only count when authenticated. Screenshots prove nothing.
- The whole check can be made systematic, with every result stored and only mismatches sent to a reviewer.
What Is Official Email Verification for Salaried Loans?
Official email verification for salaried loans links three facts: the applicant, a working mailbox, and an email domain owned by the declared employer. It complements employer risk tiers in our guide to employer categorisation for salaried loans, which decides how much to trust the employer once employment is proven.
Fintech practitioners already treat the work email as a fraud signal. Writing in Analytics Insight in June 2025, the chief executive of FinBox listed "Does the company email domain match the claimed employer?" among the employment checks lenders should triangulate.
What Does Calling HR for Every File Cost a Lender?
Calling HR for every file costs analyst hours, adds days to turnaround and still misses fake employers whose "HR desk" is a friend of the applicant. In this illustrative scenario, a lender handles 2,500 salaried files a month.
| Measure | HR Tele-Verification | Email Verification With Exception Review |
|---|---|---|
| Minutes per file, including retries | 18 | 3 |
| Analyst hours a month | 750 | 125 |
| Hours released | – | 625, about three and a half full-time analysts |
| Typical turnaround | 1 to 2 working days | Minutes, when the applicant is online |
The turnaround row matters most in personal loans, where the applicant often takes the first offer that arrives.
Which Checks Make Official Email Verification Reliable?
Six checks make official email verification reliable: free-domain screening, OTP delivery, domain-to-employer match, domain age, mail authentication records and duplicate-use detection.
| Check | What It Tests | Typical Fail Signal |
|---|---|---|
| Free or disposable domain | Is it a personal email service? | Gmail, Yahoo or throwaway domains |
| OTP to the work address | Applicant can read the mailbox | OTP not entered |
| Domain-to-employer match | Domain belongs to the declared employer | Domain differs from the employer's website |
| Domain age | When the domain was registered | Registered weeks before the application |
| Mail records | Domain receives and authenticates mail | No mail exchanger (MX) or authentication records |
| Duplicate use | Address used on other applications | Same address on unrelated applicants |
The last check works best inside loan application deduplication, and external fraud bureau checks are covered in our guide to Hunter fraud check integration.
How Does an Email OTP Prove Mailbox Control?
An email OTP proves mailbox control because the code reaches only the inbox of the address entered, and the applicant must type it back within a short window. The code should be single-use, expire quickly and be sent from the lender's own authenticated domain.
Two controls stop OTP gaming. Limit how many times an applicant can change the work address after a failed attempt, and log every address tried, because a string of failed corporate addresses followed by a success on an unknown domain is itself a fraud signal.
How Can Lenders Tell a Real Employer Domain From a Fake One?
Lenders can tell a real employer domain from a fake one by testing five public signals that a fraudster finds hard to fake all at once.
| Signal | Where to Check | Genuine Employer Usually Shows |
|---|---|---|
| Registration date | Registration Data Access Protocol (RDAP) lookup | Several years old |
| Mail exchanger records | Domain Name System (DNS) | Present, often a known mail provider |
| Sender Policy Framework (SPF) and Domain-based Message Authentication, Reporting and Conformance (DMARC) records | DNS | Published |
| Website | Employer's public website | Same domain as the email |
| Company records | Ministry of Corporate Affairs (MCA) master data | Matching company name; email often on the same domain |
According to the Internet Corporation for Assigned Names and Numbers (ICANN), RDAP was created to replace WHOIS, and generic top-level domain registries and registrars were no longer required to run WHOIS from 28 January 2025. According to Request for Comments (RFC) 9989 (May 2026), DMARC lets domain owners publish a policy telling receivers how to treat mail that fails SPF or DomainKeys Identified Mail (DKIM).
Large employers have strong reasons to publish these records. Google's sender guidelines have required all senders to Gmail to set up SPF or DKIM since 1 February 2024, and bulk senders to add DMARC as well.
Should Lenders Accept Forwarded HR Emails as Proof?
Lenders should accept forwarded HR emails as proof only when the original message, forwarded as an attachment, carries a valid DKIM signature from the employer's domain. According to RFC 6376, DKIM lets the domain owner take responsibility for a message through a cryptographic signature checked against a public key in its DNS.
A pasted or screenshotted email has no such signature, which is why the same caution applies as in forged salary slip detection.
Which Results Should Pass, Refer or Decline a File?
Five result patterns cover most files, and each one maps to a clear action.
| Result Pattern | Action |
|---|---|
| OTP passed, domain matches employer, domain several years old | Pass |
| OTP passed, domain matches, but domain new or no mail records | Refer for a second proof |
| OTP passed, domain does not match employer | Refer; likely look-alike domain |
| OTP failed or abandoned | Refer to alternative evidence |
| Free email domain for a large employer | Ask for the work address; refer if refused |
Declines should come from the reviewer, not the rule, because genuine applicants sometimes mistype or work for a group company with a different domain.
Should Lenders Keep an Approved Employer Domain List?
Lenders should keep an approved employer domain list for their top employers, because a known-good list turns most salaried files into instant passes. Each entry should hold the employer's legal name, every domain its staff use, including group and legacy domains, and the date it was last confirmed.
Ownership matters as much as content. Credit operations should own the list, with maker-checker approval for additions, so a sales team cannot quietly add a domain to speed up its own files.
Is a look-alike domain getting past your salaried checks?
See How the Digiqt Lending Platform Supports Custom Verification Steps
Learn how Digiqt builds onboarding, disbursement and repayment journeys for NBFCs, or talk to our lending platform team.
How Does the Digiqt Lending Platform Run Official Email Verification?
The Digiqt Lending Platform runs official email verification by letting Digiqt build the OTP step, domain checks and referral rules into your onboarding journey, so every salaried file is checked the same way.
The Digiqt Lending Platform helps lenders launch a custom lending product or platform in weeks, with onboarding, disbursement and repayments exposed through application programming interfaces (APIs). Digiqt can build this email verification workflow on it to your credit policy.
| Step | Manual Today | With a Workflow on the Digiqt Lending Platform |
|---|---|---|
| Capture | Work email typed on a form, rarely checked | Work email collected with purpose notice |
| OTP | Not used, or sent from a sales officer's phone | OTP step built into the journey |
| Domain checks | Analyst searches the web if time allows | Your chosen checks run and stored per file |
| Matching | Analyst judgement | Your approved employer-domain list applied |
| Exceptions | Phone calls to HR | Referral queue with reasons |
| Audit | No record | Results kept with the application |
The lender still decides which signals count, maintains its approved domain list and owns the final credit call.
Worked Example: A Real Mailbox on the Wrong Domain
In this illustrative example, the applicant passes the OTP but fails domain checks, so the file is referred and later declined. The applicant claims to be a software engineer at a private limited company, earning ₹72,000 a month, and applies for a ₹5 lakh personal loan.
| Check | Finding | Result |
|---|---|---|
| OTP | Entered correctly within 60 seconds | Pass |
| Domain age | Registered 41 days before the application | Fail |
| Mail records | MX present, no DMARC record | Weak |
| Website match | Employer's website uses a different domain | Fail |
| MCA master data | Company exists, incorporated 2019, email on another domain | Fail |
Three fails and one weak signal outweigh one pass. The reviewer asks for Employees' Provident Fund Organisation (EPFO) records and salary credits, finds neither, and declines.
Where Does Official Email Verification Fall Short?
Official email verification falls short for five groups of applicants, so lenders need a defined fallback for each.
| Applicant Group | Why Email Fails | Better Evidence |
|---|---|---|
| Staff of small firms on free email | No corporate domain | Salary credits, EPFO records |
| Contractors placed at a client | Client's email, payroll elsewhere | Payroll company's records |
| Recent leavers | Mailbox may still work for a few days | Exit date in EPFO records |
| Group companies | Parent's domain, subsidiary payroll | Approved domain list per group |
| Field and factory staff | No email account | Field investigation |
For anchor employers, employer tie-ups for salaried loans can supply a verified domain list directly. Fraud teams can also feed email results into a lending fraud detection artificial intelligence (AI) agent alongside device and bureau signals.
How Should Lenders Handle Work Email Data?
Lenders should treat the work email as personal data: tell the applicant why it is collected, use it only for verification and retain it only as policy allows. Our guide to DPDP Act compliance for lenders covers notices, consent and retention under the Digital Personal Data Protection (DPDP) framework.
Want salaried employment proven in minutes, not after a day of HR calls?
See How Digiqt Builds Email Verification Into Onboarding
Discover how Digiqt builds custom lending journeys in weeks, or book a demo with our team.
Sources
- RFC 9989: Domain-Based Message Authentication, Reporting, and Conformance (DMARC), May 2026
- RFC 6376: DomainKeys Identified Mail (DKIM) Signatures
- RFC 7208: Sender Policy Framework (SPF)
- ICANN: Registration Data Access Protocol (RDAP)
- Google Workspace Admin Help: Email Sender Guidelines
- Analytics Insight: How Smart Triangulation Can Help Nip Lending Frauds in the Bud
- LegalWiz: How to View Company Details From MCA Master Data
- AZB & Partners: India's DPDP Framework Comes Into Effect



