Stop bad addresses at signup

Check each address in real time, and catch typos, throwaway addresses, and dead domains before they enter your list.

Get started free API and SDKs

Fig. 1Signup form · POST /v1/check_email

1.1 Form

Work email

[email protected]

Did you mean [email protected]?

1.2 Result

category: risky
safe_to_send: false
reason_codes: possible_typo
suggestion: [email protected]

Sample request · fictional address

Call: POST /v1/check_email
Typo hint: A suggested address
Decide with: category and safe_to_send
Plans: Professional and Enterprise

§ 1

Why it matters

A bad signup costs more than a bounce

A mistyped address means a lost user and a password reset that never arrives. A throwaway address means a fake account.

For product and engineering teams that own signup and transactional email.

Fig. 2Without and with Verifier

WithoutWith Verifier

Without: Throwaway addresses create trial accounts.With Verifier: The form checks the address before it creates the account.
Without: A mistyped address never gets the welcome email.With Verifier: A likely typo comes back as possible_typo.
Without: Fake signups skew your funnel numbers.With Verifier: Disposable addresses get a reason code you can block on.

§ 2

How it works

One API call in your signup flow

Call the check endpoint when the user submits the form. Use the result to accept the address, ask for a fix, or block it.

2.1Call the API when the user submits the form.
2.2Ask the user to fix a likely typo.
2.3Block disposable addresses if your policy says so.

Fig. 3One check from your code

TypeScript

import { Configuration, V1Api } from "@oppulence/reacher-sdk";const api = new V1Api(  new Configuration({    basePath: process.env.VERIFIER_API_URL,    apiKey: `Bearer ${process.env.VERIFIER_API_KEY}`,  }),);const { data } = await api.v1CheckEmail({  checkEmailRequest: { to_email: "[email protected]" },});if (!data.score.safe_to_send) {  // Ask the person to check the address.}

cfg := reacher.NewConfiguration()cfg.Servers = reacher.ServerConfigurations{{URL: os.Getenv("VERIFIER_API_URL")}}cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("VERIFIER_API_KEY"))client := reacher.NewAPIClient(cfg)out, _, err := client.V1API.V1CheckEmail(ctx).	CheckEmailRequest(*reacher.NewCheckEmailRequest("[email protected]")).	Execute()

Generated SDKs · same call in each language

§ 3

What you get

What you get.

3.1Signup protection policySet signup protection as your workspace policy, and each result comes with a clear decision.
3.2Typo hintsCatch common domain typos before the account is created.

Table 3 · What a result contains

Field	Values	Meaning
category	valid · risky · invalid · unknown	The verdict for the address.
score	0 to 100	Higher is safer to send.
safe_to_send	true · false	One flag for your send rules.
reason_codes	List of codes	Each code names one thing the check found.
is_reachable	safe · risky · invalid · unknown	The raw reachability reading.

§ 4

In practice

Typical uses.

Case 4.1
Free trials
Reduce fake trial accounts made with throwaway addresses.

Works with the tools you send from.

All integrations

Questions

Before you start.

Will a slow mail server slow my signup form?

Set a timeout in your form. If the check does not finish in time, accept the address and check it again later.

A bad signup costs more than a bounce

A mistyped address means a lost user and a password reset that never arrives. A throwaway address means a fake account.

For product and engineering teams that own signup and transactional email.

Fig. 2Without and with Verifier

WithoutWith Verifier

Without: Throwaway addresses create trial accounts.With Verifier: The form checks the address before it creates the account.
Without: A mistyped address never gets the welcome email.With Verifier: A likely typo comes back as possible_typo.
Without: Fake signups skew your funnel numbers.With Verifier: Disposable addresses get a reason code you can block on.

One API call in your signup flow

Call the check endpoint when the user submits the form. Use the result to accept the address, ask for a fix, or block it.

2.1Call the API when the user submits the form.
2.2Ask the user to fix a likely typo.
2.3Block disposable addresses if your policy says so.

Fig. 3One check from your code

TypeScript

import { Configuration, V1Api } from "@oppulence/reacher-sdk";const api = new V1Api(  new Configuration({    basePath: process.env.VERIFIER_API_URL,    apiKey: `Bearer ${process.env.VERIFIER_API_KEY}`,  }),);const { data } = await api.v1CheckEmail({  checkEmailRequest: { to_email: "[email protected]" },});if (!data.score.safe_to_send) {  // Ask the person to check the address.}

cfg := reacher.NewConfiguration()cfg.Servers = reacher.ServerConfigurations{{URL: os.Getenv("VERIFIER_API_URL")}}cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("VERIFIER_API_KEY"))client := reacher.NewAPIClient(cfg)out, _, err := client.V1API.V1CheckEmail(ctx).	CheckEmailRequest(*reacher.NewCheckEmailRequest("[email protected]")).	Execute()

Generated SDKs · same call in each language

What you get.

3.1Signup protection policySet signup protection as your workspace policy, and each result comes with a clear decision.

3.2Typo hintsCatch common domain typos before the account is created.

Table 3 · What a result contains

Field	Values	Meaning
category	valid · risky · invalid · unknown	The verdict for the address.
score	0 to 100	Higher is safer to send.
safe_to_send	true · false	One flag for your send rules.
reason_codes	List of codes	Each code names one thing the check found.
is_reachable	safe · risky · invalid · unknown	The raw reachability reading.

From a raw listto a safe send.

Stop bad addresses at signup

A bad signup costs more than a bounce

One API call in your signup flow

What you get.

Typical uses.

Works with the tools you send from.

Before you start.

From a raw listto a safe send.

Stop bad addresses at signup

A bad signup costs more than a bounce

One API call in your signup flow

What you get.

Typical uses.

Works with the tools you send from.

Before you start.