Email validation · Use cases · Lead forms
Use case
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 validity, mailbox 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.
At capture
One request, four possible answers.
Try one address.
The same check your lead form would run. 10 free checks a day, no key and nothing sent to the address.
Or try
Why verify email on lead capture forms?
Wasted sequences on dead addresses
Inflated cost-per-lead from junk submissions
Pipeline and attribution drift
Sender reputation damage from list bounces
How does lead form email verification work?
One API call between the form submit and the CRM sync.
The lead submits the form
Your backend verifies the address
Sync, flag, route, or reject before the CRM
Which leads should you flag, route, or reject?
The four statuses map to four CRM actions. Most of the value is in the middle, where you sync a lead but mark it instead of throwing it away.
Status
What it means
CRM action
Format, MX, and SMTP confirm a real, deliverable mailbox.
Sync. Push the lead straight into the pipeline for normal follow-up.
Deliverable but unconfirmed at the mailbox. Catch-all domains and disposable domains land here. A role-based mailbox (info@, sales@) is flagged separately and does not set this status.
Sync with a flag, or route to review. Keep the lead, mark it as lower-confidence, and let a rep qualify before heavy outreach.
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.
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.
Four rules for the lead form.
Keep dead addresses out of the send list
Protect the reputation behind real leads
Treat catch-all as risky, not unknown
Route role-based leads, do not reject them
What does the API response look like?
One POST from your lead form handler. The status decides whether the lead syncs; the signals underneath tell you why.
// in your lead form handler, before the CRM sync
const check = await fetch(
"https://api.trueguard.io/v2/email/validation",
{
method: "POST",
headers: {
"X-API-KEY": process.env.TRUEGUARD_KEY,
"Content-Type": "application/json"
},
body: JSON.stringify({ email })
}
).then((r) => r.json());
if (check.deliverability.status === "invalid") {
return reject("Please check your email address");
}{
"email": "name@gmail.com",
"rawEmail": "name@gmail.com",
"syntax": { "isValid": true },
"deliverability": {
"status": "safe",
"isSmtpValid": true,
"isMxValid": true,
"isCatchall": false,
"isInboxFull": false,
"isDeliverable": true,
"isDisabled": false,
"mxRecords": [
"gmail-smtp-in.l.google.com",
"alt1.gmail-smtp-in.l.google.com",
"alt2.gmail-smtp-in.l.google.com",
"alt3.gmail-smtp-in.l.google.com",
"alt4.gmail-smtp-in.l.google.com"
]
},
"domain": {
"name": "gmail.com",
"age": 11363,
"isLive": true,
"isRisky": false
},
"quality": {
"isDisposable": false,
"isFree": true,
"isRole": false,
"isSubaddress": false
}
}Frequently asked questions.
Still deciding? Contact support or read the API reference.
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 a working one comes back safe with the role flag set, not invalid. The flag tells you the address reaches a shared inbox rather than a named person, which is 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 addresses come back risky unless a second check confirms the mailbox, 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.
Clean leads from the first submit.
100 validations a month, free, no card. Add one call to your form handler and junk leads stop reaching your CRM.
Get your free API keyNo credit card required.
