Check one address before you send

Get a clear answer for one address: valid, risky, invalid, or unknown, with a score and the reasons behind it.

Get started free Scores and reasons

Fig. 1One check, four readings

Input[email protected]

FormatSyntax ok

Domainbrightlane.co

Mail servermx1.brightlane.co

MailboxAccepts mail

No email is sent

Result

valid

Score

100

Action

Keep

Readings run in this order · a check stops before delivery

Readings: Format, domain, mail server, mailbox
Result: Category, score 0–100, reasons
Where: App, API, and SDKs
Email sent: None

§ 1

Why it matters

A typo can cost you the conversation

An address can look right and still bounce. The domain may have no mail server, the mailbox may be gone, or the address may be a throwaway.

Type an address and get a result in seconds. No email is sent to the recipient.

Fig. 2Without and with Verifier

WithoutWith Verifier

Without: You find a bad address when it bounces.With Verifier: Each address gets a verdict before the first send.
Without: A typo such as gmial.com stays on the list.With Verifier: A likely domain typo comes back as possible_typo.
Without: Role and catch-all addresses look like real people.With Verifier: Reason codes name catch-all, role, and disposable addresses.

§ 2

How it works

Every check reads the full path to the inbox

We check the address format, the domain and its mail servers, and how the mail server answers for that mailbox. Then we score the result and explain it.

2.1Enter an address.
2.2See the category, the score, and the safe-to-send flag.
2.3Open the details to see each signal and reason code.

Fig. 3A risky address

POST /v1/check_email

{  "to_email": "[email protected]"}

Response

{  "is_reachable": "risky",  "score": {    "score": 65,    "category": "risky",    "safe_to_send": false,    "reason_codes": ["catch_all", "role_account"]  }}

Response trimmed to the score

§ 3

What you get

What you get.

3.1Reasons you can act onReason codes name the problem: no mail server, disabled mailbox, full inbox, catch-all domain, disposable address, role account, or a likely typo.
3.2History for every addressSee earlier results for the same address, so you know if it changed.

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
Before an important email
Check a new contact before you send a proposal or an invoice.

Works with the tools you send from.

All integrations

Questions

Before you start.

Does a check send an email?

No. The check stops before any message is delivered.

What if the result is unknown?

Some mail servers do not say if a mailbox exists. Unknown means we could not confirm it. Treat it with care, or check it again later.

A typo can cost you the conversation

An address can look right and still bounce. The domain may have no mail server, the mailbox may be gone, or the address may be a throwaway.

Type an address and get a result in seconds. No email is sent to the recipient.

Fig. 2Without and with Verifier

WithoutWith Verifier

Without: You find a bad address when it bounces.With Verifier: Each address gets a verdict before the first send.
Without: A typo such as gmial.com stays on the list.With Verifier: A likely domain typo comes back as possible_typo.
Without: Role and catch-all addresses look like real people.With Verifier: Reason codes name catch-all, role, and disposable addresses.

Every check reads the full path to the inbox

We check the address format, the domain and its mail servers, and how the mail server answers for that mailbox. Then we score the result and explain it.

2.1Enter an address.
2.2See the category, the score, and the safe-to-send flag.
2.3Open the details to see each signal and reason code.

Fig. 3A risky address

POST /v1/check_email

{  "to_email": "[email protected]"}

Response

{  "is_reachable": "risky",  "score": {    "score": 65,    "category": "risky",    "safe_to_send": false,    "reason_codes": ["catch_all", "role_account"]  }}

Response trimmed to the score

What you get.

3.1Reasons you can act onReason codes name the problem: no mail server, disabled mailbox, full inbox, catch-all domain, disposable address, role account, or a likely typo.

3.2History for every addressSee earlier results for the same address, so you know if it changed.

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.

Check one address before you send

A typo can cost you the conversation

Every check reads the full path to the inbox

What you get.

Typical uses.

Works with the tools you send from.

Before you start.

From a raw listto a safe send.

Check one address before you send

A typo can cost you the conversation

Every check reads the full path to the inbox

What you get.

Typical uses.

Works with the tools you send from.

Before you start.