Chapter 05 of 05 · Verify before you send
How to get emails from LinkedIn Sales Navigator, then verify them
By BillionVerify Team · Facts checked November 2026 · Updated
You finish with: A send-ready list sorted by verification result, plus a stop rule for bounces.
Sales Navigator gives you a name, a title and a company. It does not give you an inbox. Most leads show no email at all. So the last step before any cold email is two jobs: find an address, then prove it works. This chapter covers how to get emails from LinkedIn Sales Navigator leads and how to verify each one before you send. Outreach Playbook is not affiliated with LinkedIn. BillionVerify is an email verification service.
Key facts (checked November 2026):
- LinkedIn’s help center says a member’s primary email is visible only to direct connections by default.
- BillionVerify returns one of six statuses on current checks: valid, invalid, unknown, catchall, role or disposable, per its API docs.
- BillionVerify never bills unknown results, per its verification reasons reference.
- BillionVerify reports catch-all domains as their own status instead of valid.
- BillionVerify’s free tool gives each IP 20 free full checks per IP every 24 hours, with no sign-up.
Where do the emails come from?
You have five honest sources. Use them in this order.
- The person. Start a conversation, then ask for the best address.
- Your CRM. The lead may already be a contact.
- A public company page. Websites, press releases and conference pages often list work emails.
- A contact data provider. Read its terms and privacy notice before you upload a list.
- A guess from the company’s format. This is the weakest source, and it always needs a check.
How do you use a business email format?
Companies tend to use one pattern. Common ones are first.last@company.com, first@company.com and flast@company.com. Find one real address at the same company, such as a press contact. Match its pattern, then build the lead’s address from the name.
Treat the result as a guess. Test the pattern on a few leads before you build the whole list. If you would rather not guess, the BillionVerify Email Finder takes a name and a company domain and returns the work address it finds, after an SMTP check.
Why verify before the first send?
An address you did not get from the person may be wrong. People change jobs and domains change. Some companies accept mail for any name, so a bad guess looks fine until nobody replies.
Bounces hurt your sender reputation. A damaged reputation pushes even good emails to spam. The first campaign on a new list is the worst moment for that, so check first.
How do you verify the list?
Start small. Paste one address into BillionVerify’s address checker and read the status. Then check each lead’s address the same way and note the status in your sheet. Do not send anything until every row has a result.
What do you do with each result?
The status tells you what to do next. BillionVerify Email Verifier returns one of these for each address.
| Status | What it means | What to do |
|---|---|---|
| valid | The mailbox is confirmed deliverable | Send |
| invalid | The mailbox or domain cannot receive mail | Delete |
| unknown | The check could not reach a conclusion | Hold and check again later |
| catchall | The domain accepts mail for every address | Small batch first |
| role | A shared inbox such as info@ or support@ | Send with care |
| disposable | A temporary email service | Delete |
Why is unknown not a verdict?
Many unknown results are temporary. The mail server may be rate limiting, greylisting or timing out. BillionVerify’s reference marks those reasons as retryable, so check the address again later. A re-check within 24 hours is free, and unknown results are never billed.
Some providers can never be checked. Addresses at Apple iCloud, Proton and Tuta always return unknown. Treat them as untested and send them in small batches.
How should you treat catch-all and role addresses?
A catch-all domain accepts every address, so one mailbox cannot be confirmed on its own. Microsoft 365 internal relay and security gateways in accept-all mode land here too. Send a small batch and watch the bounces before you send the rest.
Role addresses are usually deliverable but get low engagement, per BillionVerify’s reference. Prefer a named person when you can find one.
When should you stop sending?
Send the first batch small. Watch the bounces before you send more. If bounces climb, pause the campaign. Look for the cause, such as a stale list or a wrong guessed format. Verify again, then restart with a smaller batch.
The playbook ends here. You have a plan, a budget, a tested tool, a list and a clean set of addresses.