SaaSAcquisition

Signup Validation

Block fake and mistyped emails during account registration, so every new account starts with a working address.

Email validity · 1 credit per lookup · no monthly fee

Create account

sara@acme.com
Deliverable — safe to accept
Sign up

The problem

Every fake or mistyped address that gets through your signup form becomes a dead account: welcome emails bounce, activation links never arrive, and your onboarding funnel reports users who never existed. Worse, those addresses poison every downstream system, your CRM, your email tool, your product analytics all inherit the junk.

With Encrata

Call the validity endpoint the moment someone submits the form, before you create the account. Encrata asks the receiving mail server directly whether the mailbox exists, flags disposable domains, and suggests corrections for obvious typos. Real addresses pass in well under a second; everything else gets stopped at the door with a clear reason you can show the user.

How it works

1

Send the address

Call the validity endpoint with the email address at the moment it enters your system, a form, an import, a checkout.

2

We ask the mail server

Encrata checks syntax, domain and mailbox directly with the receiving server, and flags disposable and typo domains.

3

Act on the verdict

Accept, reject or suggest a correction based on a clear valid / invalid / catch-all / risky verdict. One credit per check.

One call, structured answer

Signup Validation runs on the email validity lookup at 1 credit per lookup. Same API key, same JSON shape as every other Encrata lookup.

  • Answers come from the mail server itself, not a guess from patterns
  • Disposable and throwaway domains are flagged before they cost you anything
  • 1 credit per check, cheap enough to run on every address you touch
  • Cached results are free, so repeated checks never double-charge
Terminal
curl -X POST "https://encrata.com/api/agent/validate" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"email": "sara@acme.com"}'
response.json
{
"email": "sara@acme.com",
"status": "valid",
"reason": "deliverable",
"disposable": false,
"confidence": "high",
"provider": "google",
"message": "Mailbox exists and accepts mail, safe to send.",
"credits": 1
}

Validate before the account exists

Most teams wire the check into the form's submit handler: validate on blur or on submit, and only create the account once the verdict comes back. The response arrives fast enough to sit inline in the signup flow, and the did_you_mean field doubles as a typo prompt, so a single call covers both rejection and correction. Catch-all and risky verdicts are worth accepting with a flag rather than rejecting outright, corporate domains often answer that way even for real mailboxes.

Cleaner funnels from day one

The change shows up within the first week: activation-email bounce rates collapse, and the fake-signup noise that used to pollute product analytics disappears. Teams that A/B tested inline validation consistently find the small added friction costs less than the dead accounts did, and support stops fielding 'I never got my confirmation email' tickets from addresses that never existed.

More email validity use cases

View all
Start with 500 free credits
$curl https://encrata.com/api/agent/lookup -H "Authorization: Bearer YOUR_API_KEY" -d '{"e": "satya@microsoft.com"}'