Lead form email verification for a clean CRM
Verifying email on a lead form means checking each address as the lead submits, before it syncs to your CRM. Trueguard's email validation confirms format, MX records, SMTP deliverability, disposable domains, catch-all behavior, role-based mailboxes, and free-mail providers in one call, so junk and fake leads are flagged at capture and your sales pipeline stays clean.
The problem
Why verify email on lead capture forms?
A junk lead does not announce itself. It clears your form, syncs to the CRM, and costs you time and deliverability before you realize the address was never real.
Wasted sequences on dead addresses
Real rep time and email quota spent following up on leads whose addresses were never deliverable. The sequence runs, nothing lands, and the cost is invisible until the bounce report appears.
Inflated cost-per-lead from junk submissions
Fake and throwaway leads count against your ad spend and form conversion numbers, diluting your cost-per-lead. The campaigns look less efficient than they are because the denominator is polluted.
Pipeline and attribution drift
A CRM full of undeliverable contacts skews every report that touches the pipeline. Lead source attribution, stage conversion rates, and forecasts all drift away from what is actually real.
Sender reputation damage from list bounces
Marketing sends to unverified lead lists accumulate bounces. Enough of them and mailbox providers start routing your sends to spam, including the mail to leads who are genuinely interested.
*Impact examples are illustrative. Actual results depend on your form volume and lead mix.
How it works
How does lead form email verification work?
Lead form email verification is one API call between the form submit and the CRM sync. The lead submits, your form handler calls the email verification API, and the verdict decides whether the lead syncs clean, syncs flagged, routes to review, or never reaches the CRM at all. It runs server-side, so the result is trustworthy and the lead is already scored by the time it lands in your pipeline.
The lead submits the form
A visitor fills your lead capture or marketing form and submits. The check runs on submit, against the final address, so it fires once on the value the lead actually entered rather than on partial keystrokes.
Your backend verifies the address
Your handler sends the email to the validation endpoint and gets the seven signals back in one response: format against RFC 5322, MX records, SMTP deliverability from a live handshake that stops before any message is sent, disposable detection, catch-all detection, role-based detection, and free-mail provider detection.
Sync, flag, route, or reject before the CRM
The response carries a status of safe, risky, invalid, or unknown. You map it to a CRM action: sync clean leads straight in, sync risky ones with a flag, route ambiguous ones to review, and reject dead ones at the form. The lead arrives in your CRM already labeled, so reps spend time on the leads worth working.
The response
What does the API response look like?
Seven signals per lead. Safe syncs clean. Risky lands flagged. Invalid gets rejected at the form. Catch-all returns risky, not unknown.
{
"email": "realemail@gmail.com",
"rawEmail": "realemail@gmail.com",
"syntax": {
"isValid": true
},
"deliverability": {
"status": "safe",
"isSmtpValid": true,
"isMxValid": true,
"isCatchall": false,
"isInboxFull": false,
"isDeliverable": true,
"isDisabled": false,
"mxRecords": [
"alt2.gmail-smtp-in.l.google.com",
"gmail-smtp-in.l.google.com",
"alt4.gmail-smtp-in.l.google.com",
"alt1.gmail-smtp-in.l.google.com",
"alt3.gmail-smtp-in.l.google.com"
]
},
"domain": {
"name": "gmail.com",
"age": 11263,
"isLive": true,
"isRisky": false
},
"quality": {
"isDisposable": false,
"isFree": true,
"isRole": false,
"isSubaddress": false
}
}The decision
Which leads should you flag, route, or reject?
The four statuses map to four CRM actions. Lead quality is not binary, so the table is not a simple pass or fail: most of the value is in the middle, where you sync a lead but mark it for context instead of throwing it away. Two signals matter most here. Catch-all is risky, not unknown: the domain accepts mail for every address, so it is deliverable at the server but unconfirmed at the mailbox. Role-based addresses like info@ or sales@ are also a lead-quality flag: they are real and deliverable, but they reach a shared inbox, not a named buyer, so they are worth routing rather than rejecting.
| Result | What it means for the lead | CRM action |
|---|---|---|
| safe | Format, MX, and SMTP confirm a real, deliverable mailbox. | Sync. Push the lead straight into the pipeline for normal follow-up. |
| risky | Deliverable but unconfirmed at the mailbox. Catch-all domains and role-based mailboxes (info@, sales@) land here. | Sync with a flag, or route to review. Keep the lead, mark it as lower-confidence, and let a rep qualify before heavy outreach. A role-based address often signals an inbound from a company, not a junk fill. |
| invalid | Bad format, no MX records, or the server rejected the address. Undeliverable. | Reject at the form. Do not sync it. This is the lead that would have bounced and wasted a sequence. |
| unknown | The server blocked the probe or gave no clear answer. No verdict. | Retry or queue. Hold the lead for a re-check rather than rejecting a possibly real prospect because their provider rate-limited the probe. |
What it means for the lead
Format, MX, and SMTP confirm a real, deliverable mailbox.
CRM action
Sync. Push the lead straight into the pipeline for normal follow-up.
What it means for the lead
Deliverable but unconfirmed at the mailbox. Catch-all domains and role-based mailboxes (info@, sales@) land here.
CRM action
Sync with a flag, or route to review. Keep the lead, mark it as lower-confidence, and let a rep qualify before heavy outreach. A role-based address often signals an inbound from a company, not a junk fill.
What it means for the lead
Bad format, no MX records, or the server rejected the address. Undeliverable.
CRM action
Reject at the form. Do not sync it. This is the lead that would have bounced and wasted a sequence.
What it means for the lead
The server blocked the probe or gave no clear answer. No verdict.
CRM action
Retry or queue. Hold the lead for a re-check rather than rejecting a possibly real prospect because their provider rate-limited the probe.
Try one address
The same check your lead form would run. See how the API scores an address before you wire it into your backend.
Paste an address above. Or try one of the examples below.
Pricing
Start free. The first 100 validations a month are free with no card, enough to verify a low-volume lead form or trial the flow end to end. As your form volume grows, the same check ships in the email verification API at $49.99 a month for 50,000 validations, then $0.001 per validation beyond that. To sanity-check one address by hand first, run it through the free email verifier.
Pay for what you check. Cancel anytime. Overage is billed through Stripe at $0.001 per validation regardless of volume.
What counts as a validation? One request to the validation endpoint is one validation. Failed calls (4xx from your side) do not count.
Deliverability
How does verifying leads protect email deliverability?
Sender reputation is earned by sending to addresses that exist and lost by sending to ones that do not. Mailbox providers track your bounce rate as a quality signal. When a marketing send hits a wall of dead addresses from unverified lead forms, the bounces stack up, your reputation drops, and your next send is more likely to land in spam, including the mail to leads who are genuinely interested.
Verifying at capture breaks that cycle before it starts. An address confirmed deliverable at the form is an address that will not bounce when marketing emails it later. Disposable and invalid addresses get rejected before they ever enter a send list. You are not cleaning the list after the damage, you are keeping the damage out of the list.
We do not publish a bounce-rate figure for your sends, because your bounce rate depends on your list, your sending practices, and your content, not on validation alone. What verification does is remove the addresses that were guaranteed to bounce. That is the part you control at capture, and it is the part that protects the deliverability of every real lead behind it.
Related use cases
Signup Form Email Validation
Validate email addresses in real time at registration, before you create the account.
Learn moreEmail Validation for Fraud Teams
Use email validation as a standalone fraud signal to catch disposable and fake addresses.
Learn moreHubSpot Email Validation
Validate emails for HubSpot forms and contacts via Trueguard's API, before they become contacts.
Learn moreFrequently asked questions.
About lead form email verification.
What is lead form email verification?
Lead form email verification is a real-time check that runs when a prospect submits your lead capture or marketing form. Your backend sends the address to a validation API, which confirms format, MX records, and SMTP deliverability and flags disposable, catch-all, and role-based addresses. You then sync, flag, route, or reject the lead based on the verdict, so junk leads never reach your CRM clean.
Does it work with my existing lead capture form?
Yes. It is an API call from your form backend, so it works with any form: a native form on your site, a marketing landing page, or a hosted form whose submissions you process server-side. You do not replace the form. You add one verification call between the submit and the CRM sync, and act on the result.
Should I reject role-based addresses like info@company.com on a lead form?
No, do not auto-reject them. Role-based addresses are real and deliverable, so they come back risky, not invalid. They reach a shared inbox rather than a named person, which is a quality flag worth knowing, but on a lead form a sales@ or info@ fill is often a genuine inbound from a company. Route it to review or sync it with a flag rather than throwing it away.
How does this keep my CRM data clean?
It stops bad records at the door instead of cleaning them up later. Fake and undeliverable addresses are rejected before they sync, and ambiguous ones are flagged so reps know what they are looking at. Your conversion rates, source attribution, and pipeline reports stay accurate because the leads in them can actually be reached, not inflated by dead addresses no one can work.
Will verifying leads reduce my email bounce rate?
Verifying before you send removes the addresses that were guaranteed to bounce, which is the part of your bounce rate you control at capture. We do not promise a specific bounce-rate number, because your real rate also depends on your list age, content, and sending practices. What verification does is keep invalid and undeliverable addresses out of your send lists, which protects the sender reputation that gets your real mail delivered.
Can I catch fake or disposable leads?
Yes. Disposable detection checks each address against a continuously updated registry of throwaway providers, and the deliverability check catches addresses that look real but reject mail. Catch-all domains are flagged risky so you can treat them with extra care. Together these flag the fake and low-quality leads at capture, before a rep spends time chasing an address that was never real.
Is there a free tier to test on my lead form?
Yes. The first 100 validations a month are free with no card, which is enough to wire verification into a real lead form and watch the flags land in your CRM. For a quick single-address check, the free email verifier at https://trueguard.io/email-verifier runs the same validation in the browser. When you need more volume, the paid plan is $49.99 a month for 50,000 validations.
