Phone Number Lookup from LinkedIn: How to Find Phone Numbers in 2026

You have a LinkedIn URL. You need a phone number. LinkedIn doesn't show phones publicly. So how do you get there?

5 workflows in 2026, ranked by hit rate and ban risk.

The 5 LinkedIn URL → phone workflows

1. Dedicated phone finder via LinkedIn URL

Tools like Derrick and Wiza take an URL and return a verified phone number. Hit rate 35-60% depending on region (US best, APAC weakest).

Pros: fastest, no ban risk on your account, works at bulk.
Cons: cost per match ($0.20-1.50).

2. LinkedIn Sales Navigator + cross-source

If the prospect exposed contact info on Sales Nav, you might see it. Combine with email finder cross-source to bypass.

Pros: leverages Sales Nav data you may already have.
Cons: requires Sales Nav subscription.

3. Chrome extension scraping

Chrome extensions of this kind scrape directly on profile pages.

Pros: free-tier often available.
Cons: cookie-based, ban risk on your account if abused (>50/day manual).

4. Manual research (Google + website + footer)

For high-value prospects: take the name, search Google + company website + look at footer signatures in their posts.

Pros: free, zero ban risk.
Cons: doesn't scale, 5-10 min per lead.

5. Direct ask (LinkedIn DM)

Simply ask: "What's the best number to reach you?" - works on warm connections, 8-15% reply rate.

Pros: 100% accurate when answered, builds rapport.
Cons: requires existing connection or strong context.

Hit rate by tool - what's real in 2026

Read the last column with the first. Derrick returns a number on 50-60% of US profiles for roughly a fifth of what the same match costs on the premium tier, which is what decides the budget once you run thousands of rows rather than dozens.

Cascade for max coverage

Best ROI workflow:

1. Bulk run primary tool (Derrick or Lusha) - covers 50-60%
2. For the nulls, run a 2nd cheaper tool - picks up another 10-15%
3. For high-priority remaining: manual research + LinkedIn DM

The lower-risk path is to stop scraping the profile for the number at all and resolve it from the identity instead. That is what the Phone Finder feature does from Google Sheets, without a browser session on your account.

Avoiding ban risk

If you scrape via extension or DM at scale, you risk LinkedIn restrictions. Mitigations:

• Stay under 50 manual actions/day on your account
• Use cookie-based extensions sparingly
• Prefer API-based lookups: the request runs on the vendor's infrastructure, so your LinkedIn account is never in the loop. Derrick exposes its Phone Finder through a REST API and an MCP server
• Don't connect tools that automate beyond 100 LinkedIn requests/day

Key takeaways

• From a LinkedIn URL to a phone number: 5 workflows ranging from 10% (manual) to 70% (premium API).
• Cascade 2 tools is the best ROI - primary tool covers 50-60%, fallback gets 10-15% more.
• Derrick has the lowest cost per match on this list, around €0.30 on the Standard plan, at a 50-60% US hit rate.
• Cognism and Lusha reach 55-70% but cost $1-1.50 per match, so the extra coverage is paid 3 to 5 times over on every number.
• For high-value targets: combine tool match + LinkedIn DM ask - accuracy near 100% on the ones who answer.