How to find someone's LinkedIn profile from an email address

The three manual ways, and where they break

Before paying, try the free routes. They are worth a minute, and they are why SenderFinder starts with a local signature scan.

1. Web search. "name@company.com" site:linkedin.com/in relies on the address appearing on an indexed page — a speaker list, a GitHub profile, a personal site. Most profiles do not show an email, so this only works when the address leaked elsewhere.

2. LinkedIn search. Paste the display name, add the company, compare headline and location. Works for unusual names at small companies. Fails for common names, aliases, people between jobs and private profiles — and costs ten tabs of attention per email.

3. Read the signature. A search for linkedin.com/in in the thread is free and instant. It fails when the sender omits it, when it is an image, or when it hides behind a tracking redirect. This is the one manual method the extension automates locally.

Why email → LinkedIn is not a lookup table

There is no public API that maps an email address to a LinkedIn profile. LinkedIn's APIs are for authenticated members and partners, not arbitrary reverse lookups. Providers fill the gap with licensed data, public-web signals, company domains and their own graph; coverage and prices differ. The hard part is not finding a person with that name, but deciding whether that person is the sender. j.smith@acme.com narrows the company, not two Smiths, a shared mailbox or a former employee. A serious lookup constrains by company domain and compares the returned name with the mail header — which is why SenderFinder sometimes says “uncertain”.

The automated way: a cheapest-first waterfall

A waterfall runs several providers in order, cheapest first, and stops at the first answer that passes the name check. The order is the product: you do not pay Apollo prices for an address a half-cent lookup can solve, and you do not stop at an uncertain cheap answer when a costlier step can confirm it.

• Signature scan — local regex over the mail body for a linkedin.com/in link. Free, and the answer is cached if found.
• BlitzAPI (treg) — reverse email lookup. Catalog price $0.0005 per hit; misses are free.
• Hunter (Monid) — email to profile. $0.0049 per hit; a 404 miss is free.
• QuickEnrich (treg) — email enrichment. $0.0048 per hit; misses are free.
• Apollo (Monid) — email plus name plus company domain. $0.026 per hit; a miss is free unless Apollo returns an empty stub attached to a known company, which is billed. In this run every call that reached Apollo answered.
• Data Legion (Firecrawl, optional) — a last-resort fallback, 10 credits, roughly $0.008–$0.032. Not recommended as a first step.

What a lookup costs

The 50-address benchmark measured the full waterfall at about $0.0111 per address: 48 of 50 verified work addresses found, 2 uncertain. With treg alone, 29 of 50 addresses were answered (26 found, 3 uncertain) for about $0.0006 per address. That is “one key is enough” in numbers: a cheap key gets a useful first pass; a second key buys the backstop.

Two caps keep a bad day from becoming an expensive one. The per-lookup cap (default $0.05) skips any step whose current catalog price would push a single lookup over the limit. The daily cap (default $2) stops paid calls once the day's spend reaches it. Both are editable in settings, and both are checked before the call, not after.

Caching changes the economics more than any provider choice. An address is looked up once and served from IndexedDB, pruned by default to 90 days and 5,000 entries. Repeat senders — most of an inbox — cost nothing after the first lookup. That is why the calculator asks for new sender addresses per day, not emails read.

Accuracy: what “found” and “uncertain” mean

A provider can return a profile whose name does not match the display name in the email. SenderFinder keeps that result only as a fallback, runs the remaining steps, and lets a matching answer win. If nothing matches, the card is marked “uncertain” and shows both names.

Personal mailbox domains (gmail.com, outlook.com, qq.com) and role addresses (info@, support@, sales@) are skipped because they rarely map to one person. A “look up anyway” button is there when you disagree.

The extension shows what the provider returned. It does not verify that the profile is current, still at that company, or canonical. Treat a match as a strong hint, not identity verification.

Privacy: where the address goes

The address, display name and company domain go to the provider whose key you configured, with that key. That is the same data a manual search exposes to a search engine, minus the browser history. SenderFinder has no server in the lookup path.

The mail body is scanned locally for a LinkedIn link and is never stored or transmitted. Phone numbers and personal emails returned by a provider are discarded; only professional fields are kept. Keys, cache and history stay in browser storage.

Anonymous daily counts are on by default and one switch turns them off, deleting the installation ID and anything unsent. The privacy statement has the full list.

When it will not work

Even a perfect waterfall is not a person database. Expect gaps in these cases:

• The person has no LinkedIn profile, or the profile is not discoverable by the providers.
• The email is a shared or role address that does not belong to one person.
• The address is new, personal, or on a domain the providers have not indexed.
• The name in the mail header is a nickname, a localised name or a different spelling from the profile.
• The person changed companies recently and the providers still return the old profile.
• You are reading Outlook on the web: supported on a best-effort basis, and the sender mark can disappear when Microsoft changes the page structure.

A five-minute manual checklist

When you do not want to spend a lookup, this sequence gets the most out of the free routes:

1. Search the thread for linkedin.com/in. If the signature has it, you are done.
2. Search the web for the exact address in quotes plus site:linkedin.com/in.
3. Search LinkedIn for the display name plus the company name; open the most plausible profile and compare the headline, location and tenure.
4. If the name is common, add the company domain, a past employer or a conference/talk title to the query.

The automated route is worth it when the same question arrives dozens of times a day, when manual searches keep failing on common names, or when you want the answer inside the inbox.

Related reading

• The 50-address benchmark — measured hit rate and price per provider.
• Sales Navigator for Gmail is gone — what still works for sender lookup.
• The Outlook sidebar — what works on Outlook on the web and what does not.
• Clearbit Connect alternative and Rapportive alternative.
• Install guide — from ZIP to the first lookup in two minutes.