Find a work address from a name and a domain

Enter a first name, a last name, and a company domain. We check the likely addresses and show the best match with a confidence level.

Get started free Single checks

Fig. 1Find email · POST /v1/find_email

1.1 Search

name: Ada Lovelace
domain: acme.io · mail server found

1.2 Addresses checked

1.3 Best match

[email protected] · first.last · confidence high

Sample search · fictional person · 5 of 13 patterns shown

Input: First name, last name, domain
Tries: Up to 13 address patterns
Result: Best match with a confidence
Uses: One check per address tried

§ 1

Why it matters

A guessed address costs a bounce

Teams guess first.last@ and send. A wrong guess bounces, and each bounce hurts your sender reputation.

No email is sent to the person. Each address we try counts as one check.

Fig. 2Without and with Verifier

WithoutWith Verifier

Without: Teams guess first.last@ and hope it delivers.With Verifier: Up to 13 likely addresses are checked for you.
Without: A wrong guess bounces and hurts your sender reputation.With Verifier: Only a match with a confidence of high or medium is suggested.
Without: Each person tries patterns by hand.With Verifier: The same search works in the app and through the API.

§ 2

How it works

Up to 13 patterns, one check each

We build up to 13 addresses from the name, such as first.last and flast. We check the domain's mail servers first, then each address, and rank the results.

2.1Enter a first name, a last name, and a company domain.
2.2We check the domain, then each likely address.
2.3Use the best match, or review the other results.

Fig. 3One search

POST /v1/find_email

{  "first_name": "Ada",  "last_name": "Lovelace",  "domain": "acme.io"}

Response

{  "job_id": 812,  "status": "running",  "candidates_checked": 13}

GET /v1/find_email/812

{  "status": "completed",  "domain_has_mx": true,  "domain_is_catch_all": false,  "best_match": {    "email": "[email protected]",    "score": 100,    "confidence": "high",    "pattern": "first.last"  }}

13 addresses tried, 13 checks used · fields trimmed

§ 3

What you get

What you get.

3.1A confidence you can readThe best match comes with its score and a confidence of high or medium. A catch-all domain accepts every address, so the result says so and the confidence stays at medium.
3.2No checks used on dead domainsIf the domain has no mail server, the search stops and uses no checks.

Table 3 · The patterns we try, for Ada Lovelace at acme.io

Pattern	Address
first.last	[email protected]
flast	[email protected]
f.last	[email protected]
firstlast	[email protected]
first_last	[email protected]
first-last	[email protected]
first	[email protected]
last	[email protected]
first.l	[email protected]
firstl	[email protected]
last.first	[email protected]
lastf	[email protected]
f_last	[email protected]

§ 4

In practice

Typical uses.

Case 4.1
Reach a contact you met
Find the work address of someone you met at an event, and check it before you write.
Case 4.2
Complete a CRM record
Fill in a missing address for a known contact at a company you work with.

Works with the tools you send from.

All integrations

Questions

Before you start.

How many checks does a search use?

One check for each address it tries, up to 13. If the domain has no mail server, the search uses none.

Does a search send an email?

No. Each address is checked like a single check, and no message is delivered.

Can I email any address that I find?

Only people you have a lawful reason to contact. Privacy and anti-spam laws, such as GDPR and CAN-SPAM, apply to the messages you send.

A guessed address costs a bounce

Teams guess first.last@ and send. A wrong guess bounces, and each bounce hurts your sender reputation.

No email is sent to the person. Each address we try counts as one check.

Fig. 2Without and with Verifier

WithoutWith Verifier

Without: Teams guess first.last@ and hope it delivers.With Verifier: Up to 13 likely addresses are checked for you.
Without: A wrong guess bounces and hurts your sender reputation.With Verifier: Only a match with a confidence of high or medium is suggested.
Without: Each person tries patterns by hand.With Verifier: The same search works in the app and through the API.

Up to 13 patterns, one check each

We build up to 13 addresses from the name, such as first.last and flast. We check the domain's mail servers first, then each address, and rank the results.

2.1Enter a first name, a last name, and a company domain.
2.2We check the domain, then each likely address.
2.3Use the best match, or review the other results.

Fig. 3One search

POST /v1/find_email

{  "first_name": "Ada",  "last_name": "Lovelace",  "domain": "acme.io"}

Response

{  "job_id": 812,  "status": "running",  "candidates_checked": 13}

GET /v1/find_email/812

{  "status": "completed",  "domain_has_mx": true,  "domain_is_catch_all": false,  "best_match": {    "email": "[email protected]",    "score": 100,    "confidence": "high",    "pattern": "first.last"  }}

13 addresses tried, 13 checks used · fields trimmed

What you get.

3.1A confidence you can readThe best match comes with its score and a confidence of high or medium. A catch-all domain accepts every address, so the result says so and the confidence stays at medium.

3.2No checks used on dead domainsIf the domain has no mail server, the search stops and uses no checks.

Pattern

Address

first.last

flast

f.last

firstlast

first_last